Skip to main content

Failed to create session: Failed to activate service 'org.freedesktop.login1': timed out

Comments

3 comments

  • WasChristine
    The server has performed an update recently and appears is now in need of a re-boot (this is why I'm not fond of auto-updates) I'm seeing tons of these errors echoed in var/log/lfd.log and assume it's related, so I'll be performing the reboot out of hours. Nov 18 13:00:26 xxxxxxx crond[25540]: pam_systemd(crond:session): Failed to create session: Failed to activate service 'org.freedesktop.login1': timed out Nov 18 13:01:26 xxxxxxx crond[25949]: pam_systemd(crond:session): Failed to create session: Connection timed out
    Any ideas what these relate to ? I also had problems accessing the server via SFTP this morning, maybe also related ??

    Hello, This issue generally loops back to the systemd-logind service. The service could experience problems for various reasons. A user in
    0
  • keat63
    The server performed an automated update which required a reboot (yellow - please reboot banner) The reboot seems to have resolved the issue. I don't like auto updates for this exact reason. If I have to connect out of hours to perform a reboot, I might as well connect out of hours to perform the update. It doesn't save any time. I rebooted it last night, it's performed another update at 4am, so I'll have to reboot it again tonight.
    0
  • WasChristine
    Greetings, Thank you for getting back to us. You could disable updates manually through the
    0

Please sign in to leave a comment.