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.

Double logs from powerdown package.

Featured Replies

I don't see why I should be the only person experiencing this problem, but I cannot find any reference to it.

 

Whenever my unRAID server is shut down by apcupsd, or other mechanisms which invoke the powerdown package (issuing the powerdown command, or pushing the power button), I get two log files saved to my usb drive.  The first one has one set of diagnostic/status results, the second one has two sets of diagnostic/status results.  It seems that unRAID_stop is being invoked twice.

 

If I issue /etc/rc.d/rc,unRAID stop manually, then I get one logfile, if I then issue the /sbin/shutdown command, I get a second logfile, with double diagnostics/status results.

 

Looking at the /sbin/powerdown script, it appears that once upon a time, it ended with /sbin/poweroff.  It has subsequently been modified to end with /sbin/shutdown.

 

Do the double logs get created because of the use of the shutdown utility instead of poweroff?  If I reverted to poweroff, would the double logs go away?  Why was the script changed to use shutdown?

 

Or, is the double log a result of the 'sysctl -w kernel.poweroff_cmd=/sbin/powerdown' included in the install script?

 

What is the best solution for preventing the double logfiles?

 

If I stop the system from the web interface, and reboot, I only get a single logfile.

 

 

Edit:

A quick experiment shows that the double logging occurs whether poweroff or shutdown is used.

 

Further investigation shows that the '/etc/rc.d/rc.unRAID stop' command is added to '/etc/rc.d/rc.local_shutdown'.  This being the case, I suspect that the command should not also be invoked by the '/sbin/powerdown' script.

 

Edit 2:

I've commented out the 'etc/rc.d/rc.unRAID stop' line in the '/sbin/powerdown' script and my initial test (a short press on the power button) would seem to suggest that the shutdown is now behaving correctly.

  • Author
I've commented out the 'etc/rc.d/rc.unRAID stop' line in the '/sbin/powerdown' script and my initial test (a short press on the power button) would seem to suggest that the shutdown is now behaving correctly.

 

Since making this change, powerdown seems to be behaving exactly as I would expect - no more double logging and, in all circumstances I've tried, the system shuts down correctly and stores one copy of the logfile with all the diagnostic/status information.

 

I've tried: Short press of power button, apcupsd-driven shutdown, shutdown and reboot typed at the console, stop followed by reboot on the web interface.

 

Who is the originator/current maintainer of the powerdown package?  I really believe that that my change is an improvement!

  • 1 year later...

I did some configuration stuff yesterday and also noticed this double entries in the logfile.

Therefore I'm bumping this and perhaps Joe L will see it...

I will also do the suggested change in the script.

 

I did some configuration stuff yesterday and also noticed this double entries in the logfile.

Therefore I'm bumping this and perhaps Joe L will see it...

I will also do the suggested change in the script.

 

There's a new version of Powerdown that fixes this problem and others.

Yes, just read through the recent posts... :D

 

Here is the thread.

 

Now an update of unMENU would come in handy...

Archived

This topic is now archived and is closed to further replies.

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.