[Nut-upsuser] communications lost/established

Douglas Parsons doug at parsonsemail.com
Thu Mar 18 22:02:11 UTC 2010


One suggestion would to be to determine if the serial port is working and
what it is named without Nut involved. Use a terminal program and a loopback
or some known device to test and confirm the port. There are several cases
in the archives that talk about testing serial ports as well as Google.

On Mar 18, 2010 5:19 PM, "ricman" <ricman at neomedia.it> wrote:

Scrive Arjen de Korte <nut+users at de-korte.org <nut%2Busers at de-korte.org>>:

> Citeren ricman <ricman at neomedia.it>: > > > here are a couple of logs: log
1 and 2 are pretty simi...
serial-pci card installed and ups connected.
since it is the only serial port in use i guess it is ttyS0... anyway i
tried
ttyS0 and ttyS1 but it doesn't work.
connecting or not the cable the result doesn't change


Mar 18 22:02:40 maialinux upsd[2895]: listening on 127.0.0.1 port 3493
Mar 18 22:02:40 maialinux upsd[2895]: Can't connect to UPS [myups]
(blazer_ser-myups): No such file or directory
Mar 18 22:02:40 maialinux upsd[2903]: Startup successful
Mar 18 22:02:40 maialinux upsmon[2905]: Startup successful
Mar 18 22:02:40 maialinux upsd[2903]: User local_mon at 127.0.0.1 logged into
UPS
[myups]
Mar 18 22:02:40 maialinux upsmon[2908]: Poll UPS [myups at localhost] failed -
Driver not connected
Mar 18 22:02:40 maialinux upsmon[2908]: Communications with UPS
myups at localhost
lost
Mar 18 22:02:45 maialinux upsmon[2908]: Poll UPS [myups at localhost] failed -
Driver not connected
Mar 18 22:02:45 maialinux upsmon[2908]: UPS myups at localhost is unavailable
Mar 18 22:02:50 maialinux upsmon[2908]: Poll UPS [myups at localhost] failed -
Driver not connected


debug level is '3'
Trying megatec protocol...
send: Q1
read: timeout
blazer_status: short reply
Status read 1 failed
send: Q1
read: timeout
blazer_status: short reply
Status read 2 failed
send: Q1
read: timeout
blazer_status: short reply
Status read 3 failed
Trying mustek protocol...
send: QS
read: timeout
blazer_status: short reply
Status read 1 failed
send: QS
read: timeout
blazer_status: short reply
Status read 2 failed
send: QS
read: timeout
blazer_status: short reply
Status read 3 failed
Trying megatec/old protocol...
send: D
read: timeout
blazer_status: short reply
Status read 1 failed
send: D
read: timeout
blazer_status: short reply
Status read 2 failed
send: D
read: timeout
blazer_status: short reply
Status read 3 failed
No supported UPS detected
Network UPS Tools - Megatec/Q1 protocol serial driver 1.51 (2.4.1)

where am i wrong?

_______________________________________________ Nut-upsuser mailing list
Nut-upsuser at lists.alioth....
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20100318/0a4931c5/attachment.htm>


More information about the Nut-upsuser mailing list