Re: [Nut-upsuser] nut problem on boot/restart
hi 2011/5/14 pepe jose dynami...@hotmail.com Hi Aquette, please, let my login name for computers... call me either Arnaud, Arnaud Quette, ... ;-) Thank you very much for responding. I try to up a bit more NUT's ranking with $ sudo mv /etc/rc2.d/S50nut /etc/rc2.d/s99nut as you say. does it mean that you confirm your issue is fixed? cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software 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 problem on boot/restart
Hi, 2011/5/8 pepe jose dynami...@hotmail.com hi! When I turn on my pc everything works fine, but if I restart fails (I'm not sure if this is true at 100%)(then, i can do 'sudo /etc/init.d/nut restart' and it works) But what is certain is that sometimes when start up the pc it works and sometimes fails. It seems like attempting to use the USB bus before it has initialized. how I can fix this? thanks so much! my setup: core i5, SSD corsair, 8GB ram, msi p67a-gd65 Ubuntu 11.04 64bit NUT v2.6 deb from ubuntu UPS Soyntec Sekury C 800 USB syslog: Apr 30 21:58:16 tron upsd[1251]: listening on 127.0.0.1 port 3493 Apr 30 21:58:16 tron upsd[1251]: Can't connect to UPS [soyntec] (blazer_usb-soyntec): No such file or directory Apr 30 21:58:16 tron upsd[1253]: Startup successful Apr 30 21:58:16 tron upsmon[1256]: Startup successful Apr 30 21:58:16 tron upsd[1253]: User monuser 127.0.0.1 logged into UPS [soyntec] Apr 30 21:58:16 tron upsmon[1259]: Poll UPS [soyntec localhost] failed - Driver not connected Apr 30 21:58:16 tron upsmon[1259]: Communications with UPS soyntec localhost lost output (sudo /lib/nut/blazer_usb -D -a soyntec) attachedhttp://lists.alioth.debian.org/mailman/listinfo/nut-upsuser as per your provided info, this indeed resemble to a udev related issue. this is quite probably due to the upstart + sysV mix that is in use in natty, with udev being an upstart job, while nut is still a sysV (compatibility) one. I've sadly not had time to install an actual natty, and pbuilder disable udev. the final solution will come with NUT conversion to upstart (I had a session at the UDS today on that). for the time being, you can try to up a bit more NUT's ranking by doing: $ sudo mv /etc/rc2.d/S50nut /etc/rc2.d/s99nut and check if the situation has improved. I'll give a word tomorrow to upstart developers on this. cheers, Arnaud (from UDS Budapest) -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software 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
[Nut-upsuser] nut problem on boot/restart
hi! When I turn on my pc everything works fine, but if I restart fails (I'm not sure if this is true at 100%)(then, i can do 'sudo /etc/init.d/nut restart' and it works) But what is certain is that sometimes when start up the pc it works and sometimes fails. It seems like attempting to use the USB bus before it has initialized. how I can fix this? thanks so much! my setup:core i5, SSD corsair, 8GB ram, msi p67a-gd65Ubuntu 11.04 64bitNUT v2.6 deb from ubuntuUPS Soyntec Sekury C 800 USB syslog:Apr 30 21:58:16 tron upsd[1251]: listening on 127.0.0.1 port 3493Apr 30 21:58:16 tron upsd[1251]: Can't connect to UPS [soyntec] (blazer_usb-soyntec): No such file or directoryApr 30 21:58:16 tron upsd[1253]: Startup successfulApr 30 21:58:16 tron upsmon[1256]: Startup successfulApr 30 21:58:16 tron upsd[1253]: User monuser 127.0.0.1 logged into UPS [soyntec]Apr 30 21:58:16 tron upsmon[1259]: Poll UPS [soyntec localhost] failed - Driver not connectedApr 30 21:58:16 tron upsmon[1259]: Communications with UPS soyntec localhost lost output (sudo /lib/nut/blazer_usb -D -a soyntec) attached Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.0) 0.00 send_to_all: SETINFO driver.parameter.port auto 0.56 debug level is '5' 0.132441 Checking device (1D6B/0003) (004/001) 0.132483 - VendorID: 1d6b 0.132490 - ProductID: 0003 0.132495 - Manufacturer: unknown 0.132501 - Product: unknown 0.132506 - Serial Number: unknown 0.132511 - Bus: 004 0.132516 Trying to match device 0.132522 Device does not match - skipping 0.132531 Checking device (1D6B/0003) (003/001) 0.132547 - VendorID: 1d6b 0.132553 - ProductID: 0003 0.132559 - Manufacturer: unknown 0.132564 - Product: unknown 0.132569 - Serial Number: unknown 0.132574 - Bus: 003 0.132579 Trying to match device 0.132584 Device does not match - skipping 0.132592 Checking device (8087/0024) (002/002) 0.132605 - VendorID: 8087 0.132610 - ProductID: 0024 0.132615 - Manufacturer: unknown 0.132621 - Product: unknown 0.132626 - Serial Number: unknown 0.132630 - Bus: 002 0.132635 Trying to match device 0.132641 Device does not match - skipping 0.132648 Checking device (1D6B/0002) (002/001) 0.132663 - VendorID: 1d6b 0.132669 - ProductID: 0002 0.132674 - Manufacturer: unknown 0.132679 - Product: unknown 0.132684 - Serial Number: unknown 0.132689 - Bus: 002 0.132694 Trying to match device 0.132699 Device does not match - skipping 0.132706 Checking device (0665/5161) (001/010) 0.136925 - VendorID: 0665 0.136941 - ProductID: 5161 0.136948 - Manufacturer: Cypress Semiconductor 0.136954 - Product: USB to Serial 0.136960 - Serial Number: unknown 0.136965 - Bus: 001 0.136971 Trying to match device 0.136977 Device matches 0.136990 failed to claim USB device: could not claim interface 0: Device or resource busy 0.193524 detached kernel driver from USB device... 0.194699 send_to_all: SETINFO ups.vendorid 0665 0.194717 send_to_all: SETINFO ups.productid 5161 0.194729 send_to_all: SETINFO device.type ups 0.194737 send_to_all: SETINFO driver.version 2.6.0 0.194744 send_to_all: SETINFO driver.version.internal 0.03 0.194752 send_to_all: SETINFO driver.name blazer_usb 0.194758 Trying megatec protocol... 0.195462 send: Q1 0.563527 read: (230.7 230.7 230.7 019 50.1 13.5 25.0 1001 0.563573 send_to_all: SETINFO input.voltage 230.7 0.563585 send_to_all: SETINFO input.voltage.fault 230.7 0.563594 send_to_all: SETINFO output.voltage 230.7 0.563619 send_to_all: SETINFO ups.load 19 0.563628 send_to_all: SETINFO input.frequency 50.1 0.563638 send_to_all: SETINFO battery.voltage 13.50 0.563647 send_to_all: SETINFO ups.temperature 25.0 0.563655 send_to_all: SETINFO beeper.status enabled 0.563663 send_to_all: SETINFO ups.type offline / line interactive 0.563676 send_to_all: SETINFO ups.status OL 0.563683 Status read in 1 tries 0.563689 Supported UPS detected with megatec protocol 0.564446 send: F 0.755438 read: #230.0 003 12.00 50.0 0.755467 send_to_all: SETINFO input.voltage.nominal 230 0.755477 send_to_all: SETINFO input.current.nominal 3.0 0.755488 send_to_all: SETINFO battery.voltage.nominal 12.0 0.755497 send_to_all: SETINFO input.frequency.nominal 50 0.755510 Ratings read in 1 tries 0.756084 send: I 1.756636 read: could not claim interface 0: Device or resource busy 1.756660 blazer_vendor: short reply 1.756668 Vendor information read 1 failed 1.757836 send: I 2.758276
Re: [Nut-upsuser] nut problem on boot/restart
Citeren Jose Álvarez dynami...@hotmail.com: When I turn on my pc everything works fine, but if I restart fails (I'm not sure if this is true at 100%) (then, i can do 'sudo /etc/init.d/nut restart' and it works) This usually means that you're attempting to use the USB bus before it has initialized. But what is certain is that sometimes when start up the pc it works and sometimes fails, can be a problem with the start time (i have a fast ssd) and the initialization of the driver and the usb port? The latter. [...] Don't inline log files. The formatting will usually not be preserved and they become very hard to read. Please attach log messages (and preferably, gzip them too to save bandwidth and prevent the mailinglist from rejecting them because of size). Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut problem on boot/restart
sorry, I realized that no kept well linebreaks when I had sent the message This usually means that you're attempting to use the USB bus before it has initialized. how I can fix this? thanks so much! Date: Sun, 1 May 2011 13:38:51 +0200 From: nut+us...@de-korte.org To: nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] nut problem on boot/restart Citeren Jose Álvarez : When I turn on my pc everything works fine, but if I restart fails (I'm not sure if this is true at 100%) (then, i can do 'sudo /etc/init.d/nut restart' and it works) This usually means that you're attempting to use the USB bus before it has initialized. But what is certain is that sometimes when start up the pc it works and sometimes fails, can be a problem with the start time (i have a fast ssd) and the initialization of the driver and the usb port? The latter. [...] Don't inline log files. The formatting will usually not be preserved and they become very hard to read. Please attach log messages (and preferably, gzip them too to save bandwidth and prevent the mailinglist from rejecting them because of size). Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ 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
