- Minor
I primarily use the NUT plugin for UPS control, and leave the baked in UPS monitor alone, however have had two instances now where I wake up to emails/errors about UPS lost communication. System was last started up/reset on 4/6/19 and first saw the issue on 4/14:
Apr 14 04:40:04 OCHO apcupsd[547]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded
Apr 14 04:40:04 OCHO apcupsd[547]: NIS server startup succeeded
Apr 14 04:40:04 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 14 04:40:09 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 14 04:40:14 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 14 04:40:19 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 14 04:40:24 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 14 04:40:29 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 14 04:40:34 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 14 04:40:39 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 14 04:40:44 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 14 04:40:49 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 14 04:40:54 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 14 04:40:59 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 14 04:41:04 OCHO apcupsd[547]: Communications with UPS lost.
The usbfs error continues on w/ the communications lost notification until I addressed the issue.
Found my dashboard had the UPS plugin running, went into settings and found it started w/ gui setting set to off. a quick toggle of the settings and all was well again & dashboard panel went away.
Now again last night (4/21/19)
Apr 21 04:40:04 OCHO apcupsd[2116]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded
Apr 21 04:40:04 OCHO apcupsd[2116]: NIS server startup succeeded
Apr 21 04:40:04 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 21 04:40:09 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 21 04:40:14 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 21 04:40:19 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 21 04:40:24 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 21 04:40:29 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 21 04:40:34 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 21 04:40:39 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 21 04:40:44 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 21 04:40:49 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 21 04:40:54 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 21 04:40:59 OCHO kernel: usb 2-1.1: usbfs: interface 0 claimed by usbfs while 'apcupsd' sets config #1
Apr 21 04:41:04 OCHO apcupsd[2116]: Communications with UPS lost.
Exactly 7 days to the second, we get another myster startup.
I dont have any user scripts running that would call apcupsd, but i do see my "fixed schedules" set to run daily scripts at 440a. But apcupsd doesnt start up daily, only weekly which is set to run at 430a on Sundays.