Apcupsd exiting, signal 15


BobNik

Recommended Posts

HI,

Does anyone knows why I have these lines in my log? There are no errors before or after:

 

>>

Feb 14 03:55:41 Tower kernel: mdcmd (206): spindown 5
Feb 14 04:40:01 Tower apcupsd[27942]: apcupsd exiting, signal 15
Feb 14 04:40:01 Tower apcupsd[27942]: apcupsd shutdown succeeded
Feb 14 04:40:04 Tower apcupsd[14778]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded
Feb 14 04:40:04 Tower apcupsd[14778]: NIS server startup succeeded
Feb 14 05:41:50 Tower kernel: mdcmd (207): spindown 2

<<

 

Thank you

Link to comment

Found another instance of the log entries at exact same time one week ago. Must be some settings somewhere but what?

 

>>

Feb 7 04:40:01 Tower apcupsd[2165]: apcupsd exiting, signal 15

Feb 7 04:40:01 Tower apcupsd[2165]: apcupsd shutdown succeeded

Feb 7 04:40:04 Tower apcupsd[27942]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded

Feb 7 04:40:04 Tower apcupsd[27942]: NIS server startup succeeded

<<

Link to comment

Also have a couple instinces of this in my log:

 

Feb 14 04:40:01 Tower apcupsd[26901]: apcupsd exiting, signal 15
Feb 14 04:40:01 Tower apcupsd[26901]: apcupsd shutdown succeeded
Feb 14 04:40:04 Tower apcupsd[6799]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded
Feb 14 04:40:04 Tower apcupsd[6799]: NIS server startup succeeded

 

Maybe this happened when the apcupsd plugin was updated? Did you find anything out?

Link to comment
  • 1 month later...
  • 2 years later...

@BobNik @adminmat @ConnerVT @nraygun

 

Hi guys.  I was curious about this myself and here are some things that I found.

 

As you can guess the apcupsd daemon controls the UPS communication.  The number in brackets is the process ID of that daemon process.  It seems that, on a weekly basis, the old process [524] is destroyed (exited) and a new process [13221] is created.  Obviously your process numbers would be different from mine.

 

This weekly restart process is controlled by "logrotate".  You can find logrotate.conf in the "/etc" folder.  Basically the logrotate config file is run and then all scripts within the logrotate.d folder are run.

 

image.png.29230962a1ad1fd5cdcda5fb8ff48453.png

 

In the /etc/logrotate.d folder you'll see apcupsd which contains the following commands.  The rc.d is a folder that contains "run commands" for daemons.

 

image.png.547ce9579d0c6c97b5cddf2ca5beacba.png

 

More info here --> https://linux.die.net/man/8/logrotate and https://forums.unraid.net/topic/119894-resolved-problems-with-apcupsd-starting-at-regular-times-when-disabled/

 

The UPS Self Test is a test that the UPS performs on a regular basis and the apcupsd daemon simply posts the results to the log.  It's interesting my settings show SELFTEST = NO and yet my UPS still does a regular Self Test.  Maybe just a bug with apcupsd.  See this for more info about the Self Test --> https://www.apc.com/ca/en/faqs/FA405317/

 

Note below in the screenshots that everything in my settings jives with the logs especially the power failure at 6:50:34 lasting for 2 seconds.

 

image.png.8a76b5ce24f2140d47ba3194ae43eb1d.png

 

image.thumb.png.199f392220dcb1347e56884428e42b6b.png

 

image.png.d56a42280c1bf4a342308eb2fa410678.png

 

image.png.1b83a25cc92da5507284581a15058db9.png

Edited by TimTheSettler
Link to comment

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.