Problem/Bug report: slave says battery needs replacing when master doesn't, master apcupsd cannot be manually restarted

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Problem/Bug report: slave says battery needs replacing when master doesn't, master apcupsd cannot be manually restarted

apcupsd-4
The incident occurred when the master was being upgraded from Ubuntu
14.04 to 16.04.1 LTS

Master:
OS: Ubuntu 14.04 -> 16.04.1
UPS: Smart-UPS 620
cable: 940-0024C
apcupsd version: 3.14.10 -> 3.14.12

Slave:
OS: Debian 8
UPS: slave
apcupsd version: 3.14.12

The master was restarted during the OS upgrade. The slave gave the
normal "communications with UPS lost" message, then the restored
message, and, immediately, the "battery must be replaced" message. I
first saw the warning in email, but the events files from the master and
slave show what happened (several previous restarts included - the times
between master and slave are synchronised with ntp):

Master apcupsd.events
2016-06-03 11:01:21 +0800  apcupsd exiting, signal 15
2016-06-03 11:01:21 +0800  apcupsd shutdown succeeded
2016-06-03 11:04:02 +0800  apcupsd 3.14.10 (13 September 2011) debian
startup succeeded
2016-06-23 13:06:01 +0800  apcupsd exiting, signal 15
2016-06-23 13:06:01 +0800  apcupsd shutdown succeeded
2016-06-23 13:08:40 +0800  apcupsd 3.14.10 (13 September 2011) debian
startup succeeded
2016-07-05 18:33:28 +0800  apcupsd exiting, signal 15
2016-07-05 18:33:28 +0800  apcupsd shutdown succeeded
2016-07-05 18:36:25 +0800  apcupsd 3.14.10 (13 September 2011) debian
startup succeeded
2016-07-20 13:19:49 +0800  apcupsd exiting, signal 15
2016-07-20 13:19:49 +0800  apcupsd shutdown succeeded
2016-07-20 13:22:42 +0800  apcupsd 3.14.10 (13 September 2011) debian
startup succeeded
2016-08-11 18:39:27 +0800  apcupsd exiting, signal 15
2016-08-11 18:39:27 +0800  apcupsd shutdown succeeded
2016-08-11 18:42:17 +0800  apcupsd 3.14.10 (13 September 2011) debian
startup succeeded
2016-08-11 20:13:11 +0800  apcupsd exiting, signal 15
2016-08-11 20:13:11 +0800  apcupsd shutdown succeeded
2016-08-11 20:31:20 +0800  apcupsd 3.14.12 (29 March 2014) debian
startup succeeded
2016-08-11 20:39:14 +0800  apcupsd 3.14.12 (29 March 2014) debian
startup succeeded

Slave apcupsd.events
2016-06-03 11:01:50 +0800  Communications with UPS lost.
2016-06-03 11:04:05 +0800  Communications with UPS restored.
2016-06-23 13:06:03 +0800  Communications with UPS lost.
2016-06-23 13:08:43 +0800  Communications with UPS restored.
2016-07-05 18:34:19 +0800  Communications with UPS lost.
2016-07-05 18:36:29 +0800  Communications with UPS restored.
2016-07-20 13:20:35 +0800  Communications with UPS lost.
2016-07-20 13:22:45 +0800  Communications with UPS restored.
2016-08-11 18:40:18 +0800  Communications with UPS lost.
2016-08-11 18:42:24 +0800  Communications with UPS restored.
2016-08-11 20:13:25 +0800  Communications with UPS lost.
2016-08-11 20:23:25 +0800  Communications with UPS lost.
2016-08-11 20:31:20 +0800  Communications with UPS restored.
2016-08-11 20:38:25 +0800  Communications with UPS lost.
2016-08-11 20:39:20 +0800  Communications with UPS restored.
2016-08-11 20:39:20 +0800  UPS battery must be replaced.

But, as a test I tried restarting apcupsd on the master, it failed to
restart:
service apcupsd restart

master apcupsd.events shows:
2016-08-15 12:53:41 +0800  apcupsd exiting, signal 15
2016-08-15 12:53:41 +0800  apcupsd shutdown succeeded

slave apcupsd.events shows:
2016-08-15 12:53:54 +0800  Communications with UPS lost.


checking the service status:
service apcupsd status
‚óŹ apcupsd.service - LSB: Starts apcupsd daemon
    Loaded: loaded (/etc/init.d/apcupsd; bad; vendor preset: enabled)
    Active: active (exited) since Mon 2016-08-15 12:53:41 HKT; 1min 0s ago
      Docs: man:systemd-sysv-generator(8)
   Process: 15307 ExecStop=/etc/init.d/apcupsd stop (code=exited,
status=0/SUCCES
   Process: 15312 ExecStart=/etc/init.d/apcupsd start (code=exited,
status=0/SUCC

Aug 15 12:53:41 beluga apcupsd[15307]: Stopping UPS power management:
apcupsd.
Aug 15 12:53:41 beluga systemd[1]: Stopped LSB: Starts apcupsd daemon.
Aug 15 12:53:41 beluga systemd[1]: Starting LSB: Starts apcupsd daemon...
Aug 15 12:53:41 beluga apcupsd[1661]: apcupsd shutdown succeeded
Aug 15 12:53:41 beluga apcupsd[15312]: Starting UPS power management:
Aug 15 12:53:41 beluga apcupsd[15312]: A copy of the daemon is still
running.  I
Aug 15 12:53:41 beluga apcupsd[15312]: please wait about 5 seconds for
it to shu
Aug 15 12:53:41 beluga systemd[1]: Started LSB: Starts apcupsd daemon.

I'm unable to restart apcupsd on the master manually.

Rebooting the master, apcupsd starts, and a battery error is given by
the slave:
master apcupsd.events:
2016-08-15 13:03:29 +0800  apcupsd 3.14.12 (29 March 2014) debian
startup succeeded

slave apcupsd.events:
2016-08-15 13:03:36 +0800  Communications with UPS restored.
2016-08-15 13:03:36 +0800  UPS battery must be replaced.

So the new version of apcupsd on the master, installed with the OS
upgrade, appears to have a problem. How should I proceed with testing
further?


Thanks

Allan


------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Loading...