You are not logged in.

#1 2017-09-02 03:05:54

jlindgren
Member
Registered: 2011-02-27
Posts: 224

systemd-tmpfiles-setup failing after filesystem update

After a pacman -Syu tonight, which notably updated the filesystem package to 2017.08-1, systemd-tmpfiles-setup.service is failing:

Sep 01 22:31:49 white-knight systemd[1]: Starting Create Volatile Files and Directories...
Sep 01 22:31:49 white-knight systemd-tmpfiles[187]: [/usr/lib/tmpfiles.d/etc.conf:13] Duplicate line for path "/etc/resolv.conf", ignoring.
Sep 01 22:31:49 white-knight systemd-tmpfiles[187]: stat(/etc/resolv.conf) failed: No such file or directory
Sep 01 22:31:49 white-knight systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE
Sep 01 22:31:49 white-knight systemd[1]: Failed to start Create Volatile Files and Directories.
Sep 01 22:31:49 white-knight systemd[1]: systemd-tmpfiles-setup.service: Unit entered failed state.
Sep 01 22:31:49 white-knight systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.

I see that in /usr/lib/tmpfiles.d, both etc.conf (owned by systemd) and arch.conf (owned by filesystem) have entries for resolv.conf:

etc.conf:

L! /etc/resolv.conf - - - - ../usr/lib/systemd/resolv.conf

arch.conf:

C /etc/resolv.conf

Neither of these seems necessary for my system since /etc/resolv.conf is a symlink to /var/run/NetworkManager/resolv.conf.  And name resolution is working fine in spite of the failed systemd unit.

What's the best way to fix this error?  I imagine that removing the /etc/resolv.conf lines from both etc.conf and arch.conf files would be one way, but I hesitate to start editing stock config files without a better understanding of what they're doing.

Offline

#2 2017-09-02 23:30:07

loqs
Member
Registered: 2014-03-06
Posts: 11,218

Re: systemd-tmpfiles-setup failing after filesystem update

Offline

#3 2017-09-03 00:01:32

jlindgren
Member
Registered: 2011-02-27
Posts: 224

Re: systemd-tmpfiles-setup failing after filesystem update

Ah okay, guess I'm not the only one then.  I've just commented out the line in arch.conf for now.

Offline

Board footer

Powered by FluxBB