[Nut-upsuser] newhidups fails only at boot

[Jon Gough]

Is this a problem with the UDEV sequence? ie in /etc/udev/rules.d are 
the nut udev rules the last ones to execute? I found that I had to do 
this to get around a permissions problem during boot.

Jon

At 06:00 17/04/2007, Peter Selinger wrote:
>Could it be a permissions problem? Perhaps the USB devices are not yet
>owned by the correct user during boot? -- Peter
>
>Jim Osborn wrote:
> >
> > I can start the driver successfully manually, after the machine is up
> > and running, but at boot time, it can't find my UPS. My init script
> > makes sure that the usbfs is up (by checking for the existence of
> > /proc/bus/usb/devices), and I can't think of what else could be
> > different with the boot-time failure versus the manual startup after
> > logging in.  I'll include my configuration at the end of this note.
> > Here's the log of the boot failure:
> >
> > Sun Apr 15 21:49:48 PDT 2007 /etc/init.d/rc3.d/S09ups: Starting 
> ups driver (-DDDDD)
> > Sun Apr 15 21:49:48 PDT 2007 /etc/init.d/rc3.d/S09ups: USB 
> filesystem is mounted
> > Starting UPS: ups
> > exec: //bin/newhidups -a ups
> > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5)
> >
> > No matching HID UPS found
> > Driver failed to start (exit status=1)
> > Network UPS Tools - UPS driver controller 2.0.5
> >
> > Here are my config files:
> >
> > /etc/ups/ups.conf:
> > [ups]
> >       driver = newhidups
> >       port = auto
> >       desc = "My Little APC Back-UPS ES 750"
> >
> > /etc/hotplug/usb/libhidups:
> > if [ "$ACTION" = "add" -a "$TYPE" = "usb" ]; then
> >   chown root:nut "$DEVICE"
> >   chmod 0664 "$DEVICE"
> > fi
> >
> > Here's my init script, which runs in runlevel 3:
> >
> > case "$1" in
> >   start)
> >       echo "`date` ${0}: Starting ups driver (-DDDDD)" >>$log
> >       if [ -f /proc/bus/usb/devices ]; then
> >               echo "`date` ${0}: USB filesystem is mounted" >>$log
> >       else
> >               echo "`date` ${0}: Mounting the USB filesystem" >>$log
> >               modprobe usbcore
> >               mount -t usbfs usbfs /proc/bus/usb
> >               [ -f /proc/bus/usb/devices ] ||
> >                       echo "`date` ${0}: cannot mount the USB 
> filesystem" >>$log
> >       fi
> >
> >       /bin/upsdrvctl -DDDDD start ups >>$log 2>&1
> >       ...
> >
> >
> > The only runlevel 3 init script that runs after ups is nfs.
> >
> > System details:
> > Linux kernel 2.4.32
> > UPS: APC Back-UPS ES 750
> >
> > Fwiw, here's a log of a manual driver startup:
> >
> > Starting UPS: ups
> > exec: //bin/newhidups -a ups
> > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5)
> >
> > Detected a UPS: APC/Back-UPS ES 750 FW:819.z3.D USB FW:z3
> > Using subdriver: APC/CyberPower HID 0.9
> > Network UPS Tools - UPS driver controller 2.0.5
> >
> > Any ideas?  Any suggestions what to do to get more debugging info?
> >
> > TIA,
> >
> > Jim
> >
> > _______________________________________________
> > Nut-upsuser mailing list
> > Nut-upsuser at lists.alioth.debian.org
> > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
> >
>
>
>_______________________________________________
>Nut-upsuser mailing list
>Nut-upsuser at lists.alioth.debian.org
>http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser




---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 000734-0, 16/04/2007
Tested on: 17/04/2007 7:24:38 AM
avast! is copyright (c) 2000-2007 ALWIL Software.
http://www.avast.com


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20070417/f6bd21e9/attachment.htm