On Fri, Jul 20, 2018 at 10:35 AM Pacal Mario <[email protected]> wrote:
> Dear sirs and madams, > > > > Apology in advance if contacting this mailing list was the wrong thing to > do. > > If so, please advise me on where to find answers for my system related > problem. > > > > I am seeking assistance in the underlying problem’s root cause analysis > caused by an unknown source. > > As well as the risk of just restarting the service system-logind1 and if > this would resolve my issue. Same goes for a whole server restart. > > > > Since it seems that org.freedesktop.systemd1 as the only bus service > cannot be started properly, this > > problem is quite specific. I posted this issue within linus forums, though > thinking the issue cannot be solved > > easily by only user based knowledge. > org.freedesktop.systemd1 is not meant to be startable on-demand – it's the bus name of init (pid 1) itself. If you're missing it, then either systemd couldn't connect to the bus for some reason (try 'kill -USR1 1`) or your pid 1 is not actually systemd. -- Mantas Mikulėnas
_______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
