Hi,
I've had NUT 2.6.1 on OpenIndiana working with a Tripp-Lite
ECO550. I've been playing around with the config files a
little bit, and I must have done something that messed up
the demon. I now get
wiley$ pfexec /opt/nut/sbin/upsd -DD
Network UPS Tools upsd 2.6.1
0.000000 listening on 127.0.0.1 port 3493
0.000486 listening on ::1 port 3493
0.001279 Can't connect to UPS [eco550]
(usbhid-ups-eco550): No such file or directory
0.003922 mainloop: polling 2 filedescriptors
2.013960 mainloop: no data available
2.014191 mainloop: polling 2 filedescriptors
4.024208 mainloop: no data available
4.024453 mainloop: polling 2 filedescriptors
6.034474 mainloop: no data available
6.034733 mainloop: polling 2 filedescriptors
^C 7.598418 mainloop: Interrupted system call
7.598578 Signal 2: exiting
The "0.001279" line is correct: there is no such file, but
there never was. There is only /opt/nut/bin/usbhid-ups.
Why is the demon looking for "usbhid-ups-eco550" now?
Kostas
On Aug 31, 2011, at 8:32 PM, Kostas Oikonomou wrote:> Hi, > > I've had NUT 2.6.1 on OpenIndiana working with a Tripp-Lite ECO550. > I've been playing around with the config files a little bit, and I > must have done something that messed up the demon. I now get > > wiley$ pfexec /opt/nut/sbin/upsd -DD > Network UPS Tools upsd 2.6.1 > 0.000000 listening on 127.0.0.1 port 3493 > 0.000486 listening on ::1 port 3493 > 0.001279 Can't connect to UPS [eco550] (usbhid-ups-eco550): No > such file or directory > 0.003922 mainloop: polling 2 filedescriptors > 2.013960 mainloop: no data available > 2.014191 mainloop: polling 2 filedescriptors > 4.024208 mainloop: no data available > 4.024453 mainloop: polling 2 filedescriptors > 6.034474 mainloop: no data available > 6.034733 mainloop: polling 2 filedescriptors > ^C 7.598418 mainloop: Interrupted system call > 7.598578 Signal 2: exiting > > The "0.001279" line is correct: there is no such file, but there > never was. There is only /opt/nut/bin/usbhid-ups. Why is the demon > looking for "usbhid-ups-eco550" now?Hi Kostas, It is actually looking for a Unix-domain driver state socket here, and the socket name is formed from the driver name (usbhid-ups), and the UPS name from the config file. From one of your earlier emails, I think the socket is created in /var/state/ups (the default directory).
Hi Charles, Thanks. I checked /var/state/ups, and it is an empty directory. None of the config files in nut/etc contains the string "/var/state/ups", so this must be the default. How do I troubleshoot this? Kostas> > Hi Kostas, > > It is actually looking for a Unix-domain driver state socket > here, and the socket name is formed from the driver name > (usbhid-ups), and the UPS name from the config file. From > one of your earlier emails, I think the socket is created in > /var/state/ups (the default directory).