[Nut-upsuser] nut problem on boot/restart

[pepe jose]

Hi Aquette, 

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.
thanks!
Date: Thu, 12 May 2011 22:27:54 +0200
Subject: Re: [Nut-upsuser] nut problem on boot/restart
From: aquette.dev at gmail.com
To: dynamix66 at hotmail.com
CC: nut-upsuser at lists.alioth.debian.org

Hi,

2011/5/8 pepe jose <dynamix66 at 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-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 successful
Apr 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 connected
Apr 30 21:58:16 tron upsmon[1259]: Communications with UPS soyntec localhost lost
output (sudo /lib/nut/blazer_usb -DDDDD -a soyntec) attached


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 R&D - 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/

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20110514/bf57f54e/attachment.htm>