Hi Michael Followed your suggestions and a reboot but still seeing NGINX-SSL Proxy as not running (while it is actually running according to service nginx status (and restart every 15 minutes by swatch because it thinks it's not running)
PS -aux still shows: dbus 820 0.0 0.0 58088 2380 ? Ss 14:45 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation and the systemctl command: systemctl list-unit-files shows all files correctly (I think) [root@xxx admin]# systemctl daemon-reexec [root@xxx admin]# systemctl --user list-unit-files Failed to get D-Bus connection: No such file or directory Any more suggestions? Many thanks Janwillem From: Blueonyx <blueonyx-boun...@mail.blueonyx.it> on behalf of Michael Stauber <mstau...@blueonyx.it> Organization: Team BlueOnyx (www.blueonyx.it) Reply-To: BlueOnyx General Mailing List <blueonyx@mail.blueonyx.it> Date: Wednesday, 22. August 2018 at 15:36 To: <blueonyx@mail.blueonyx.it> Subject: [BlueOnyx:22345] Re: sysetmctl dbus errors after automatic updates Hi Jochen, Yeah. There was a Systemd update in that last batch of updates. Failed to get D-Bus connection: Too many levels of symbolic links There ware two things to check: 1.) Please check if /var/run is a symbolic link to /run and most likely it is not. The typical fix is to do this: rm -R /var/run ln -s /run /var/run 2.) Check if /run/dbus/system_bus_socket is a Symbolic link to /var/run/dbus/system_bus_socket. That should also not be the case. If it is, do the following: rm /run/dbus/system_bus_socket rm -R /var/run ln -s /run /var/run And yes: There is then no way around a reboot after either one of these two. :-/ -- With best regards Michael Stauber _______________________________________________ Blueonyx mailing list Blueonyx@mail.blueonyx.it http://mail.blueonyx.it/mailman/listinfo/blueonyx
_______________________________________________ Blueonyx mailing list Blueonyx@mail.blueonyx.it http://mail.blueonyx.it/mailman/listinfo/blueonyx
