Suppress UPS "Communication Lost" Notification When Caused by Scheduled Logrotate Restart

Background:

Unraid includes apcupsd by default, and /etc/logrotate.d/apcupsd is configured to rotate /var/log/apcupsd.events weekly on Sundays at 4:40am via cron. This rotation triggers a restart of apcupsd, which results in a brief "Communications with UPS lost" message in the syslog.

Jun 22 04:40:02 Tower rc.apcupsd: Restarting APC-UPS Power Management...
Jun 22 04:40:03 Tower rc.apcupsd: Stopping APC-UPS Power Management...
Jun 22 04:40:03 Tower apcupsd[3181830]: apcupsd exiting, signal 15
Jun 22 04:40:03 Tower rc.apcupsd: APC-UPS Power Management...  Failed.
Jun 22 04:40:03 Tower apcupsd[3181830]: Communications with UPS lost.
Jun 22 04:40:03 Tower kernel: usb 1-5: reset full-speed USB device number 4 using xhci_hcd
Jun 22 04:40:03 Tower apcupsd[3181830]: apcupsd shutdown succeeded
Jun 22 04:40:04 Tower rc.apcupsd: Starting APC-UPS Power Management...
Jun 22 04:40:04 Tower rc.apcupsd: APC-UPS Power Management...  Started.
Jun 22 04:40:04 Tower apcupsd[2135584]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded
Jun 22 04:40:04 Tower apcupsd[2135584]: NIS server startup succeeded

Problem:

Unraid then generates a critical alert notification, even though this is a normal, expected event caused by the built-in log rotation. This is a confusing and unnecessary alert for users who have not actually experienced a UPS failure. Users expect to be alerted only for real UPS communication failures. False positives reduce trust in the alerting system and cause unnecessary concern. I personally have spent many hours trying to figure out what is causing this and whether I need to worry about it and I've come across a bunch of threads with other users inquiring about the same thing.

Unraid Notification:

Feature Request:

Please suppress the "Communication with UPS lost" notification when the event occurs at the known scheduled restart time (e.g., Sunday 4:40am daily) caused by logrotate.

This could be achieved by:

- Temporarily suppressing the commfailure event in apccontrol if it occurs in a small window around 4:40am

- Or modifying the notification system to ignore this specific expected logrotate-triggered restart

Thank you for considering!

Edited June 29, 20251 yr by tallguydirk
formatting