8.3-RELEASE-p4 will not shutdown after 30 second timer on APC usb UPS

[kepik]

FreeNAS: FreeBSD 8.3-RELEASE-p4 #3 r239131M
UPS: APC Smart-UPS 1500 USB only
Problem: FreeNAS will not initial shut down after the 30 second configured timer expires
Possible open bug ticket: 7846

Details

/var/log/messages for the duration of the test:

Sep 2 22:02:57 freenas upsmon[29573]: UPS ups on battery
Broadcast Message from root@freenas.local
(no tty) at 22:02 CDT...
UPS ups on battery
Sep 2 22:02:57 freenas upssched[31317]: read confirmation got [ERR UNKNOWN T" "30"]
Sep 2 22:02:57 freenas last message repeated 4 times
Sep 2 22:02:57 freenas upssched[31317]: read confirmation failed, trying again
Sep 2 22:02:57 freenas upssched[31317]: read confirmation got [ERR UNKNOWN T" "30"]
Sep 2 22:02:57 freenas last message repeated 4 times
Sep 2 22:02:57 freenas upssched[31317]: read confirmation failed, trying again
Sep 2 22:02:58 freenas upssched[31317]: read confirmation got [ERR UNKNOWN T" "30"]
Sep 2 22:02:58 freenas last message repeated 4 times
Sep 2 22:02:58 freenas upssched[31317]: read confirmation failed, trying again
Sep 2 22:02:58 freenas upssched[31317]: read confirmation got [ERR UNKNOWN T" "30"]
Sep 2 22:02:58 freenas last message repeated 6 times
Sep 2 22:02:58 freenas upssched[31317]: Unable to connect to daemon and unable to start daemon
Sep 2 22:06:42 freenas upsmon[29573]: UPS ups on line power

Broadcast Message from root@freenas.local
(no tty) at 22:06 CDT...
UPS ups on line power
Sep 2 22:06:42 freenas upssched[31363]: read confirmation got [ERR UNKNOWN TT" "ONLINE"]
Sep 2 22:06:42 freenas last message repeated 9 times
Sep 2 22:06:42 freenas upssched[31363]: read confirmation failed, trying again
Sep 2 22:06:43 freenas upssched[31363]: read confirmation got [ERR UNKNOWN TT" "ONLINE"]
Sep 2 22:06:43 freenas last message repeated 4 times
Sep 2 22:06:43 freenas upssched[31363]: read confirmation failed, trying again
Sep 2 22:06:43 freenas upssched[31363]: read confirmation got [ERR UNKNOWN TT" "ONLINE"]
Sep 2 22:06:43 freenas last message repeated 7 times
Sep 2 22:06:43 freenas upssched[31363]: Unable to connect to daemon and unable to start daemon

Some configuration details that may be relevant:

[root@freenas] ~# cat /usr/local/etc/nut/upssched.conf

CMDSCRIPT /usr/local/bin/custom-upssched-cmd
PIPEFN /var/db/nut/upssched.pipe
LOCKFN /var/db/nut/upssched.lock

AT COMMBAD * START-TIMER COMMBAD 10
AT COMMOK * CANCEL-TIMER COMMBAD COMMOK
AT FSD * EXECUTE FSD
AT LOWBATT * START-TIMER LOWBATT 30
AT LOWBATT * EXECUTE EMAIL
AT ONBATT * START-TIMER ONBATT 30
AT ONBATT * EXECUTE EMAIL
AT ONLINE * CANCEL-TIMER ONBATT ONLINE
AT ONLINE * CANCEL-TIMER LOWBATT ONLINE
AT REPLBATT * EXECUTE REPLBATT
AT SHUTDOWN * EXECUTE SHUTDOWN

[root@freenas] ~# cat /usr/local/etc/nut/upssched.conf

FINALDELAY 30
MONITOR ups 1 upsmon fixmepass master
NOTIFYCMD "/usr/local/sbin/upssched"
NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC
NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC
NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC
NOTIFYFLAG FSD SYSLOG+EXEC
NOTIFYFLAG SHUTDOWN SYSLOG+EXEC
SHUTDOWNCMD "/sbin/shutdown -p now"

[root@freenas] ~# cat /usr/local/etc/nut/upsmon.conf

[ups]
driver = usbhid-ups
port = /dev/ugen0.2
desc = ""

[root@freenas] ~# dmesg
ugen0.2: <American Power Conversion> at usbus0

Has anyone else run into this and is the ticket number above (the only one I could find on Bug Tracking Site regarding upssched)

 

[Stephens]

Can you update your title to the correct FreeNAS version? You've given the FreeBSD version, which isn't the same thing. The basic FreeNAS version shows up when you get the WebGUI login screen, and the full version shows up when you select Help in the WebGUI. For instance, one of mine is FreeNAS-8.0.4-RELEASE-p2-x64 (11367).

There are threads here already about this issue, but I don't remember the current status. My UPS doesn't shutdown my system either, but I've only tried it with 8.0.4, not 8.2 (or any of the 8.3 nightly releases).

 

[kepik]

Of course I had to forget the most important set of numbers:

​

FreeNAS-8.3.0-BETA1-x64 (r12054)

 

[William Grzybowski]

Seems like it is a bug in nut 2.6.4, wait for next BETA which will bring 2.6.5