FS#55467 - [filesystem] [systemd] New arch.conf file seems to cause systemd-tmpfiles-setup.service to fail
Attached to Project:
Arch Linux
Opened by ignoreme (ignoreme) - Saturday, 02 September 2017, 08:22 GMT
Last edited by Sébastien Luttringer (seblu) - Sunday, 03 September 2017, 21:45 GMT
Opened by ignoreme (ignoreme) - Saturday, 02 September 2017, 08:22 GMT
Last edited by Sébastien Luttringer (seblu) - Sunday, 03 September 2017, 21:45 GMT
|
Details
Description: New arch.conf file seems to cause
systemd-tmpfiles-setup.service to fail
Additional info: * 2017-08-1 * /usr/lib/tmpfiles.d/arch.conf item conflicts with /usr/lib/tmpfiles.d/etc.conf item Steps to reproduce: Install latest testing version of filesystem. The addition of the /usr/lib/tmpfiles.d/arch.conf file contains this line C /etc/resolv.conf This conflicts with /usr/lib/tmpfiles.d/etc.conf L! /etc/resolv.conf - - - - ../usr/lib/systemd/resolv.conf and causes the systemd-tmpfiles-setup.service to fail to start Sep 02 00:00:33 hostname systemd-tmpfiles[337]: [/usr/lib/tmpfiles.d/etc.conf:13] Duplicate line for path "/etc/resolv.conf", ignoring Sep 02 00:00:33 hostname systemd-tmpfiles[337]: stat(/etc/resolv.conf) failed: No such file or directory Sep 02 00:00:33 hostname systemd-udevd[248]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Sep 02 00:00:33 hostname systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Sep 02 00:00:33 hostname systemd[1]: Failed to start Create Volatile Files and Directories. Sep 02 00:00:33 ihostname systemd[1]: systemd-tmpfiles-setup.service: Unit entered failed state. Sep 02 00:00:33 hostname systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Sunday, 03 September 2017, 21:45 GMT
Reason for closing: Fixed
Additional comments about closing: filesystem-2017.09-1
Sunday, 03 September 2017, 21:45 GMT
Reason for closing: Fixed
Additional comments about closing: filesystem-2017.09-1
└───╼ systemctl status systemd-tmpfiles-setup.service
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)
Active: active (exited) since Sat 2017-09-02 10:09:00 CEST; 1h 17min ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 1181 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=0/SUCCESS)
Main PID: 1181 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/systemd-tmpfiles-setup.service
sep 02 10:09:00 sL1pKn07 systemd[1]: Starting Create Volatile Files and Directories...
sep 02 10:09:00 sL1pKn07 systemd-tmpfiles[1181]: [/usr/lib/tmpfiles.d/etc.conf:13] Duplicate line for path "/etc/resolv.conf", ignoring.
sep 02 10:09:00 sL1pKn07 systemd[1]: Started Create Volatile Files and Directories.
when /etc/resolv.conf is a sym link to run/systemd/resolve/resolv.conf appears to be a possible bug to me in systemd-tmpfiles-setup
cat /etc/systemd/system/systemd-tmpfiles-setup.service.d/override.conf
[Unit]
After=
After=local-fs.target systemd-sysusers.service systemd-resolved.service
And that didn't work so gonna look for something else.
# stat /alink
File: /alink -> /foobar
Size: 7 Blocks: 0 IO Block: 4096 symbolic link
Device: fe00h/65024d Inode: 16 Links: 1
Access: (0777/lrwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2017-09-02 20:18:28.570091125 +0000
Modify: 2017-09-02 20:18:28.570091125 +0000
Change: 2017-09-02 20:18:28.570091125 +0000
Birth: -
# stat /foobar
stat: cannot stat '/foobar': No such file or directory
# touch /usr/share/factory/etc/
# cat /etc/tmpfiles.d/test.conf
C /alink
# systemd-tmpfiles --create
stat(/alink) failed: No such file or directory
At least the error message is wrong or systemd-tmpfiles appears to have mistakenly followed the targets link.
Edit:
added missing output for stat /foobar