systemd-tmpfiles: fchownat() of /run/.. failed: Invalid argument
Hello everyone,
I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After a recent reboot I found most of my services to be in a failed state. The reason for that, I guess, are these log entries:
Nov 17 04:47:42 h2118376 systemd-
Nov 17 04:47:42 h2118376 systemd-
Nov 17 04:47:42 h2118376 systemd-
Nov 17 04:47:42 h2118376 systemd-
Nov 17 04:47:42 h2118376 systemd-
Nov 17 04:47:42 h2118376 systemd-
Nov 17 04:47:42 h2118376 systemd-
Nov 17 04:47:42 h2118376 systemd-
Nov 17 04:47:42 h2118376 systemd-
Nov 17 04:47:42 h2118376 systemd-
Nov 17 04:47:42 h2118376 systemd-
Nov 17 04:47:42 h2118376 systemd-
Nov 17 04:47:42 h2118376 systemd-
Nov 17 04:47:42 h2118376 systemd-
To verify I tried this:
/usr/lib/
Reading config file "elasticsearch.
Running create action for entry d /var/run/
Found existing directory "/var/run/
"/run/elasticse
chown "/run/elasticse
fchownat() of /run/elasticsearch failed: Invalid argument
I can manually chown the directories, e.g. "chown elasticsearch:
At this point I don't know what to do.
I'm also confused about the version I have installed, which I thought is systemd-229. Howver, I looked at https:/
Tag v237 (and earlier, including 229):
/.../
}
/.../
Tag v238
/.../
if (fchownat(fd,
return log_error_
/.../
Any help fixing this problem would be highly appreciated.
Many thanks,
Rafael
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu systemd Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Rafael
- Solved:
- 2018-11-28
- Last query:
- 2018-11-28
- Last reply:
Rafael (riffraff99) said : | #1 |
a little update:
I did apt-get source for
- systemd=
- systemd=
and compared the two tmpfiles.c. I can confirm that the latest version replaced 'chown' with 'fchownat'. The packages are hosted by my server provider.
So my question is, why is fchownat not working on my system? Is there a chance I misconfigured anything? Can it be related to the virtualization?
Peter Enns (nelway) said : | #2 |
I am having the same issue.
I upgraded my VPS with 'sudo apt-get upgrade' a few days ago which broke Redis on my server. After a little investigation, the cause was that the installation failed with the error "fchownat() of /run/redis failed: Invalid argument".
I tried a clean install of the 16.04 OS, with 2 different VPS providers, and the exact same result both times. If I install the updates, the following installation of several different packages fail with the error message "fchownat() of /run/redis failed: Invalid argument"
Steps to reproduce:
1. Clean install of Ubuntu 16.04 (not sure exactly what each of the VPS providers use as the starting image, both are slightly different)
2. sudo apt update && sudo apt upgrade
3. sudo apt install lamp-server^
4. sudo apt install redis-server
Results in:
Setting up redis-server (2:3.0.6-1) ...
fchownat() of /run/redis failed: Invalid argument
Job for redis-server.
invoke-rc.d: initscript redis-server, action "start" failed.
I have not found a solution yet (except not installing the latest version).
Chris E (cbz) said : | #3 |
Raised and linked the following bug to this problem:
https:/
Rafael (riffraff99) said : | #4 |
Thanks all for taking this up!