Banana Pi Pro : Failed to start Login Service.


logicite
 Share

1 1

Recommended Posts

Hello everyone,

 

Looks like i have some issue after last upgrade. I'm using a Banana Pi Pro as a file server at home (with samba mainly).

The system is some kind of freezing after a few hours : i'm watching a movie and cannot go to the end of it. The system disappears from the network : no more access via samba/windows network, no more ssh, no more ping...

 

Fortunately i am logging remotly so i can see that the system is still working somehow because it goes on sending syslogs. Last syslog is (the system "froze" at 20:10) :

Feb  7 20:02:01 localhost CRON[3118]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb  7 20:05:01 localhost CRON[3149]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb  7 20:15:01 localhost CRON[3203]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb  7 20:16:09 localhost systemd[1]: systemd-logind.service: Watchdog timeout (limit 3min)!
Feb  7 20:17:39 localhost systemd[1]: systemd-logind.service: State 'stop-sigabrt' timed out. Terminating.
Feb  7 20:19:10 localhost systemd[1]: systemd-logind.service: State 'stop-sigterm' timed out. Killing.
Feb  7 20:20:40 localhost systemd[1]: systemd-logind.service: Processes still around after SIGKILL. Ignoring.
Feb  7 20:22:10 localhost systemd[1]: systemd-logind.service: State 'stop-final-sigterm' timed out. Killing.
Feb  7 20:23:40 localhost systemd[1]: systemd-logind.service: Processes still around after final SIGKILL. Entering failed mode.
Feb  7 20:23:40 localhost systemd[1]: systemd-logind.service: Unit entered failed state.
Feb  7 20:23:40 localhost systemd[1]: systemd-logind.service: Failed with result 'timeout'.
Feb  7 20:23:41 localhost systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
Feb  7 20:23:41 localhost systemd[1]: Stopped Login Service.
Feb  7 20:23:41 localhost systemd[1]: Starting Login Service...

And nothing after...

 

Any clue where i should be looking for a solution ??

Thank you for ideas.

 

 

My config :

dpkg -l | grep armbian :

ii  armbian-firmware                   5.38                                       all          Linux firmware
ii  armbian-tools-xenial               5.38                                       armhf        Armbian tools, Cubie bt utils
ii  hostapd                            2:2.6-4~armbian5.38+1                      armhf        IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator
ii  sunxi-tools                        1.4.2-2~armbian5.38+1                      armhf        tools for working with Allwinner (sunxi) ARM processors

 

Link to post
Share on other sites

Armbian is a community driven open source project. Do you like to contribute your code?

Hi again,

 

I found more in the logs today : repeting log regarding systemd-logind...

 

I'm stil searching. If you have any idea...

Thanks

Feb  9 15:12:57 localhost systemd[1]: Failed to start Login Service.
Feb  9 15:12:57 localhost systemd[1]: systemd-logind.service: Unit entered failed state.
Feb  9 15:12:57 localhost systemd[1]: systemd-logind.service: Failed with result 'timeout'.
Feb  9 15:12:57 localhost systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
Feb  9 15:12:57 localhost systemd[1]: Stopped Login Service.
Feb  9 15:12:57 localhost systemd[1]: Starting Login Service...
Feb  9 15:12:57 localhost systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE
Feb  9 15:14:36 localhost systemd[1]: systemd-logind.service: State 'stop-sigterm' timed out. Killing.
Feb  9 15:16:06 localhost systemd[1]: systemd-logind.service: Processes still around after SIGKILL. Ignoring.
Feb  9 15:17:45 localhost systemd[1]: systemd-logind.service: State 'stop-final-sigterm' timed out. Killing.
Feb  9 15:19:15 localhost systemd[1]: systemd-logind.service: Processes still around after final SIGKILL. Entering failed mode.
Feb  9 15:19:15 localhost systemd[1]: Failed to start Login Service.
Feb  9 15:19:15 localhost systemd[1]: systemd-logind.service: Unit entered failed state.
Feb  9 15:19:15 localhost systemd[1]: systemd-logind.service: Failed with result 'timeout'.
Feb  9 15:19:16 localhost systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
Feb  9 15:19:16 localhost systemd[1]: Stopped Login Service.
Feb  9 15:19:16 localhost systemd[1]: Starting Login Service...
Feb  9 15:19:16 localhost systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE
Feb  9 15:20:54 localhost systemd[1]: systemd-logind.service: State 'stop-sigterm' timed out. Killing.
Feb  9 15:22:25 localhost systemd[1]: systemd-logind.service: Processes still around after SIGKILL. Ignoring.
Feb  9 15:24:04 localhost systemd[1]: systemd-logind.service: State 'stop-final-sigterm' timed out. Killing.
Feb  9 15:25:34 localhost systemd[1]: systemd-logind.service: Processes still around after final SIGKILL. Entering failed mode.
Feb  9 15:25:34 localhost systemd[1]: Failed to start Login Service.
Feb  9 15:25:34 localhost systemd[1]: systemd-logind.service: Unit entered failed state.
Feb  9 15:25:34 localhost systemd[1]: systemd-logind.service: Failed with result 'timeout'.
Feb  9 15:25:34 localhost systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
Feb  9 15:25:34 localhost systemd[1]: Stopped Login Service.
Feb  9 15:25:34 localhost systemd[1]: Starting Login Service...

 

Link to post
Share on other sites

I tried this to get some status information :

$ sudo systemctl status systemd-logind
● systemd-logind.service - Login Service
   Loaded: loaded (/lib/systemd/system/systemd-logind.service; static; vendor preset: enabled)
   Active: deactivating (final-sigterm) (Result: timeout) since ven. 2018-02-09 14:15:01 CET; 1h 27min ago
     Docs: man:systemd-logind.service(8)
           man:logind.conf(5)
           http://www.freedesktop.org/wiki/Software/systemd/logind
           http://www.freedesktop.org/wiki/Software/systemd/multiseat
  Process: 19171 ExecStart=/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
 Main PID: 19171 (code=exited, status=1/FAILURE)
   Status: "Shutting down..."
   CGroup: /system.slice/systemd-logind.service
           └─691 /lib/systemd/systemd-logind

févr. 09 15:38:11 sharing systemd[1]: Stopped Login Service.
févr. 09 15:38:11 sharing systemd[1]: Starting Login Service...
févr. 09 15:38:11 sharing systemd-logind[19171]: Failed to register name: File exists
févr. 09 15:38:11 sharing systemd-logind[19171]: Failed to fully start up daemon: File exists
févr. 09 15:38:11 sharing systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE
févr. 09 15:39:49 sharing systemd[1]: systemd-logind.service: State 'stop-sigterm' timed out. Killing.
févr. 09 15:41:19 sharing systemd[1]: systemd-logind.service: Processes still around after SIGKILL. Ignoring.

 

And if i want to reload, it fails (probably because de "file exists" : looks like there are several 'daemons' running at the same time ?) :

$ sudo systemctl reload systemd-logind
Failed to reload systemd-logind.service: Job type reload is not applicable for unit systemd-logind.service.
See system logs and 'systemctl status systemd-logind.service' for details.

So i did not hesitate and issue a stop command :

$ sudo systemctl stop systemd-logind

And now nothing, no prompt ! By the way remote log shows that the OS is still working (logging the same failure again and again).

Link to post
Share on other sites

  • Igor locked this topic
Guest
This topic is now closed to further replies.
 Share

1 1