Re: [Nut-upsuser] Can't connect to UPS [mustek] (megatec-mustek): No such file or directory
Arjen de Korte wrote: Citeren Vedran Furač vedr...@vedranf.mine.nu: NUT recently stopped working on my debian. I'm not sure which upgrade broke it. From which version did you upgrade it? Current version is 2.4.1 to which I upgraded few months ago, but I think it worked until recently (few weeks). Maybe upgrade of some other package broke it. Where is megatec-mustek file? It should be created by the driver, which apparently isn't running. Either it isn't started at all, fails to detect the UPS or isn't running with the proper permissions. Please post the output of /path/to/megatec -a mustek -D # /lib/nut/megatec -a mustek -D Network UPS Tools - Megatec protocol driver 1.6 (2.4.1) debug level is '5' DTR=1, RTS=0 Starting UPS detection process... Asking for UPS information [I]... I = FAILED [timeout] Asking for UPS status [Q1]... Q1 = OK [(226.7 226.7 226.7 045 49.9 13.9 25.0 1001] Q1 VALUES = [226.7 226.7 226.7 45.0 49.9 13.9 25.0 1001] Asking for UPS status [Q1]... Q1 = OK [(227.2 227.2 227.2 045 49.9 13.9 25.0 1001] Q1 VALUES = [227.2 227.2 227.2 45.0 49.9 13.9 25.0 1001] Asking for UPS status [Q1]... Q1 = OK [(227.2 227.2 227.2 045 49.9 13.9 25.0 1001] Q1 VALUES = [227.2 227.2 227.2 45.0 49.9 13.9 25.0 1001] Asking for UPS status [Q1]... Q1 = OK [(227.2 227.2 227.2 045 49.9 13.9 25.0 1001] Q1 VALUES = [227.2 227.2 227.2 45.0 49.9 13.9 25.0 1001] Asking for UPS status [Q1]... Q1 = OK [(227.2 227.2 227.2 045 49.9 13.9 25.0 1001] Q1 VALUES = [227.2 227.2 227.2 45.0 49.9 13.9 25.0 1001] 0 out of 5 detection attempts failed (minimum failures: 2). send_to_all: SETINFO ups.type standby Cancelling any pending shutdown or battery test. Asking for UPS information [I]... I = FAILED [timeout] send_to_all: SETINFO ups.mfr unknown send_to_all: SETINFO ups.model unknown Megatec protocol UPS detected. send_to_all: SETINFO ups.serial unknown Parameter [ignoreoff]: [false] Asking for UPS power ratings [F]... F = OK [#220.0 002 12.00 50.0] F VALUES = [220.0 2.0 12.0 50.0] send_to_all: SETINFO battery.voltage.nominal 12.0 send_to_all: SETINFO input.voltage.nominal 220.0 send_to_all: SETINFO input.frequency.nominal 50.0 12.0V battery, interval [9.7V, 13.7V]. send_to_all: SETINFO ups.delay.start 2 send_to_all: SETINFO ups.delay.shutdown 0 send_to_all: ADDCMD test.battery.start.deep send_to_all: ADDCMD test.battery.start send_to_all: ADDCMD test.battery.stop send_to_all: ADDCMD shutdown.return send_to_all: ADDCMD shutdown.stayoff send_to_all: ADDCMD shutdown.stop send_to_all: ADDCMD load.on send_to_all: ADDCMD load.off send_to_all: ADDCMD reset.input.minmax send_to_all: ADDCMD reset.watchdog send_to_all: ADDCMD beeper.toggle Done setting up the UPS. Asking for UPS status [Q1]... Q1 = OK [(227.2 227.2 227.2 045 49.9 13.9 25.0 1001] Q1 VALUES = [227.2 227.2 227.2 45.0 49.9 13.9 25.0 1001] send_to_all: SETINFO input.voltage 227.2 send_to_all: SETINFO input.voltage.fault 227.2 send_to_all: SETINFO output.voltage 227.2 send_to_all: SETINFO ups.load 45.0 send_to_all: SETINFO input.frequency 49.9 send_to_all: SETINFO battery.voltage 13.90 send_to_all: SETINFO ups.temperature 25.0 send_to_all: SETINFO battery.charge 100.0 Calculated battery charge: 100.0% send_to_all: SETINFO ups.beeper.status enabled send_to_all: SETINFO input.voltage.minimum 227.2 send_to_all: SETINFO input.voltage.maximum 227.2 send_to_all: SETINFO ups.status OL send_to_all: DATAOK dstate_init: sock /var/run/nut/megatec-mustek open on fd 5 send_to_all: SETINFO driver.version 2.4.1 send_to_all: SETINFO driver.version.internal 1.6 send_to_all: SETINFO driver.name megatec send_to_all: SETINFO driver.parameter.pollinterval 2 Asking for UPS status [Q1]... Q1 = OK [(227.2 227.6 227.2 045 49.9 13.9 25.0 1001] Q1 VALUES = [227.2 227.6 227.2 45.0 49.9 13.9 25.0 1001] send_to_all: SETINFO input.voltage.fault 227.6 Calculated battery charge: 100.0% Regards! ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Belkin support?
On Monday 01 June 2009 05:08:05 Gene Heskett wrote: On Sunday 31 May 2009, Charles Lepple wrote: On May 31, 2009, at 10:36 PM, Gene Heskett wrote: [myups] driver = mydriver port = /dev/ttyS1 cable = 1234 desc = A POS Belkin # # To find out if your driver supports any extra settings, start it with # the -h option and/or read the driver's documentation. - I now see the port is wrong, and should probably be /dev/ttyUSB1, as zero is busy here, with heyu. However, fixing that makes zero difference. Actually, for the usbhid-ups driver (with only one UPS on a machine), / etc/nut/boils down to: ### [myups] driver = usbhid-ups port = auto desc = Whatever floats your boat ### Made no diff when I pasted that in erased the other, sorry. This is the way I discover the base configuration problems: Try running the driver by hand, tweaking it in its own command line. Forget about NUT until you can run the driver itself. The driver is a program, and it can be launched alone. That way you can read the complete driver text output.i Noel er Envite signature.asc Description: This is a digitally signed message part. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't connect to UPS [mustek] (megatec-mustek): No such file or directory
Citeren Vedran Furač vedr...@vedranf.mine.nu: Where is megatec-mustek file? It should be created by the driver, which apparently isn't running. Either it isn't started at all, fails to detect the UPS or isn't running with the proper permissions. [snip] dstate_init: sock /var/run/nut/megatec-mustek open on fd 5 There is the driver socket to which the server connects. Since this is created without problems, I suspect that you forgot to start the driver in your earlier attempts. Best regards, Arjen -- Please keep list traffic on the list ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Belkin support?
On Monday 01 June 2009 05:08:05 Gene Heskett wrote: On Sunday 31 May 2009, Charles Lepple wrote: On May 31, 2009, at 10:36 PM, Gene Heskett wrote: [myups] driver = mydriver port = /dev/ttyS1 cable = 1234 desc = A POS Belkin # # To find out if your driver supports any extra settings, start it with # the -h option and/or read the driver's documentation. - I now see the port is wrong, and should probably be /dev/ttyUSB1, as zero is busy here, with heyu. However, fixing that makes zero difference. Actually, for the usbhid-ups driver (with only one UPS on a machine), / etc/nut/boils down to: ### [myups] driver = usbhid-ups port = auto desc = Whatever floats your boat ### Made no diff when I pasted that in erased the other, sorry. This is the way I discover the base configuration problems: Try running the driver by hand, tweaking it in its own command line. Forget about NUT until you can run the driver itself. The driver is a program, and it can be launched alone. That way you can read the complete driver text output. Noel er Envite signature.asc Description: This is a digitally signed message part. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Belkin support?
On Monday 01 June 2009, Manuel Wolfshant wrote: Charles Lepple wrote: On May 31, 2009, at 10:17 PM, Gene Heskett wrote: On Sunday 31 May 2009, Charles Lepple wrote: On May 31, 2009, at 2:26 PM, Gene Heskett wrote: I have the newest nut (nut-2.2.2-4.fc10.i386) from fedora 10 repos) installed and this ups (from lsusb -vv): Bus 001 Device 006: ID 050d:0751 Belkin Components Hi Gene, This device should be supported by the usbhid-ups driver. That seems not to be part of the 2.6.30-rcX kernels. The current .config has: CONFIG_USB_HID=y CONFIG_USB_HIDDEV=y CONFIG_HID_BELKIN=y I should have been more specific - usbhid-ups is a user-mode driver in NUT. It uses libusb to kick the kernel's USB HID driver off of the device, and it uses /dev/bus/usb (I forget the kernel driver name) to speak the HID protocol. I can probably dig out anything else that might be helpful. Usually you would look this up in the data/drivers.list file, but it doesn't look like the lsusb output is terribly helpful for that (Belkin seems to change the underlying hardware while keeping the model name the same). Which model do you have? The NUT README file, while not specific to Fedora, should have the rest of the info needed to set this up. (Perhaps someone with Fedora 10 experience can suggest whether the classic driver or the HAL driver would be better.) If I had to guess, I'd say the README is in / usr/share/doc/nut. - Charles It might help, if it was there: [r...@coyote ~]# locate 'nut/README' [r...@coyote ~]# [r...@coyote ~]# cd `locate 'nut/'` [r...@coyote cur]# ls 1243795177.4479.gANVC:2,RS 1243799859.4479.0TdwL 1243813905.4479.2izhm the docs are in /usr/share/doc/nut-2.2.2/ . Generally speaking, in fedora docs are usually placed in /usr/share/doc/packagename-version and the config files are in /etc/ups not in /etc/nut [r...@coyote cur]# pwd /root/Mail/nut/cur [r...@coyote cur]# I don't believe it exists in the rpms. Next? use rpm -ql for a comprehensive list of the content of the rpm. BTW, I am using FC10 myself (but with a different UPS): [wo...@wolfy ~]$ rpm -ql nut|grep README /usr/share/doc/nut-2.2.2/README /usr/share/doc/nut-2.2.2/docs/README Thanks, they are indeed there. That should get me going once I've injected sufficient caffeine. Which is still on the missing list... -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) The NRA is offering FREE Associate memberships to anyone who wants them. https://www.nrahq.org/nrabonus/accept-membership.asp You could live a better life, if you had a better mind and a better body. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Belkin support?
On Monday 01 June 2009, Noel David Torres Taño wrote: On Monday 01 June 2009 05:08:05 Gene Heskett wrote: On Sunday 31 May 2009, Charles Lepple wrote: On May 31, 2009, at 10:36 PM, Gene Heskett wrote: [myups] driver = mydriver port = /dev/ttyS1 cable = 1234 desc = A POS Belkin # # To find out if your driver supports any extra settings, start it with # the -h option and/or read the driver's documentation. - I now see the port is wrong, and should probably be /dev/ttyUSB1, as zero is busy here, with heyu. However, fixing that makes zero difference. Actually, for the usbhid-ups driver (with only one UPS on a machine), / etc/nut/boils down to: ### [myups] driver = usbhid-ups port = auto desc = Whatever floats your boat ### Made no diff when I pasted that in erased the other, sorry. This is the way I discover the base configuration problems: Try running the driver by hand, tweaking it in its own command line. Forget about NUT until you can run the driver itself. The driver is a program, and it can be launched alone. That way you can read the complete driver text output. Noel er Envite That seems to work, as in doesn't exit even if I run a second invocation of usbhid-ups -a myups, both show up at the bottom of htop's listing, and both responded to a kill from htop. The output was: [r...@coyote /]# usbhid-ups -a myups Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2) Using subdriver: Belkin HID 0.11 But no other output was seen. They ran for about 2 or 3 minutes. Since this ups outputs a continuous string of status info, there must be something doofy in the connection. I'll check when I am awake, ERR_NOTSUFFICIENT_CAFFEINE right now. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) The NRA is offering FREE Associate memberships to anyone who wants them. https://www.nrahq.org/nrabonus/accept-membership.asp Traffic signals in New York are just rough guidelines. -- David Letterman ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Belking support?
This may be a little late, but experience teaches me not to buy anything from Belkin. Regards, H. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Belkin support?
Citeren Gene Heskett gene.hesk...@gmail.com: That seems to work, as in doesn't exit even if I run a second invocation of usbhid-ups -a myups, both show up at the bottom of htop's listing, and both responded to a kill from htop. The output was: [r...@coyote /]# usbhid-ups -a myups Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2) Using subdriver: Belkin HID 0.11 But no other output was seen. They ran for about 2 or 3 minutes. Since this ups outputs a continuous string of status info, there must be something doofy in the connection. I'll check when I am awake, ERR_NOTSUFFICIENT_CAFFEINE right now. This is right what we expect. You clearly first need to read up on the README and INSTALL files, since these will explain how to set this up. Looking at the above, it is quite clear that your UPS is indeed supported, but you didn't set NUT up properly yet. We have been thinking about setting up a configuration wizard, but so far we're lacking the resources to do this. Sorry about that. Best regards, Arjen -- Please keep list traffic on the list ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Belkin support?
On Monday 01 June 2009, Arjen de Korte wrote: Citeren Gene Heskett gene.hesk...@gmail.com: That seems to work, as in doesn't exit even if I run a second invocation of usbhid-ups -a myups, both show up at the bottom of htop's listing, and both responded to a kill from htop. The output was: [r...@coyote /]# usbhid-ups -a myups Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2) Using subdriver: Belkin HID 0.11 But no other output was seen. They ran for about 2 or 3 minutes. Since this ups outputs a continuous string of status info, there must be something doofy in the connection. I'll check when I am awake, ERR_NOTSUFFICIENT_CAFFEINE right now. This is right what we expect. You clearly first need to read up on the README and INSTALL files, since these will explain how to set this up. Looking at the above, it is quite clear that your UPS is indeed supported, but you didn't set NUT up properly yet. We have been thinking about setting up a configuration wizard, but so far we're lacking the resources to do this. Sorry about that. It sure would be a nice addition, hint hint. :) Best regards, Arjen Thanks Arjen -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) The NRA is offering FREE Associate memberships to anyone who wants them. https://www.nrahq.org/nrabonus/accept-membership.asp I am a bookaholic. If you are a decent person, you will not sell me another book. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
