Re: [Nut-upsuser] nut suddenly stopped working...
A.Lizard wrote: > > As I said earlier, I got it working using the -u root option. > > I'm running on the Debian distribution. > > Upon upsmon -c fsd , it shuts down the workstation, but NOT the UPS. In > order to shut down both, I first tried Peter Selinger's shutdown patch for > init.d halt : > > note: program locations reflect where nut*.deb puts things in the Debian > filesystem. > > if [ -f /etc/killpower ] ; then > # if USB is already disabled, re-enable it. > if [ ! -f /proc/bus/usb/devices ]; then > echo "Mounting USB filesystem" > mount -t usbfs usbfs /proc/bus/usb > fi > > # hotplugging is probably off, so run driver as -u root > echo "Killing the power, bye!" > /lib/nut/newhidups -u root -k belkin-ups > sleep 20 > > # uh oh... the UPS power-off failed > # you probably want to reboot here so you don't get stuck! > # *** see the section on power races in shutdown.txt! *** > echo "Rebooting." > reboot > fi > > I tried inserting it: ># See if we need to cut the power. > if [ "$INIT_HALT" = "POWEROFF" ] && [ -x /etc/init.d/ups-monitor ] > then > /etc/init.d/ups-monitor poweroff > fi > > before and after /etc/init.d/ups-monitor poweroff. My scriptlet is not indended to be inserted *inside* anything. I have no idea what the variable $INIT_HALT will be at shutdown time, but most likely it is not set. Very likely the body of that "if" never gets called at all. -- Peter ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut suddenly stopped working...
As I said earlier, I got it working using the -u root option. I'm running on the Debian distribution. Upon upsmon -c fsd , it shuts down the workstation, but NOT the UPS. In order to shut down both, I first tried Peter Selinger's shutdown patch for init.d halt : note: program locations reflect where nut*.deb puts things in the Debian filesystem. if [ -f /etc/killpower ] ; then # if USB is already disabled, re-enable it. if [ ! -f /proc/bus/usb/devices ]; then echo "Mounting USB filesystem" mount -t usbfs usbfs /proc/bus/usb fi # hotplugging is probably off, so run driver as -u root echo "Killing the power, bye!" /lib/nut/newhidups -u root -k belkin-ups sleep 20 # uh oh... the UPS power-off failed # you probably want to reboot here so you don't get stuck! # *** see the section on power races in shutdown.txt! *** echo "Rebooting." reboot fi I tried inserting it: # See if we need to cut the power. if [ "$INIT_HALT" = "POWEROFF" ] && [ -x /etc/init.d/ups-monitor ] then /etc/init.d/ups-monitor poweroff fi before and after /etc/init.d/ups-monitor poweroff. I then tried changing the ups-monitor script: original version: poweroff) flag=`sed -ne 's#^ *POWERDOWNFLAG *\(.*\)$#\1#p' /etc/nut/upsmon.conf` wait_delay=`sed -ne 's#^ *POWEROFF_WAIT= *\(.*\)$#\1#p' /etc/default/nut` if [ -f "$flag" ] ; then if /sbin/upsmon -K >/dev/null 2>&1 ; then echo "Shutting down the UPS ..." sleep 1 # if /sbin/upsdrvctl shutdown ; then I tried changing: if /sbin/upsdrvctl -u root shutdown ; then That failed. I then tried changing the above line to: if /lib/nut/newhidups -a belkin-ups -k ; then What I got was hundreds of iterations of "did not claim interface 0 before use" if /lib/nut/newhidups -a belkin-ups -k ; then Note: /sbin/upsdrvctl -u root [command] belkin-ups works for: start stop but NOT shutdown I decided that if things are to the point where I'm trying to modify ups-monitor, it's time for me to ask for help. thanks A.Lizard member The Internet Society (ISOC), The HTML Writers Guild. "You can't have in a democracy various groups with arms - you have to have the state with a monopoly on power." Condoleeza Rice, US Secretary of State Personal Website http://www.ecis.com/~alizard business Website http://www.reptilelabs.com backup address (if ALL else fails) [EMAIL PROTECTED] PGP 8.0 key available by request or keyserver. Download PGP from: http://www.pgpi.org for e-mail privacy. Disaster prep info: http://www.ecis.com/~alizard/y2k.html ***Looking for INTELLIGENT new technology public policy alternatives?*** http://www.ecis.com/~alizard/technology.html ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut suddenly stopped working...
That is great news! -- Peter A.Lizard wrote: > > At 12:41 PM 2/27/07, you wrote: > It now works - with minor issues. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut suddenly stopped working...
At 12:41 PM 2/27/07, you wrote: It now works - with minor issues. Hi again, several people have already responded to this message, so I will be brief. I just wanted to reiterate that the output below is exactly as it should be. I don't see any bugs there. The problem rather seems to be that you are not following the instructions precisely. What is the point of starting, then stopping the driver? Of course you cannot read anything from the UPS if you have stopped the driver. If you need some step-by-step instructions in addition to the ones that are contained in the file INSTALL in the NUT distribution, try these: http://www.mathstat.dal.ca/~selinger/ups/backups.html They have been written for Linux 2.6.10 and an APC device, but it should work the same way for Belkin and other operating systems. If you still run into trouble, please write to the list again! Preferably include information on what set of instructions you followed, up to what step you got, and in what step of the instructions the error occurred. Good luck! -- Peter Thanks. When looking at the URL earlier, I'd missed something rather important, and as a result, misunderstood most of the advice I'd gotten. Basically, hotplugging failed with either the hotplug or hotplug-ng files. I missed step 17... as a result, I didn't know adding nut startup commands to rc.local was required and the place to run -u root commands if need be. It came up running as soon as boot complated as soon as I added the rc.local commands and rebooted. 17. power-on startup during regular boot echo "Starting UPS driver, daemon, and monitor." upsdrvctl -u root start belkin-ups upsd -u root Glitches: 1. knutclient won't run instant commands, but the upscmd is an adequate workaround. 2. The ups doesn't shut down after the system is powered off, but that's because I'm figuring out where to put your recommended additions to /etc/init.d/halt If I can't get it to work, I'll probably be back for help. Thanks again to you and to everyone on the list who responded. A.Lizard A.Lizard wrote: > > I tried building nut 2.0.5 pre2 from source using the user=nut and make usb > options, and got the same results. It works from -u root, but upsd gets a > "connection refused" message. > > Same messages when I run newhidups directly. I can't find any processes > connected to the UPS. > > I am open to suggestions. Giving up isn't an option for me, I really do > need to get this running and more to the point, I'm writing an article > about this which is due in a few days. > > here's some of the output I've gotten: > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl start > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5-pre2) > > No matching HID UPS found > Driver failed to start (exit status=1) > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl stop > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Can't open /var/state/ups/newhidups-belkin-ups.pid: No such file or directory > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u root start > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5-pre2) > > Detected a UPS: Belkin/UPS > Using subdriver: Belkin HID 0.1 > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u root stop > Network UPS Tools - UPS driver controller 2.0.5-pre2 > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u nut stop > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Can't open /var/state/ups/newhidups-belkin-ups.pid: No such file or directory > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u nut start > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5-pre2) > > No matching HID UPS found > Driver failed to start (exit status=1) > terrarium:/usr/local/ups/etc# > > > >At 11:48 PM 2/23/07, you wrote: > >>At 06:14 PM 2/23/07, you wrote: > >>>Back to square one. Is there any other process running that might > >>>already be attached to that device? -- Peter > >> > >>these are the only hal processes running > >>terrarium:/usr/lib/hal# ps axjf > >> > >>/usr/sbin/hald > >> 2590 2591 2590 2590 ? -1 S0 0:00 \_ hald-runner > >> 2591 2597 2590 2590 ? -1 S 105 0:00 \_ > >> hald-addon-acpi: listening on acpid socket /var/run/acpid.socket > >> 2591 2603 2590 2590 ? -1 S 105 0:00 \_ > >> hald-addon-keyboard: listening on /dev/input/event0 > >> 2591 2617 2590 2590 ? -1 S0 0:01 \_ > >> hald-addon-storage: polling /dev/hdc > >> > >>/usr/lib/hal# usbmodules --device /proc/bus/usb/002/006usbhid > >> > >>from dmesg: > >>hiddev96: USB HID v1.11 Device [Belkin UPS] on usb-:00:0b.0-5.3 > >> > >>from messages: > >>Feb 23 14:17:25 terrarium ke
Re: [Nut-upsuser] nut suddenly stopped working...
Peter Selinger wrote: Basically, you need to pass the same system user to "-u" on both the driver and upsd. >>> How? >> See 'man 3 upsd'. > Or perhaps 'man 8 upsd'. I really need to go to bed... :-) Best regards, Arjen ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut suddenly stopped working...
Arjen de Korte wrote: > > A.Lizard wrote: > > >> Basically, you need to pass the same system user to "-u" on both the > >> driver and upsd. > > > > How? > > See 'man 3 upsd'. Or perhaps 'man 8 upsd'. -- Peter ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut suddenly stopped working...
A.Lizard wrote: >> Basically, you need to pass the same system user to "-u" on both the >> driver and upsd. > > How? See 'man 3 upsd'. Best regards, Arjen ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut suddenly stopped working...
A.Lizard wrote: > >> >This is also expected, since it sounds like you still have the driver > >> >running with "-u root". > >> > >>I haven't been able to get it to run any other way - newhidups outputs > >>(non-root and root) below. > > > >Right. The fact that it works when both the driver and upsd are passed > >"-u root" points to a permissions problem. > > > >Basically, you need to pass the same system user to "-u" on both the > >driver and upsd. > > How? By typing upsd -u root instead of upsd -- Peter ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut suddenly stopped working...
Hi again, several people have already responded to this message, so I will be brief. I just wanted to reiterate that the output below is exactly as it should be. I don't see any bugs there. The problem rather seems to be that you are not following the instructions precisely. What is the point of starting, then stopping the driver? Of course you cannot read anything from the UPS if you have stopped the driver. If you need some step-by-step instructions in addition to the ones that are contained in the file INSTALL in the NUT distribution, try these: http://www.mathstat.dal.ca/~selinger/ups/backups.html They have been written for Linux 2.6.10 and an APC device, but it should work the same way for Belkin and other operating systems. If you still run into trouble, please write to the list again! Preferably include information on what set of instructions you followed, up to what step you got, and in what step of the instructions the error occurred. Good luck! -- Peter A.Lizard wrote: > > I tried building nut 2.0.5 pre2 from source using the user=nut and make usb > options, and got the same results. It works from -u root, but upsd gets a > "connection refused" message. > > Same messages when I run newhidups directly. I can't find any processes > connected to the UPS. > > I am open to suggestions. Giving up isn't an option for me, I really do > need to get this running and more to the point, I'm writing an article > about this which is due in a few days. > > here's some of the output I've gotten: > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl start > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5-pre2) > > No matching HID UPS found > Driver failed to start (exit status=1) > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl stop > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Can't open /var/state/ups/newhidups-belkin-ups.pid: No such file or directory > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u root start > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5-pre2) > > Detected a UPS: Belkin/UPS > Using subdriver: Belkin HID 0.1 > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u root stop > Network UPS Tools - UPS driver controller 2.0.5-pre2 > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u nut stop > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Can't open /var/state/ups/newhidups-belkin-ups.pid: No such file or directory > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u nut start > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5-pre2) > > No matching HID UPS found > Driver failed to start (exit status=1) > terrarium:/usr/local/ups/etc# > > > >At 11:48 PM 2/23/07, you wrote: > >>At 06:14 PM 2/23/07, you wrote: > >>>Back to square one. Is there any other process running that might > >>>already be attached to that device? -- Peter > >> > >>these are the only hal processes running > >>terrarium:/usr/lib/hal# ps axjf > >> > >>/usr/sbin/hald > >> 2590 2591 2590 2590 ? -1 S0 0:00 \_ hald-runner > >> 2591 2597 2590 2590 ? -1 S 105 0:00 \_ > >> hald-addon-acpi: listening on acpid socket /var/run/acpid.socket > >> 2591 2603 2590 2590 ? -1 S 105 0:00 \_ > >> hald-addon-keyboard: listening on /dev/input/event0 > >> 2591 2617 2590 2590 ? -1 S0 0:01 \_ > >> hald-addon-storage: polling /dev/hdc > >> > >>/usr/lib/hal# usbmodules --device /proc/bus/usb/002/006usbhid > >> > >>from dmesg: > >>hiddev96: USB HID v1.11 Device [Belkin UPS] on usb-:00:0b.0-5.3 > >> > >>from messages: > >>Feb 23 14:17:25 terrarium kernel: usb 2-5.3: USB disconnect, address 3 > >>Feb 23 14:22:23 terrarium kernel: usb 2-5.3: new low speed USB device > >>using ohci_hcd and address 6 > >>Feb 23 14:22:23 terrarium kernel: usb 2-5.3: configuration #1 chosen from > >>1 choice > >>Feb 23 14:22:23 terrarium kernel: hiddev96: USB HID v1.11 Device [Belkin > >>UPS] on usb-:00:0b.0-5.3 > >> > >> > >>Is there anywhere else I should be looking? > >> > >>thanks > >>A.Lizard > >> > >> > >>>A.Lizard wrote: > >>> > > >>> > At 01:01 PM 2/23/07, you wrote: > >>> > I tried the procedure - no change. > >>> > > >>> > terrarium:/usr/lib/hal# /lib/nut/newhidups -DDD -a belkin-ups > >>> > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 > >>> > (2.0.5) > >>> > > >>> > debug level is '3' > >>> > Checking device (050D/0551) (002/006) > >>> > - VendorID: 050d > >>> > - ProductID: 0551 > >>> > - Manufacturer: unknown > >>> > - Product: unknown > >>> > - Serial Number: unknown > >>> > - Bus: 002 > >>> > Trying to match device > >>> > Device matches > >>> > failed to claim USB device, try
Re: [Nut-upsuser] nut suddenly stopped working...
At 05:31 AM 2/27/07, you wrote: [for general debugging like this, please keep the list copied.] On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote: At 05:09 AM 2/27/07, you wrote: >On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote: >>At 04:48 AM 2/27/07, you wrote: >> >On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote: >> >>and "upsd gets a 'connection refused' message" was a typo, I meant >> *upsc* . >> >>I haven't tried running upsd since building the wrong source package. >> > >> >upsc connects to upsd (this is the network portion of "Network UPS >> >Tools"), so upsd needs to be running or else you will get a >> >"connection refused" message from upsc. >> > >> >upsd also connects to the individual drivers, as Arjen as pointed out. >> > >> >-- >> >- Charles Lepple >> >>interesting... so I tried this and got: >> >>terrarium:/home/alizard# /usr/local/ups/sbin/upsd -u root >>Network UPS Tools upsd 2.0.5-pre2 >>/usr/local/ups/etc/upsd.conf is world readable >>Connected to UPS [belkin-ups]: belkin-ups >>/usr/local/ups/etc/upsd.users is world readable >>terrarium:/home/alizard# >> >>and knutclient suddenly started displaying. >> >>Afterwards, I tried: >> 2469 ?00:00:00 upsd >> 2515 pts/100:00:00 ps >>terrarium:/home/alizard# kill -9 2469 >>terrarium:/home/alizard# /etc/init.d/nut start >>Starting Network UPS Tools: (upsdrvctl failed). >>terrarium:/home/alizard# /etc/init.d nut stop >>bash: /etc/init.d: is a directory >>terrarium:/home/alizard# /etc/init.d/nut stop >>Stopping Network UPS Tools: (upsdrvctl failed) upsd upsmon. >>terrarium:/home/alizard# /usr/local/ups/sbin/upsd -u root >>Network UPS Tools upsd 2.0.5-pre2 >>/usr/local/ups/etc/upsd.conf is world readable >>Connected to UPS [belkin-ups]: belkin-ups >>/usr/local/ups/etc/upsd.users is world readable >> >>[note - I have root , nut , alizard entries in upsd.users ] > >upsd.users lists roles - they don't have to be named like the system >users such as root or nut. > >The "-u" parameter for the daemons is for overriding the choice of the >"nut" system user. > >>terrarium:/home/alizard# /usr/local/ups/sbin/upsd -u alizard >>Network UPS Tools upsd 2.0.5-pre2 >>Can't chdir to /var/state/ups: Permission denied > >Right, permissions are usually restricted to the nut system user on >that directory. > >>terrarium:/home/alizard# /usr/local/ups/sbin/upsd -u nut >>Network UPS Tools upsd 2.0.5-pre2 >>/usr/local/ups/etc/upsd.conf is world readable >>Can't connect to UPS [belkin-ups] (belkin-ups): Permission denied > >This is also expected, since it sounds like you still have the driver >running with "-u root". I haven't been able to get it to run any other way - newhidups outputs (non-root and root) below. Right. The fact that it works when both the driver and upsd are passed "-u root" points to a permissions problem. Basically, you need to pass the same system user to "-u" on both the driver and upsd. How? thanks A.Lizard Users in ups.users are not connected to the system user IDs, but they are one part of the system used to prevent random users from being able to shut down the system. -- - Charles Lepple member The Internet Society (ISOC), The HTML Writers Guild. "You can't have in a democracy various groups with arms - you have to have the state with a monopoly on power." Condoleeza Rice, US Secretary of State Personal Website http://www.ecis.com/~alizard business Website http://www.reptilelabs.com backup address (if ALL else fails) [EMAIL PROTECTED] PGP 8.0 key available by request or keyserver. Download PGP from: http://www.pgpi.org for e-mail privacy. Disaster prep info: http://www.ecis.com/~alizard/y2k.html ***Looking for INTELLIGENT new technology public policy alternatives?*** http://www.ecis.com/~alizard/technology.html ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut suddenly stopped working...
[for general debugging like this, please keep the list copied.] On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote: At 05:09 AM 2/27/07, you wrote: >On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote: >>At 04:48 AM 2/27/07, you wrote: >> >On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote: >> >>and "upsd gets a 'connection refused' message" was a typo, I meant >> *upsc* . >> >>I haven't tried running upsd since building the wrong source package. >> > >> >upsc connects to upsd (this is the network portion of "Network UPS >> >Tools"), so upsd needs to be running or else you will get a >> >"connection refused" message from upsc. >> > >> >upsd also connects to the individual drivers, as Arjen as pointed out. >> > >> >-- >> >- Charles Lepple >> >>interesting... so I tried this and got: >> >>terrarium:/home/alizard# /usr/local/ups/sbin/upsd -u root >>Network UPS Tools upsd 2.0.5-pre2 >>/usr/local/ups/etc/upsd.conf is world readable >>Connected to UPS [belkin-ups]: belkin-ups >>/usr/local/ups/etc/upsd.users is world readable >>terrarium:/home/alizard# >> >>and knutclient suddenly started displaying. >> >>Afterwards, I tried: >> 2469 ?00:00:00 upsd >> 2515 pts/100:00:00 ps >>terrarium:/home/alizard# kill -9 2469 >>terrarium:/home/alizard# /etc/init.d/nut start >>Starting Network UPS Tools: (upsdrvctl failed). >>terrarium:/home/alizard# /etc/init.d nut stop >>bash: /etc/init.d: is a directory >>terrarium:/home/alizard# /etc/init.d/nut stop >>Stopping Network UPS Tools: (upsdrvctl failed) upsd upsmon. >>terrarium:/home/alizard# /usr/local/ups/sbin/upsd -u root >>Network UPS Tools upsd 2.0.5-pre2 >>/usr/local/ups/etc/upsd.conf is world readable >>Connected to UPS [belkin-ups]: belkin-ups >>/usr/local/ups/etc/upsd.users is world readable >> >>[note - I have root , nut , alizard entries in upsd.users ] > >upsd.users lists roles - they don't have to be named like the system >users such as root or nut. > >The "-u" parameter for the daemons is for overriding the choice of the >"nut" system user. > >>terrarium:/home/alizard# /usr/local/ups/sbin/upsd -u alizard >>Network UPS Tools upsd 2.0.5-pre2 >>Can't chdir to /var/state/ups: Permission denied > >Right, permissions are usually restricted to the nut system user on >that directory. > >>terrarium:/home/alizard# /usr/local/ups/sbin/upsd -u nut >>Network UPS Tools upsd 2.0.5-pre2 >>/usr/local/ups/etc/upsd.conf is world readable >>Can't connect to UPS [belkin-ups] (belkin-ups): Permission denied > >This is also expected, since it sounds like you still have the driver >running with "-u root". I haven't been able to get it to run any other way - newhidups outputs (non-root and root) below. Right. The fact that it works when both the driver and upsd are passed "-u root" points to a permissions problem. Basically, you need to pass the same system user to "-u" on both the driver and upsd. Users in ups.users are not connected to the system user IDs, but they are one part of the system used to prevent random users from being able to shut down the system. -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut suddenly stopped working...
On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote: At 04:48 AM 2/27/07, you wrote: >On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote: >>and "upsd gets a 'connection refused' message" was a typo, I meant *upsc* . >>I haven't tried running upsd since building the wrong source package. > >upsc connects to upsd (this is the network portion of "Network UPS >Tools"), so upsd needs to be running or else you will get a >"connection refused" message from upsc. > >upsd also connects to the individual drivers, as Arjen as pointed out. > >-- >- Charles Lepple interesting... so I tried this and got: terrarium:/home/alizard# /usr/local/ups/sbin/upsd -u root Network UPS Tools upsd 2.0.5-pre2 /usr/local/ups/etc/upsd.conf is world readable Connected to UPS [belkin-ups]: belkin-ups /usr/local/ups/etc/upsd.users is world readable terrarium:/home/alizard# and knutclient suddenly started displaying. Afterwards, I tried: 2469 ?00:00:00 upsd 2515 pts/100:00:00 ps terrarium:/home/alizard# kill -9 2469 terrarium:/home/alizard# /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl failed). terrarium:/home/alizard# /etc/init.d nut stop bash: /etc/init.d: is a directory terrarium:/home/alizard# /etc/init.d/nut stop Stopping Network UPS Tools: (upsdrvctl failed) upsd upsmon. terrarium:/home/alizard# /usr/local/ups/sbin/upsd -u root Network UPS Tools upsd 2.0.5-pre2 /usr/local/ups/etc/upsd.conf is world readable Connected to UPS [belkin-ups]: belkin-ups /usr/local/ups/etc/upsd.users is world readable [note - I have root , nut , alizard entries in upsd.users ] upsd.users lists roles - they don't have to be named like the system users such as root or nut. The "-u" parameter for the daemons is for overriding the choice of the "nut" system user. terrarium:/home/alizard# /usr/local/ups/sbin/upsd -u alizard Network UPS Tools upsd 2.0.5-pre2 Can't chdir to /var/state/ups: Permission denied Right, permissions are usually restricted to the nut system user on that directory. terrarium:/home/alizard# /usr/local/ups/sbin/upsd -u nut Network UPS Tools upsd 2.0.5-pre2 /usr/local/ups/etc/upsd.conf is world readable Can't connect to UPS [belkin-ups] (belkin-ups): Permission denied This is also expected, since it sounds like you still have the driver running with "-u root". -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut suddenly stopped working...
> The latest version available packaged for Debian that I can find on the > Debian site is 2.0.5-3, the one I've previously had trouble with. The problems you have don't seem to be related to the anything wrong with the code, but rather with the configuration. So I'd go with the packaged version for Debian if I were you. > So that's the one I should be using? Would I be better off dumping the > source build and installing 2.0.5-3 , or doing a source build from the > 2.1. development tree? There are some improvements in the development tree, but not that critical that warrants an advice to not use nut-2.0.5 anymore. The latter should be fine. As long as you still don't have a more or less working setup, it is pointless to try to head for the development version. It will have (almost) the same problems. Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut suddenly stopped working...
On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote: and "upsd gets a 'connection refused' message" was a typo, I meant *upsc* . I haven't tried running upsd since building the wrong source package. upsc connects to upsd (this is the network portion of "Network UPS Tools"), so upsd needs to be running or else you will get a "connection refused" message from upsc. upsd also connects to the individual drivers, as Arjen as pointed out. -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut suddenly stopped working...
At 03:20 AM 2/27/07, you wrote: Thanks. What I wanted was the latest version short of building it from the code in subversion. (which I consider kind of a last resort, since I've The latest version available packaged for Debian that I can find on the Debian site is 2.0.5-3, the one I've previously had trouble with. So that's the one I should be using? Would I be better off dumping the source build and installing 2.0.5-3 , or doing a source build from the 2.1. development tree? and "upsd gets a 'connection refused' message" was a typo, I meant *upsc* . I haven't tried running upsd since building the wrong source package. thanks A.Lizard > I tried building nut 2.0.5 pre2 from source using the user=nut and make > usb options, and got the same results. That's an old version, please don't use that anymore. The latest stable version is nut-2.0.5. Furthermore, you should specify the same '-u user' for both upsdrvctl and upsd. > It works from -u root, but upsd gets a "connection refused" message. The fact that it works as root is usually is indicative for a permissions problem on the usb port. The other message is probably due to the fact that if you run the driver as root, upsd must run as root too. > Same messages when I run newhidups directly. I can't find any processes > connected to the UPS. If you start up the driver via upsdrvctl, the driver will show up as 'newhidups' if started successfully. > I am open to suggestions. Giving up isn't an option for me, I really do > need to get this running and more to the point, I'm writing an article > about this which is due in a few days. > > here's some of the output I've gotten: > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl start > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 > (2.0.5-pre2) > > No matching HID UPS found > Driver failed to start (exit status=1) See above. > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl stop > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Can't open /var/state/ups/newhidups-belkin-ups.pid: No such file or > directory If the driver isn't running, you can't stop it (there will be no pid file). > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u root start > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 > (2.0.5-pre2) > > Detected a UPS: Belkin/UPS > Using subdriver: Belkin HID 0.1 After this, starting 'upsd -u root' should also work. > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u root stop > Network UPS Tools - UPS driver controller 2.0.5-pre2 This means the state directory apparently exists, a driver was found and it has been send a signal to stop successfully. Most likely, it will stop. > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u nut stop > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Can't open /var/state/ups/newhidups-belkin-ups.pid: No such file or > directory You already stopped the driver in the step before, so there is nothing left to stop. > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u nut start > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 > (2.0.5-pre2) > > No matching HID UPS found > Driver failed to start (exit status=1) Again, this is a permissions problem on the usb port. The solution to this problem is in scripts/hotplug or scripts/hotplug-ng (depending on the kernel you're using). Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57 member The Internet Society (ISOC), The HTML Writers Guild. "You can't have in a democracy various groups with arms - you have to have the state with a monopoly on power." Condoleeza Rice, US Secretary of State Personal Website http://www.ecis.com/~alizard business Website http://www.reptilelabs.com backup address (if ALL else fails) [EMAIL PROTECTED] PGP 8.0 key available by request or keyserver. Download PGP from: http://www.pgpi.org for e-mail privacy. Disaster prep info: http://www.ecis.com/~alizard/y2k.html ***Looking for INTELLIGENT new technology public policy alternatives?*** http://www.ecis.com/~alizard/technology.html ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut suddenly stopped working...
> I tried building nut 2.0.5 pre2 from source using the user=nut and make > usb options, and got the same results. That's an old version, please don't use that anymore. The latest stable version is nut-2.0.5. Furthermore, you should specify the same '-u user' for both upsdrvctl and upsd. > It works from -u root, but upsd gets a "connection refused" message. The fact that it works as root is usually is indicative for a permissions problem on the usb port. The other message is probably due to the fact that if you run the driver as root, upsd must run as root too. > Same messages when I run newhidups directly. I can't find any processes > connected to the UPS. If you start up the driver via upsdrvctl, the driver will show up as 'newhidups' if started successfully. > I am open to suggestions. Giving up isn't an option for me, I really do > need to get this running and more to the point, I'm writing an article > about this which is due in a few days. > > here's some of the output I've gotten: > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl start > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 > (2.0.5-pre2) > > No matching HID UPS found > Driver failed to start (exit status=1) See above. > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl stop > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Can't open /var/state/ups/newhidups-belkin-ups.pid: No such file or > directory If the driver isn't running, you can't stop it (there will be no pid file). > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u root start > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 > (2.0.5-pre2) > > Detected a UPS: Belkin/UPS > Using subdriver: Belkin HID 0.1 After this, starting 'upsd -u root' should also work. > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u root stop > Network UPS Tools - UPS driver controller 2.0.5-pre2 This means the state directory apparently exists, a driver was found and it has been send a signal to stop successfully. Most likely, it will stop. > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u nut stop > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Can't open /var/state/ups/newhidups-belkin-ups.pid: No such file or > directory You already stopped the driver in the step before, so there is nothing left to stop. > terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u nut start > Network UPS Tools - UPS driver controller 2.0.5-pre2 > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 > (2.0.5-pre2) > > No matching HID UPS found > Driver failed to start (exit status=1) Again, this is a permissions problem on the usb port. The solution to this problem is in scripts/hotplug or scripts/hotplug-ng (depending on the kernel you're using). Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut suddenly stopped working...
I tried building nut 2.0.5 pre2 from source using the user=nut and make usb options, and got the same results. It works from -u root, but upsd gets a "connection refused" message. Same messages when I run newhidups directly. I can't find any processes connected to the UPS. I am open to suggestions. Giving up isn't an option for me, I really do need to get this running and more to the point, I'm writing an article about this which is due in a few days. here's some of the output I've gotten: terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5-pre2 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5-pre2) No matching HID UPS found Driver failed to start (exit status=1) terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl stop Network UPS Tools - UPS driver controller 2.0.5-pre2 Can't open /var/state/ups/newhidups-belkin-ups.pid: No such file or directory terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u root start Network UPS Tools - UPS driver controller 2.0.5-pre2 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5-pre2) Detected a UPS: Belkin/UPS Using subdriver: Belkin HID 0.1 terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u root stop Network UPS Tools - UPS driver controller 2.0.5-pre2 terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u nut stop Network UPS Tools - UPS driver controller 2.0.5-pre2 Can't open /var/state/ups/newhidups-belkin-ups.pid: No such file or directory terrarium:/usr/local/ups/etc# /usr/local/ups/bin/upsdrvctl -u nut start Network UPS Tools - UPS driver controller 2.0.5-pre2 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5-pre2) No matching HID UPS found Driver failed to start (exit status=1) terrarium:/usr/local/ups/etc# At 11:48 PM 2/23/07, you wrote: At 06:14 PM 2/23/07, you wrote: Back to square one. Is there any other process running that might already be attached to that device? -- Peter these are the only hal processes running terrarium:/usr/lib/hal# ps axjf /usr/sbin/hald 2590 2591 2590 2590 ? -1 S0 0:00 \_ hald-runner 2591 2597 2590 2590 ? -1 S 105 0:00 \_ hald-addon-acpi: listening on acpid socket /var/run/acpid.socket 2591 2603 2590 2590 ? -1 S 105 0:00 \_ hald-addon-keyboard: listening on /dev/input/event0 2591 2617 2590 2590 ? -1 S0 0:01 \_ hald-addon-storage: polling /dev/hdc /usr/lib/hal# usbmodules --device /proc/bus/usb/002/006usbhid from dmesg: hiddev96: USB HID v1.11 Device [Belkin UPS] on usb-:00:0b.0-5.3 from messages: Feb 23 14:17:25 terrarium kernel: usb 2-5.3: USB disconnect, address 3 Feb 23 14:22:23 terrarium kernel: usb 2-5.3: new low speed USB device using ohci_hcd and address 6 Feb 23 14:22:23 terrarium kernel: usb 2-5.3: configuration #1 chosen from 1 choice Feb 23 14:22:23 terrarium kernel: hiddev96: USB HID v1.11 Device [Belkin UPS] on usb-:00:0b.0-5.3 Is there anywhere else I should be looking? thanks A.Lizard A.Lizard wrote: > > At 01:01 PM 2/23/07, you wrote: > I tried the procedure - no change. > > terrarium:/usr/lib/hal# /lib/nut/newhidups -DDD -a belkin-ups > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) > > debug level is '3' > Checking device (050D/0551) (002/006) > - VendorID: 050d > - ProductID: 0551 > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device matches > failed to claim USB device, trying 2 more time(s)... > detaching kernel driver from USB device... > failed to detach kernel driver from USB device... > trying again to claim USB device... > failed to claim USB device, trying 1 more time(s)... > detaching kernel driver from USB device... > failed to detach kernel driver from USB device... > trying again to claim USB device... > failed to claim USB device, trying 0 more time(s)... > detaching kernel driver from USB device... > failed to detach kernel driver from USB device... > trying again to claim USB device... > Unable to get HID descriptor (error sending control message: Operation not > permitted) > HID descriptor, method 2: (9 bytes) => 09 21 11 01 21 01 22 a8 01 > HID descriptor retrieved (Reportlen = 424) > Unable to get Report descriptor (-1): Operation not permitted > Checking device (04A9/1094) (002/005) > - VendorID: 04a9 > - ProductID: 1094 > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device does not match - skipping > Checking device (058F/9254) (002/002) > - VendorID: 058f > - ProductID: 9254 > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device does not match - skipping > Checking device (04A9/220E) (002/004) > - VendorID: 04a9 > - ProductID: 220e > - Manufacturer: unkno
Re: [Nut-upsuser] nut suddenly stopped working...
At 06:14 PM 2/23/07, you wrote: Back to square one. Is there any other process running that might already be attached to that device? -- Peter these are the only hal processes running terrarium:/usr/lib/hal# ps axjf /usr/sbin/hald 2590 2591 2590 2590 ? -1 S0 0:00 \_ hald-runner 2591 2597 2590 2590 ? -1 S 105 0:00 \_ hald-addon-acpi: listening on acpid socket /var/run/acpid.socket 2591 2603 2590 2590 ? -1 S 105 0:00 \_ hald-addon-keyboard: listening on /dev/input/event0 2591 2617 2590 2590 ? -1 S0 0:01 \_ hald-addon-storage: polling /dev/hdc /usr/lib/hal# usbmodules --device /proc/bus/usb/002/006usbhid from dmesg: hiddev96: USB HID v1.11 Device [Belkin UPS] on usb-:00:0b.0-5.3 from messages: Feb 23 14:17:25 terrarium kernel: usb 2-5.3: USB disconnect, address 3 Feb 23 14:22:23 terrarium kernel: usb 2-5.3: new low speed USB device using ohci_hcd and address 6 Feb 23 14:22:23 terrarium kernel: usb 2-5.3: configuration #1 chosen from 1 choice Feb 23 14:22:23 terrarium kernel: hiddev96: USB HID v1.11 Device [Belkin UPS] on usb-:00:0b.0-5.3 Is there anywhere else I should be looking? thanks A.Lizard A.Lizard wrote: > > At 01:01 PM 2/23/07, you wrote: > I tried the procedure - no change. > > terrarium:/usr/lib/hal# /lib/nut/newhidups -DDD -a belkin-ups > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) > > debug level is '3' > Checking device (050D/0551) (002/006) > - VendorID: 050d > - ProductID: 0551 > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device matches > failed to claim USB device, trying 2 more time(s)... > detaching kernel driver from USB device... > failed to detach kernel driver from USB device... > trying again to claim USB device... > failed to claim USB device, trying 1 more time(s)... > detaching kernel driver from USB device... > failed to detach kernel driver from USB device... > trying again to claim USB device... > failed to claim USB device, trying 0 more time(s)... > detaching kernel driver from USB device... > failed to detach kernel driver from USB device... > trying again to claim USB device... > Unable to get HID descriptor (error sending control message: Operation not > permitted) > HID descriptor, method 2: (9 bytes) => 09 21 11 01 21 01 22 a8 01 > HID descriptor retrieved (Reportlen = 424) > Unable to get Report descriptor (-1): Operation not permitted > Checking device (04A9/1094) (002/005) > - VendorID: 04a9 > - ProductID: 1094 > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device does not match - skipping > Checking device (058F/9254) (002/002) > - VendorID: 058f > - ProductID: 9254 > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device does not match - skipping > Checking device (04A9/220E) (002/004) > - VendorID: 04a9 > - ProductID: 220e > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device does not match - skipping > Checking device (/) (002/001) > - VendorID: > - ProductID: > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device does not match - skipping > Checking device (/) (001/001) > - VendorID: > - ProductID: > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 001 > Trying to match device > Device does not match - skipping > No appropriate HID device found > No matching HID UPS found > terrarium:/usr/lib/hal# exit > exit > > terrarium:/home/alizard# /lib/nut/newhidups -DDD -u root -a belkin-ups > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) > > debug level is '3' > Checking device (050D/0551) (002/006) > - VendorID: 050d > - ProductID: 0551 > - Manufacturer: Belkin > - Product: UPS > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device matches > failed to claim USB device, trying 2 more time(s)... > detaching kernel driver from USB device... > trying again to claim USB device... > > > >[please, keep the traffic on the list] > > > >2007/2/23, A.Lizard <[EMAIL PROTECTED]>: > >>At 05:12 AM 2/23/07, you wrote: > >> >Not sure you've seen it, so I step up: > >> > > >> >in the "ps" output, there is: hald-addon-hid-ups > >> >this is an HAL addon, based upon the same code as our old hidups... > >> >this is what I'm working on in NUT to replace. > >> >I've not thought at it before since I've completely disabled hiddev > >> >support in kernel for MGE units, but any other brand that is HID > >> >compliant, should face it. > >> > > >> >the detach method might fail since the driver is _used_, not only loaded! > >> > > >> >Note that the above is the reason why I've not thrown out
Re: [Nut-upsuser] nut suddenly stopped working...
Back to square one. Is there any other process running that might already be attached to that device? -- Peter A.Lizard wrote: > > At 01:01 PM 2/23/07, you wrote: > I tried the procedure - no change. > > terrarium:/usr/lib/hal# /lib/nut/newhidups -DDD -a belkin-ups > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) > > debug level is '3' > Checking device (050D/0551) (002/006) > - VendorID: 050d > - ProductID: 0551 > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device matches > failed to claim USB device, trying 2 more time(s)... > detaching kernel driver from USB device... > failed to detach kernel driver from USB device... > trying again to claim USB device... > failed to claim USB device, trying 1 more time(s)... > detaching kernel driver from USB device... > failed to detach kernel driver from USB device... > trying again to claim USB device... > failed to claim USB device, trying 0 more time(s)... > detaching kernel driver from USB device... > failed to detach kernel driver from USB device... > trying again to claim USB device... > Unable to get HID descriptor (error sending control message: Operation not > permitted) > HID descriptor, method 2: (9 bytes) => 09 21 11 01 21 01 22 a8 01 > HID descriptor retrieved (Reportlen = 424) > Unable to get Report descriptor (-1): Operation not permitted > Checking device (04A9/1094) (002/005) > - VendorID: 04a9 > - ProductID: 1094 > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device does not match - skipping > Checking device (058F/9254) (002/002) > - VendorID: 058f > - ProductID: 9254 > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device does not match - skipping > Checking device (04A9/220E) (002/004) > - VendorID: 04a9 > - ProductID: 220e > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device does not match - skipping > Checking device (/) (002/001) > - VendorID: > - ProductID: > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device does not match - skipping > Checking device (/) (001/001) > - VendorID: > - ProductID: > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 001 > Trying to match device > Device does not match - skipping > No appropriate HID device found > No matching HID UPS found > terrarium:/usr/lib/hal# exit > exit > > terrarium:/home/alizard# /lib/nut/newhidups -DDD -u root -a belkin-ups > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) > > debug level is '3' > Checking device (050D/0551) (002/006) > - VendorID: 050d > - ProductID: 0551 > - Manufacturer: Belkin > - Product: UPS > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device matches > failed to claim USB device, trying 2 more time(s)... > detaching kernel driver from USB device... > trying again to claim USB device... > > > >[please, keep the traffic on the list] > > > >2007/2/23, A.Lizard <[EMAIL PROTECTED]>: > >>At 05:12 AM 2/23/07, you wrote: > >> >Not sure you've seen it, so I step up: > >> > > >> >in the "ps" output, there is: hald-addon-hid-ups > >> >this is an HAL addon, based upon the same code as our old hidups... > >> >this is what I'm working on in NUT to replace. > >> >I've not thought at it before since I've completely disabled hiddev > >> >support in kernel for MGE units, but any other brand that is HID > >> >compliant, should face it. > >> > > >> >the detach method might fail since the driver is _used_, not only loaded! > >> > > >> >Note that the above is the reason why I've not thrown out _our_ HAL > >> >support: we still need a way to instruct the HAL autoloaded drivers > >> >not to run if we want to use the classic nut . And this will be done > >> >through the new config (nut.conf -> MODE) > >> > > >> >I've no clean solution apart from removing / renaming the addon... > >> > >>So I should try finding the addon and removing or renaming it? > > > >right > > > >simply unplug your UPS' USB cord > >rename the hald-addon-hid-ups file (should be somewhere in > >/usr/lib/hal ; use rpm or deb to query the content exact and path of > >the hal package) > >plug back your USB cord, > >retry the previous tests. > > > >Arnaud > >-- > >Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt > >Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ > >Debian Developer - http://people.debian.org/~aquette/ > >OpenSource Developer - http://arnaud.quette.free.fr/ > > member The Internet Society (ISOC), The HTML Writers Guild. > "You can't have in a democracy various groups with arms - you have to have > the state with a monopoly on power." Condoleeza Rice, US Secretary of State > Personal Website http://ww
Re: [Nut-upsuser] nut suddenly stopped working...
At 01:01 PM 2/23/07, you wrote: I tried the procedure - no change. terrarium:/usr/lib/hal# /lib/nut/newhidups -DDD -a belkin-ups Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) debug level is '3' Checking device (050D/0551) (002/006) - VendorID: 050d - ProductID: 0551 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 002 Trying to match device Device matches failed to claim USB device, trying 2 more time(s)... detaching kernel driver from USB device... failed to detach kernel driver from USB device... trying again to claim USB device... failed to claim USB device, trying 1 more time(s)... detaching kernel driver from USB device... failed to detach kernel driver from USB device... trying again to claim USB device... failed to claim USB device, trying 0 more time(s)... detaching kernel driver from USB device... failed to detach kernel driver from USB device... trying again to claim USB device... Unable to get HID descriptor (error sending control message: Operation not permitted) HID descriptor, method 2: (9 bytes) => 09 21 11 01 21 01 22 a8 01 HID descriptor retrieved (Reportlen = 424) Unable to get Report descriptor (-1): Operation not permitted Checking device (04A9/1094) (002/005) - VendorID: 04a9 - ProductID: 1094 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 002 Trying to match device Device does not match - skipping Checking device (058F/9254) (002/002) - VendorID: 058f - ProductID: 9254 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 002 Trying to match device Device does not match - skipping Checking device (04A9/220E) (002/004) - VendorID: 04a9 - ProductID: 220e - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 002 Trying to match device Device does not match - skipping Checking device (/) (002/001) - VendorID: - ProductID: - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 002 Trying to match device Device does not match - skipping Checking device (/) (001/001) - VendorID: - ProductID: - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 001 Trying to match device Device does not match - skipping No appropriate HID device found No matching HID UPS found terrarium:/usr/lib/hal# exit exit terrarium:/home/alizard# /lib/nut/newhidups -DDD -u root -a belkin-ups Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) debug level is '3' Checking device (050D/0551) (002/006) - VendorID: 050d - ProductID: 0551 - Manufacturer: Belkin - Product: UPS - Serial Number: unknown - Bus: 002 Trying to match device Device matches failed to claim USB device, trying 2 more time(s)... detaching kernel driver from USB device... trying again to claim USB device... [please, keep the traffic on the list] 2007/2/23, A.Lizard <[EMAIL PROTECTED]>: At 05:12 AM 2/23/07, you wrote: >Not sure you've seen it, so I step up: > >in the "ps" output, there is: hald-addon-hid-ups >this is an HAL addon, based upon the same code as our old hidups... >this is what I'm working on in NUT to replace. >I've not thought at it before since I've completely disabled hiddev >support in kernel for MGE units, but any other brand that is HID >compliant, should face it. > >the detach method might fail since the driver is _used_, not only loaded! > >Note that the above is the reason why I've not thrown out _our_ HAL >support: we still need a way to instruct the HAL autoloaded drivers >not to run if we want to use the classic nut . And this will be done >through the new config (nut.conf -> MODE) > >I've no clean solution apart from removing / renaming the addon... So I should try finding the addon and removing or renaming it? right simply unplug your UPS' USB cord rename the hald-addon-hid-ups file (should be somewhere in /usr/lib/hal ; use rpm or deb to query the content exact and path of the hal package) plug back your USB cord, retry the previous tests. Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ member The Internet Society (ISOC), The HTML Writers Guild. "You can't have in a democracy various groups with arms - you have to have the state with a monopoly on power." Condoleeza Rice, US Secretary of State Personal Website http://www.ecis.com/~alizard business Website http://www.reptilelabs.com backup address (if ALL else fails) [EMAIL PROTECTED] PGP 8.0 key available by request or keyserver. Download PGP from: http://www.pgpi.org for e-mail privacy. Disaster prep info: http://www.ecis.com/~alizard/y2k.html ***Looking for INTELLIGENT new technology public policy alternatives?*** http://www.ecis.com/~alizard/technology.html ___ Nut-upsuser mailing list
Re: [Nut-upsuser] nut suddenly stopped working...
At 01:01 PM 2/23/07, you wrote: [please, keep the traffic on the list] Now that I'm awake, no problem. This is how message traffic is showing up from the list: Date: Fri, 23 Feb 2007 21:27:57 +0100 From: "Arnaud Quette" <[EMAIL PROTECTED]> To: "Peter Selinger" <[EMAIL PROTECTED]> Subject: Re: [Nut-upsuser] how do I find the association between a usb Cc: "A.Lizard" <[EMAIL PROTECTED]>, nut-upsuser@lists.alioth.debian.org In-Reply-To: <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> x-security: VScan v0.85 - http://hoopajoo.net x-virus-found: no So my default "hit reply" reflex sends e-mail to the poster, not to the list. 2007/2/23, A.Lizard <[EMAIL PROTECTED]>: At 05:12 AM 2/23/07, you wrote: >Not sure you've seen it, so I step up: > >in the "ps" output, there is: hald-addon-hid-ups >this is an HAL addon, based upon the same code as our old hidups... >this is what I'm working on in NUT to replace. >I've not thought at it before since I've completely disabled hiddev >support in kernel for MGE units, but any other brand that is HID >compliant, should face it. > >the detach method might fail since the driver is _used_, not only loaded! > >Note that the above is the reason why I've not thrown out _our_ HAL >support: we still need a way to instruct the HAL autoloaded drivers >not to run if we want to use the classic nut . And this will be done >through the new config (nut.conf -> MODE) > >I've no clean solution apart from removing / renaming the addon... So I should try finding the addon and removing or renaming it? right simply unplug your UPS' USB cord rename the hald-addon-hid-ups file (should be somewhere in /usr/lib/hal ; use rpm or deb to query the content exact and path of the hal package) plug back your USB cord, retry the previous tests. thanks, I'll give it a try. A.Lizard Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ member The Internet Society (ISOC), The HTML Writers Guild. "You can't have in a democracy various groups with arms - you have to have the state with a monopoly on power." Condoleeza Rice, US Secretary of State Personal Website http://www.ecis.com/~alizard business Website http://www.reptilelabs.com backup address (if ALL else fails) [EMAIL PROTECTED] PGP 8.0 key available by request or keyserver. Download PGP from: http://www.pgpi.org for e-mail privacy. Disaster prep info: http://www.ecis.com/~alizard/y2k.html ***Looking for INTELLIGENT new technology public policy alternatives?*** http://www.ecis.com/~alizard/technology.html ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut suddenly stopped working...
[please, keep the traffic on the list] 2007/2/23, A.Lizard <[EMAIL PROTECTED]>: At 05:12 AM 2/23/07, you wrote: >Not sure you've seen it, so I step up: > >in the "ps" output, there is: hald-addon-hid-ups >this is an HAL addon, based upon the same code as our old hidups... >this is what I'm working on in NUT to replace. >I've not thought at it before since I've completely disabled hiddev >support in kernel for MGE units, but any other brand that is HID >compliant, should face it. > >the detach method might fail since the driver is _used_, not only loaded! > >Note that the above is the reason why I've not thrown out _our_ HAL >support: we still need a way to instruct the HAL autoloaded drivers >not to run if we want to use the classic nut . And this will be done >through the new config (nut.conf -> MODE) > >I've no clean solution apart from removing / renaming the addon... So I should try finding the addon and removing or renaming it? right simply unplug your UPS' USB cord rename the hald-addon-hid-ups file (should be somewhere in /usr/lib/hal ; use rpm or deb to query the content exact and path of the hal package) plug back your USB cord, retry the previous tests. Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut suddenly stopped working...
Not sure you've seen it, so I step up: in the "ps" output, there is: hald-addon-hid-ups this is an HAL addon, based upon the same code as our old hidups... this is what I'm working on in NUT to replace. I've not thought at it before since I've completely disabled hiddev support in kernel for MGE units, but any other brand that is HID compliant, should face it. the detach method might fail since the driver is _used_, not only loaded! Note that the above is the reason why I've not thrown out _our_ HAL support: we still need a way to instruct the HAL autoloaded drivers not to run if we want to use the classic nut . And this will be done through the new config (nut.conf -> MODE) I've no clean solution apart from removing / renaming the addon... 2007/2/22, Peter Selinger <[EMAIL PROTECTED]>: This is perhaps a permissions problem. You need to give newhidups the "-u root" option, or else it will drop root privileges and probably not be able to open the device. Also, the newhidups driver has no "start" argument. Try this: kill all running drivers, and stop upsd and upsmon. Then: /lib/nut/newhidups -u root -DD -a belkin-ups -- Peter A.Lizard wrote: > > suAt 09:08 AM 2/21/07, you wrote: > looks like you were right, but even with the process killed the problem > doesn't go away. Chalk up the typos in the following to my starting this > before finishing my first cup of coffee. > > thanks > A.Lizard > > [EMAIL PROTECTED]:~$ ps -ef | grep ups > root 2659 1 0 12:30 ?00:00:00 /usr/sbin/cupsd > root 2686 2676 0 12:30 ?00:00:00 hald-addon-hid-ups: > listening on /dev/usb/hiddev0 > nut 2825 1 0 12:30 ?00:00:00 /sbin/upsd > root 2827 1 0 12:30 ?00:00:00 /sbin/upsmon > nut 2828 2827 0 12:30 ?00:00:00 /sbin/upsmon > [EMAIL PROTECTED]:~$ su > Password: > terrarium:/home/alizard# kill -9 2886 > bash: kill: (2886) - No such process > terrarium:/home/alizard# kill -9 2686 > terrarium:/home/alizard# /etc/init.d/nut stop > Stopping Network UPS Tools: (upsdrvctl failed) upsd upsmon. > terrarium:/home/alizard# /etc/init.d/nut start > Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon. > terrarium:/home/alizard# ps -sf | grep ups > Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html > 0 9029 > S+ pts/1 0:00 \_ grep ups > terrarium:/home/alizard# ps -ef | grep ups > root 2659 1 0 12:30 ?00:00:00 /usr/sbin/cupsd > nut 9010 1 0 12:40 ?00:00:00 /sbin/upsd > root 9012 1 0 12:40 ?00:00:00 /sbin/upsmon > nut 9013 9012 0 12:40 ?00:00:00 /sbin/upsmon > root 9034 8950 0 12:41 pts/100:00:00 grep ups > terrarium:/home/alizard# /etc/init.d/nut stop > Stopping Network UPS Tools: (upsdrvctl failed) upsd upsmon. > terrarium:/home/alizard# ps -ef | grep ups > root 2659 1 0 12:30 ?00:00:00 /usr/sbin/cupsd > root 9050 8950 0 12:42 pts/100:00:00 grep ups > terrarium:/home/alizard# exit > exit > [EMAIL PROTECTED]:~$ /etc/init.d/nut start > Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon. > [EMAIL PROTECTED]:~$ newhidups -a belkin-ups > bash: newhidups: command not found > [EMAIL PROTECTED]:~$ su root > Password: > terrarium:/home/alizard# newhidups -a belkin-ups start > bash: newhidups: command not found > terrarium:/home/alizard# /sbin/newhidups -a belkin-ups start~ > bash: /sbin/newhidups: No such file or directory > terrarium:/home/alizard# locate newhidups > /home/alizard/Desktop/FC6install-img/newhidups-problem.html > /home/alizard/Desktop/FC6install-img/newhidups-use-dev-tree.html > /home/alizard/install/nut-usb/lib/nut/newhidups > /home/alizard/install/nut-usb/usr/share/man/man8/newhidups.8.gz > /home/alizard/linux_info/download/nut-2.0.4/drivers/newhidups > /home/alizard/linux_info/download/nut-2.0.4/drivers/newhidups.c > /home/alizard/linux_info/download/nut-2.0.4/drivers/newhidups.h > /home/alizard/linux_info/download/nut-2.0.4/drivers/newhidups.o > /home/alizard/linux_info/download/nut-2.0.4/man/newhidups.8 > /home/alizard/win/business/article-archive-2006-2007/Linux-UPS/nuts-problems/newhidups-man.html > /lib/nut/newhidups > /usr/share/man/man8/newhidups.8.gz > terrarium:/home/alizard# /lib/nut/newhidups -a belkin-ups start~ > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) > No matching HID UPS found > terrarium:/home/alizard# /lib/nut/newhidups -DD -a belkin-ups start > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) > debug level is '2' > Checking device (/) (002/001) > - VendorID: > - ProductID: > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device does not match - skipping > Checking device (04A9/220E) (001/009) > - VendorID: 04a9 > - ProductID: 220e > - Manufacturer:
Re: [Nut-upsuser] nut suddenly stopped working...
This is perhaps a permissions problem. You need to give newhidups the "-u root" option, or else it will drop root privileges and probably not be able to open the device. Also, the newhidups driver has no "start" argument. Try this: kill all running drivers, and stop upsd and upsmon. Then: /lib/nut/newhidups -u root -DD -a belkin-ups -- Peter A.Lizard wrote: > > suAt 09:08 AM 2/21/07, you wrote: > looks like you were right, but even with the process killed the problem > doesn't go away. Chalk up the typos in the following to my starting this > before finishing my first cup of coffee. > > thanks > A.Lizard > > [EMAIL PROTECTED]:~$ ps -ef | grep ups > root 2659 1 0 12:30 ?00:00:00 /usr/sbin/cupsd > root 2686 2676 0 12:30 ?00:00:00 hald-addon-hid-ups: > listening on /dev/usb/hiddev0 > nut 2825 1 0 12:30 ?00:00:00 /sbin/upsd > root 2827 1 0 12:30 ?00:00:00 /sbin/upsmon > nut 2828 2827 0 12:30 ?00:00:00 /sbin/upsmon > [EMAIL PROTECTED]:~$ su > Password: > terrarium:/home/alizard# kill -9 2886 > bash: kill: (2886) - No such process > terrarium:/home/alizard# kill -9 2686 > terrarium:/home/alizard# /etc/init.d/nut stop > Stopping Network UPS Tools: (upsdrvctl failed) upsd upsmon. > terrarium:/home/alizard# /etc/init.d/nut start > Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon. > terrarium:/home/alizard# ps -sf | grep ups > Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html > 0 9029 > S+ pts/1 0:00 \_ grep ups > terrarium:/home/alizard# ps -ef | grep ups > root 2659 1 0 12:30 ?00:00:00 /usr/sbin/cupsd > nut 9010 1 0 12:40 ?00:00:00 /sbin/upsd > root 9012 1 0 12:40 ?00:00:00 /sbin/upsmon > nut 9013 9012 0 12:40 ?00:00:00 /sbin/upsmon > root 9034 8950 0 12:41 pts/100:00:00 grep ups > terrarium:/home/alizard# /etc/init.d/nut stop > Stopping Network UPS Tools: (upsdrvctl failed) upsd upsmon. > terrarium:/home/alizard# ps -ef | grep ups > root 2659 1 0 12:30 ?00:00:00 /usr/sbin/cupsd > root 9050 8950 0 12:42 pts/100:00:00 grep ups > terrarium:/home/alizard# exit > exit > [EMAIL PROTECTED]:~$ /etc/init.d/nut start > Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon. > [EMAIL PROTECTED]:~$ newhidups -a belkin-ups > bash: newhidups: command not found > [EMAIL PROTECTED]:~$ su root > Password: > terrarium:/home/alizard# newhidups -a belkin-ups start > bash: newhidups: command not found > terrarium:/home/alizard# /sbin/newhidups -a belkin-ups start~ > bash: /sbin/newhidups: No such file or directory > terrarium:/home/alizard# locate newhidups > /home/alizard/Desktop/FC6install-img/newhidups-problem.html > /home/alizard/Desktop/FC6install-img/newhidups-use-dev-tree.html > /home/alizard/install/nut-usb/lib/nut/newhidups > /home/alizard/install/nut-usb/usr/share/man/man8/newhidups.8.gz > /home/alizard/linux_info/download/nut-2.0.4/drivers/newhidups > /home/alizard/linux_info/download/nut-2.0.4/drivers/newhidups.c > /home/alizard/linux_info/download/nut-2.0.4/drivers/newhidups.h > /home/alizard/linux_info/download/nut-2.0.4/drivers/newhidups.o > /home/alizard/linux_info/download/nut-2.0.4/man/newhidups.8 > /home/alizard/win/business/article-archive-2006-2007/Linux-UPS/nuts-problems/newhidups-man.html > /lib/nut/newhidups > /usr/share/man/man8/newhidups.8.gz > terrarium:/home/alizard# /lib/nut/newhidups -a belkin-ups start~ > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) > No matching HID UPS found > terrarium:/home/alizard# /lib/nut/newhidups -DD -a belkin-ups start > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) > debug level is '2' > Checking device (/) (002/001) > - VendorID: > - ProductID: > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 002 > Trying to match device > Device does not match - skipping > Checking device (04A9/220E) (001/009) > - VendorID: 04a9 > - ProductID: 220e > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 001 > Trying to match device > Device does not match - skipping > Checking device (050D/0551) (001/008) > - VendorID: 050d > - ProductID: 0551 > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 001 > Trying to match device > Device matches > failed to claim USB device, trying 2 more time(s)... > detaching kernel driver from USB device... > failed to detach kernel driver from USB device... > trying again to claim USB device... > failed to claim USB device, trying 1 more time(s)... > detaching kernel driver from USB device... > failed to detach kernel driver from USB device... > trying again to claim USB device... > failed to claim USB device, trying 0 more time(s)... > detaching kernel driver
Re: [Nut-upsuser] nut suddenly stopped working...
suAt 09:08 AM 2/21/07, you wrote: looks like you were right, but even with the process killed the problem doesn't go away. Chalk up the typos in the following to my starting this before finishing my first cup of coffee. thanks A.Lizard [EMAIL PROTECTED]:~$ ps -ef | grep ups root 2659 1 0 12:30 ?00:00:00 /usr/sbin/cupsd root 2686 2676 0 12:30 ?00:00:00 hald-addon-hid-ups: listening on /dev/usb/hiddev0 nut 2825 1 0 12:30 ?00:00:00 /sbin/upsd root 2827 1 0 12:30 ?00:00:00 /sbin/upsmon nut 2828 2827 0 12:30 ?00:00:00 /sbin/upsmon [EMAIL PROTECTED]:~$ su Password: terrarium:/home/alizard# kill -9 2886 bash: kill: (2886) - No such process terrarium:/home/alizard# kill -9 2686 terrarium:/home/alizard# /etc/init.d/nut stop Stopping Network UPS Tools: (upsdrvctl failed) upsd upsmon. terrarium:/home/alizard# /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon. terrarium:/home/alizard# ps -sf | grep ups Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html 0 9029 S+ pts/1 0:00 \_ grep ups terrarium:/home/alizard# ps -ef | grep ups root 2659 1 0 12:30 ?00:00:00 /usr/sbin/cupsd nut 9010 1 0 12:40 ?00:00:00 /sbin/upsd root 9012 1 0 12:40 ?00:00:00 /sbin/upsmon nut 9013 9012 0 12:40 ?00:00:00 /sbin/upsmon root 9034 8950 0 12:41 pts/100:00:00 grep ups terrarium:/home/alizard# /etc/init.d/nut stop Stopping Network UPS Tools: (upsdrvctl failed) upsd upsmon. terrarium:/home/alizard# ps -ef | grep ups root 2659 1 0 12:30 ?00:00:00 /usr/sbin/cupsd root 9050 8950 0 12:42 pts/100:00:00 grep ups terrarium:/home/alizard# exit exit [EMAIL PROTECTED]:~$ /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon. [EMAIL PROTECTED]:~$ newhidups -a belkin-ups bash: newhidups: command not found [EMAIL PROTECTED]:~$ su root Password: terrarium:/home/alizard# newhidups -a belkin-ups start bash: newhidups: command not found terrarium:/home/alizard# /sbin/newhidups -a belkin-ups start~ bash: /sbin/newhidups: No such file or directory terrarium:/home/alizard# locate newhidups /home/alizard/Desktop/FC6install-img/newhidups-problem.html /home/alizard/Desktop/FC6install-img/newhidups-use-dev-tree.html /home/alizard/install/nut-usb/lib/nut/newhidups /home/alizard/install/nut-usb/usr/share/man/man8/newhidups.8.gz /home/alizard/linux_info/download/nut-2.0.4/drivers/newhidups /home/alizard/linux_info/download/nut-2.0.4/drivers/newhidups.c /home/alizard/linux_info/download/nut-2.0.4/drivers/newhidups.h /home/alizard/linux_info/download/nut-2.0.4/drivers/newhidups.o /home/alizard/linux_info/download/nut-2.0.4/man/newhidups.8 /home/alizard/win/business/article-archive-2006-2007/Linux-UPS/nuts-problems/newhidups-man.html /lib/nut/newhidups /usr/share/man/man8/newhidups.8.gz terrarium:/home/alizard# /lib/nut/newhidups -a belkin-ups start~ Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) No matching HID UPS found terrarium:/home/alizard# /lib/nut/newhidups -DD -a belkin-ups start Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) debug level is '2' Checking device (/) (002/001) - VendorID: - ProductID: - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 002 Trying to match device Device does not match - skipping Checking device (04A9/220E) (001/009) - VendorID: 04a9 - ProductID: 220e - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 001 Trying to match device Device does not match - skipping Checking device (050D/0551) (001/008) - VendorID: 050d - ProductID: 0551 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 001 Trying to match device Device matches failed to claim USB device, trying 2 more time(s)... detaching kernel driver from USB device... failed to detach kernel driver from USB device... trying again to claim USB device... failed to claim USB device, trying 1 more time(s)... detaching kernel driver from USB device... failed to detach kernel driver from USB device... trying again to claim USB device... failed to claim USB device, trying 0 more time(s)... detaching kernel driver from USB device... failed to detach kernel driver from USB device... trying again to claim USB device... Unable to get HID descriptor (error sending control message: Operation not permitted) HID descriptor retrieved (Reportlen = 424) Unable to get Report descriptor (-1): Operation not permitted Checking device (04A9/1094) (001/007) - VendorID: 04a9 - ProductID: 1094 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 001 Trying to match device Device does not match - skipping Checking device (058F/9254) (001/006) - VendorID: 058f - ProductID: 9254 - M
Re: [Nut-upsuser] nut suddenly stopped working...
This looks like another driver is already attached to your Belkin. Perhaps you already have a copy of newhidups running in the background, or perhaps as a zombie process left over from previous experiments. Try ps -ef | grep ups to see what is running, and kill it if necessary. -- Peter A.Lizard wrote: > > I almost had nut_2.0.5-3_i386.deb (from > http://packages.debian.org/unstable/admin/nut - installed via dpkg, not via > repository) working: > > * problems with getting it to come up during boot > * monitoring via knutclient was OK > * shutdown on low battery worked adequately, if not quite as described) > > and newhidups suddenly stopped talking to my Belkin F6C550-AVR . It's only > been in use for a couple of months, so I doubt it's a hardware problem. And > in general, the USB setup works, my printer runs just fine. > > also installed - nut-usb nut-dev (2.0.5-3) > > Computer hardware: > Biostar Geforce 6100 AM2 (integrated motherboard nvidia chipsets) > OS: Debian Etch > terrarium:/home/alizard/install# uname -a > Linux terrarium 2.6.18-3-486 #1 Mon Dec 4 15:59:52 UTC 2006 i686 GNU/Linux > > > thanks > A.Lizard > > terrarium:/etc/default# /lib/nut/newhidups -DD port=auto > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) > > Checking device (050D/0551) (001/008) > - VendorID: 050d > - ProductID: 0551 > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 001 > Trying to match device > Device matches > failed to claim USB device, trying 2 more time(s)... > detaching kernel driver from USB device... > failed to detach kernel driver from USB device... > trying again to claim USB device... > failed to claim USB device, trying 1 more time(s)... > detaching kernel driver from USB device... > failed to detach kernel driver from USB device... > trying again to claim USB device... > failed to claim USB device, trying 0 more time(s)... > detaching kernel driver from USB device... > failed to detach kernel driver from USB device... > trying again to claim USB device... > Unable to get HID descriptor (error sending control message: Operation not > permitted) > HID descriptor retrieved (Reportlen = 424) > Unable to get Report descriptor (-1): Operation not permitted > > Checking device (/) (001/001) > - VendorID: > - ProductID: > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 001 > Trying to match device > Device does not match - skipping > No appropriate HID device found > member The Internet Society (ISOC), The HTML Writers Guild. > "You can't have in a democracy various groups with arms - you have to have > the state with a monopoly on power." Condoleeza Rice, US Secretary of State > Personal Website http://www.ecis.com/~alizard > business Website http://www.reptilelabs.com > backup address (if ALL else fails) [EMAIL PROTECTED] > PGP 8.0 key available by request or keyserver. Download PGP from: > http://www.pgpi.org for e-mail privacy. > Disaster prep info: http://www.ecis.com/~alizard/y2k.html > ***Looking for INTELLIGENT new technology public policy > alternatives?*** http://www.ecis.com/~alizard/technology.html > > > ___ > Nut-upsuser mailing list > Nut-upsuser@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser > ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
