Systemd failed to restart [Solved]

fluancefg · 2019-05-09 14:30:29

I've updated the system with pacman -Suy, which has installed systemd-242.19-1.
During the update, I get a message

Failed to reload daemon: Access denied

I was force to downgrade systemd to 239.0-2, otherwise I was not able to restart or shutdown the machine anymore.

Does anyone know how to investigate or fix this issue ?

Last edited by fluancefg (2019-05-10 14:21:10)

Trilby · 2019-05-09 14:50:53

Please post the full output - out of context that message doesn't say much. Post your pacman.log if you don't have the output anymore.

As for restarting/shutting down, what do you mean you are not able to? What error or output does that produce?

fluancefg · 2019-05-09 15:04:59

Here's what inside pacman.log.

[2019-05-09 16:58] [ALPM] transaction started
[2019-05-09 16:58] [ALPM] upgraded libidn (1.34-2 -> 1.35-1)
[2019-05-09 16:58] [ALPM] upgraded systemd (239.0-2 -> 242.19-1)
[2019-05-09 16:58] [ALPM-SCRIPTLET] Failed to reload daemon: Access denied
[2019-05-09 16:58] [ALPM] upgraded systemd-sysvcompat (239.0-2 -> 242.19-1)
[2019-05-09 16:58] [ALPM] transaction completed

When I try to run shutdown or reboot, I get the following message:

Failed to power off system via logind: Unit systemd-poweroff.service has a bad unit file setting.
Failed to talk to init daemon.

or

Failed to reboot system via logind: Unit systemd-reboot.service has a bad unit file setting.
Failed to talk to init daemon.

jasonwryan · 2019-05-09 17:37:25

Post the full pacman log, not a tiny excerpt: https://bbs.archlinux.org/viewtopic.php?id=57855

fluancefg · 2019-05-10 06:48:03

http://ix.io/1Iz3

Trilby · 2019-05-10 12:26:01

That is still not the full log. But the most likely problem is readily apparent: you have a long history of partial upgrades.

Please post your full pacman log and your pacman.conf

fluancefg · 2019-05-10 12:43:49

I don't know what you mean with "you have a long history of partial upgrades".

pacman.log: http://ix.io/1IAN
pacman.conf: http://ix.io/1IAO

Trilby · 2019-05-10 12:49:06

Your log is litterally littered with them along with evidence that pacman (or yaourt in your case) frequently fails an you repeatedly retry over and over again.

https://wiki.archlinux.org/index.php/Sy … nsupported

You are also using a completely broken repo. I'd like to help, but frankly you've dug yourself in such a hole I'm not sure where to start. As a hail mary, I'd remove archlinux.fr and everything from that repo, do a full and proper upgrade, then restart with a hard poweroff if necessary and see if you're back in functional shape. If not, reinstall and partial upgrade no more.

fluancefg · 2019-05-10 14:20:21

I've removed the archlinux.fr repo and the yaourt tool btw. Then I've done a full upgrade and everything is working fine.

Trilby · 2019-05-10 15:16:46

That's a good outcome. I'm glad it panned out that way. Going forward, please never use the -Sy flag to pacman without also including a 'u'. Additionally, while it will not harm your system, needless use of two 'y's is just a waste of mirror resources for no purpose. The proper command for regular updates is simply `pacman -Syu`.

Arch Linux

#1 2019-05-09 14:30:29

Systemd failed to restart [Solved]

#2 2019-05-09 14:50:53

Re: Systemd failed to restart [Solved]

#3 2019-05-09 15:04:59

Re: Systemd failed to restart [Solved]

#4 2019-05-09 17:37:25

Re: Systemd failed to restart [Solved]

#5 2019-05-10 06:48:03

Re: Systemd failed to restart [Solved]

#6 2019-05-10 12:26:01

Re: Systemd failed to restart [Solved]

#7 2019-05-10 12:43:49

Re: Systemd failed to restart [Solved]

#8 2019-05-10 12:49:06

Re: Systemd failed to restart [Solved]

#9 2019-05-10 14:20:21

Re: Systemd failed to restart [Solved]

#10 2019-05-10 15:16:46

Re: Systemd failed to restart [Solved]

Board footer