systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Fix Released
|
Undecided
|
Chris Coulson |
Bug Description
The following description is taken from:
https:/
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
=== Notes ===
fchownat() was added to Linux in kernel 2.6.16;
library support was added to glibc in version 2.4.
checkinf if it is blocked/
glibc in bionic requires minimum linux 3.2.
CVE References
description: | updated |
Changed in systemd (Ubuntu): | |
assignee: | nobody → Chris Coulson (chrisccoulson) |
Status changed to 'Confirmed' because the bug affects multiple users.