Nut upsuser - Apr 2013 - NOTIFYCMD and SHUTDOWNCMD do not work until Nut is restarted

Hi everybody,

I installed and configured Nut 2.4.3 on Debian Squeeze, using package. 
It monitors an MGE Pulsar 1500 UPS in standalone mode.

Here are parts of upsmon.conf :
SHUTDOWNCMD "/bin/bash /root/extinction.sh >> /var/log/ups/ups.log
2>>&1"
NOTIFYCMD "/bin/bash /usr/sbin/alerte.sh"
[...]
NOTIFYFLAG ONBATT	SYSLOG+EXEC

At startup, driver, upsd and upsmon start but when I pull off the line, 
a message is appended to syslog but no script is executed, nor 
SHUTDOWNCMD is called. To make things better, I must restart Nut :
invoke-rc.d nut restart

Trying to understand this behavior, i noticed the following lines in 
syslog at computer startup, pasted there[1] for convenience :

usb 3-1: New USB device found, idVendor=0463, idProduct=ffff
usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=4
usb 3-1: Product: Pulsar
usb 3-1: Manufacturer: MGE UPS SYSTEMS
usb 3-1: SerialNumber: 1Y3H34201
usb 3-1: configuration #1 chosen from 1 choice
[...]
/build/buildd-linux-2.6_2.6.32-48squeeze1-i386-F95osd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/hid/usbhid/hid-core.c:
usb_submit_urb(ctrl) failed
generic-usb 0003:0463:FFFF.0001: timeout initializing reports
generic-usb 0003:0463:FFFF.0001: hiddev0,hidraw0: USB HID v1.10 Device 
[MGE UPS SYSTEMS Pulsar] on usb-0000:00:0a.1-1/input0
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver

May the failure be linked to my issue ? What can I do to make Nut work 
as soon as my computer boots up ?

Thanks
Julien

[1] 
http://paste.leslamas.net/?4cde069bbd2be749#aEElgbt8heLLpZlC2R8GbVzJ711cBKmaQiJZP+0nyLw=

bonjour Julien

2013/4/11 Julien M?tairie <ruliane at ruliane.net>
> Hi everybody,
>
> I installed and configured Nut 2.4.3 on Debian Squeeze, using package. It
> monitors an MGE Pulsar 1500 UPS in standalone mode.
>
> Here are parts of upsmon.conf :
> SHUTDOWNCMD "/bin/bash /root/extinction.sh >>
/var/log/ups/ups.log 2>>&1"
> NOTIFYCMD "/bin/bash /usr/sbin/alerte.sh"
> [...]
> NOTIFYFLAG ONBATT       SYSLOG+EXEC
>
> At startup, driver, upsd and upsmon start but when I pull off the line, a
> message is appended to syslog but no script is executed, nor SHUTDOWNCMD is
> called. To make things better, I must restart Nut :
> invoke-rc.d nut restart
>
> Trying to understand this behavior, i noticed the following lines in
> syslog at computer startup, pasted there[1] for convenience :
>
> usb 3-1: New USB device found, idVendor=0463, idProduct=ffff
> usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=4
> usb 3-1: Product: Pulsar
> usb 3-1: Manufacturer: MGE UPS SYSTEMS
> usb 3-1: SerialNumber: 1Y3H34201
> usb 3-1: configuration #1 chosen from 1 choice
> [...]
> /build/buildd-linux-2.6_2.6.**32-48squeeze1-i386-F95osd/**
>
linux-2.6-2.6.32/debian/build/**source_i386_none/drivers/hid/**usbhid/hid-core.c:
> usb_submit_urb(ctrl) failed
> generic-usb 0003:0463:FFFF.0001: timeout initializing reports
> generic-usb 0003:0463:FFFF.0001: hiddev0,hidraw0: USB HID v1.10 Device
> [MGE UPS SYSTEMS Pulsar] on usb-0000:00:0a.1-1/input0
> usbcore: registered new interface driver usbhid
> usbhid: v2.6:USB HID core driver
>
> May the failure be linked to my issue ? What can I do to make Nut work as
> soon as my computer boots up ?
>
maybe.
can you reproduce this easily?
if so, what the result of "upsc <devname>":
1) just after the boot?
2) then, when you've pulled the line?

Arnaud
cheers,
-- 
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130411/11b3ba80/attachment.html>