Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

A Service Called "elogind" Apparently Initiates a Shutdown Multiple Times per Week

Featured Replies

I think I might be revealing how little I really know, here, but I'm at a loss after pulling out my hair for two weeks on this. I posted this on Reddit and received a bit of help in better diagnosing the issue, but still no solutions.

 

My Server (Unraid 6.11.5) has been a touch unreliable for a few months now, but as I live offsite and keep it at home with my parents, I chalked it up to a power issue, and haven't really bothered to dig too deeply. Until now.

 

I always access my system remotely via Wireguard. As of about three months ago, it started going down once or twice a week. When I was home for Christmas for two weeks, it didn't go down once. But after I came back about two weeks ago, it began shutting down every 1-3 days. So I turned on persistent logging, and now I can see that it isn't crashing or losing power, it's being shut down.

I do not have a UPS.

 

The log has the following line preceding every shutdown, with a different PID every time:

 

Jan 25 17:54:39 Halcyon  shutdown[13541]: shutting down for system halt

 

I also set up a script that sends me the output of "ps auxef" in a .txt file, a list of all PIDs currently running. I can cross-reference that with the log to figure out what the PID is of the service initiating the shutdown.

 

root      1151  0.0  0.0   6320  2484 ?        S    Jan23   0:00 elogind-daemon SHELL=/bin/sh RUNLEVEL=3 PWD=/ HOME=/ TERM=linux INIT_VERSION=sysvinit-2.99 SHLVL=2 BOOT_IMAGE=/bzimage CONSOLE=/dev/console PREVLEVEL=N PATH=/bin:/sbin:/usr/bin:/usr/sbin _=/lib64/elogind/elogind
root     13541  0.0  0.0      0     0 ?        Z    17:54   0:00  \_ [init] <defunct>

 

To me, this means that PID 1151 spawns PID 13541  to initiate the shutdown, which then terminates itself. Some googling around helped me to understand that elogind handles user logins, sessions, and power-related actions like shutdowns, suspends, and reboots. Short of that though, I haven't been able to figure out where to go from here.

 

I'll also include the syslog, output of the most recent ps auxef, elogind/login.conf, and Diagnostics Zip File

Any help would be much appreciated!

  • Author
10 hours ago, JorgeB said:

Please post the diagnostics.

Hi, I’m pretty sure that I did, in the last line of the post. Is there a different diagnostics that I need?

  • Community Expert

I missed the external link, but next time just attach to the post.

 

Nothing obvious in the logs, the two main suspects would be a plugin/script or bad power button, you can reboot in safe mode and disconnect the power switch from the board to retest.

 

 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.