You are not logged in.

#1 2013-06-04 08:09:32

stryder
Member
Registered: 2009-02-28
Posts: 498

failed to start login service

I have a simple system set up in virtualbox, mostly to browse and torrent. Rarely have major problems. Recently I realized that cron was not working when flexget was not activated as expected. A check of journalctl threw up repeated instances of the following:

Jun 04 15:41:11 arch32VB systemd[1]: systemd-logind.service operation timed out. Terminating.
Jun 04 15:41:11 arch32VB systemd[1]: Failed to start Login Service.
Jun 04 15:41:11 arch32VB systemd[1]: Unit systemd-logind.service entered failed state.
Jun 04 15:41:11 arch32VB systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Jun 04 15:41:11 arch32VB systemd[1]: Stopping Login Service...
Jun 04 15:41:11 arch32VB systemd[1]: Starting Login Service...
Jun 04 15:41:11 arch32VB systemd-logind[665]: Watching system buttons on /dev/input/event3 (Power Button)
Jun 04 15:41:11 arch32VB systemd-logind[665]: Watching system buttons on /dev/input/event4 (Sleep Button)
Jun 04 15:41:11 arch32VB systemd-logind[665]: New seat seat0.
Jun 04 15:41:11 arch32VB systemd-logind[665]: New session 1 of user calvin.
Jun 04 15:42:41 arch32VB systemd[1]: systemd-logind.service operation timed out. Terminating.
Jun 04 15:42:41 arch32VB systemd[1]: Failed to start Login Service.
Jun 04 15:42:41 arch32VB systemd[1]: Unit systemd-logind.service entered failed state.
Jun 04 15:42:41 arch32VB systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Jun 04 15:42:41 arch32VB systemd[1]: Stopping Login Service...
Jun 04 15:42:41 arch32VB systemd[1]: Starting Login Service...
Jun 04 15:42:41 arch32VB systemd-logind[693]: Watching system buttons on /dev/input/event3 (Power Button)
Jun 04 15:42:41 arch32VB systemd-logind[693]: Watching system buttons on /dev/input/event4 (Sleep Button)
Jun 04 15:42:41 arch32VB systemd-logind[693]: New seat seat0.
Jun 04 15:42:41 arch32VB systemd-logind[693]: New session 1 of user calvin.

I use autologin to console (and then to X via bash_profile) and there is no glitch except that I find that getting to desktop takes a little longer these days. Thought it is due to psd. I have no idea when this happened as things have been OK.

Any advice? I suspect that cron's failure is due to this issue though honestly I have no basis to think so. Systemctl shows cronie.service loaded and running. System is up to date.

Offline

#2 2013-06-06 06:36:20

stryder
Member
Registered: 2009-02-28
Posts: 498

Re: failed to start login service

With all the changes over the past year, I have been wanting to set up a fresh installation to remove any old issues that might not have been properly dealt with over time. This current issue, and the fact that the move to consolidate everything to /usr/bin has happened, tilted the balance.

New installation, login is OK, no repeated messages from systemd-logind, cronie is working.

Why the problems, I have no idea. But the new installation is working well.

Offline

#3 2014-03-01 12:00:57

leha2000
Member
Registered: 2013-10-18
Posts: 4

Re: failed to start login service

Before systemd this problem was not exist sad
At present old systems cannot be updated similar Windows, and must be reinstalling???

This is very sad:(

Offline

#4 2014-03-01 15:43:07

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 13,411

Re: failed to start login service

Closing this thread.
It never gained any traction.  It is an old thread.  The assertion in the previous thread is incorrect.  And, I believe, the OP dealt with it with a re-install.  Not much point in continuing.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
You assume people are rational and influenced by evidence.  You must not work with the public much. -- Trilby
----
How to Ask Questions the Smart Way

Online

Board footer

Powered by FluxBB