Павел Мотырев
2017-02-15 19:50:05 UTC
Hello, Stan.
I think this is not the same problem - bug is not related to system
shutdown process.
On host with apcupsd (powered _not_ from UPS) I executed "tcpdump -pni
eth0 host <ups-ip>" in one terminal and "touch /etc/apcupsd/powerfail
&& apcupsd --killpower" in another.
As you can see in tcpdump output in my previous message, apcupsd sent
SNMP-packet to UPS, but UPS answered with error, because SNMP OID is
incorrect.
Regards,
Pavel Motyrev
I think this is not the same problem - bug is not related to system
shutdown process.
On host with apcupsd (powered _not_ from UPS) I executed "tcpdump -pni
eth0 host <ups-ip>" in one terminal and "touch /etc/apcupsd/powerfail
&& apcupsd --killpower" in another.
As you can see in tcpdump output in my previous message, apcupsd sent
SNMP-packet to UPS, but UPS answered with error, because SNMP OID is
incorrect.
Regards,
Pavel Motyrev
Hi
See: https://bugs.launchpad.net/ubuntu/+source/apcupsd/+bug/1634572
This has been a big problem for many Ubuntu 16.04 users
Not sure if its the exact same problem, because the bug is related to
USB UPS's as far as i know. But i know that it does not send Killpower
to UPS.
Express your concern there as well so that the Ubuntu developers may fix
the issue.
Regards,
Stan
See: https://bugs.launchpad.net/ubuntu/+source/apcupsd/+bug/1634572
This has been a big problem for many Ubuntu 16.04 users
Not sure if its the exact same problem, because the bug is related to
USB UPS's as far as i know. But i know that it does not send Killpower
to UPS.
Express your concern there as well so that the Ubuntu developers may fix
the issue.
Regards,
Stan