[Nut-upsuser] How do I resolve comm issues
Scott Tuc Ellentuch at T-B-O-H
ml at t-b-o-h.net
Tue May 9 14:04:58 UTC 2006
>
> Hi again Scott,
>
Hello again. :)
> so, I should have read that one before ;-)
>
Thats ok.
>
> > The issue is that when I went to try the mge-shut (I'm
> > doing this serial) I get :
> >
> > soekris# /usr/local/libexec/nut/mge-shut -D -D -D -D -D -D -D -D -a ellipse
> > Network UPS Tools - MGE UPS SYSTEMS/SHUT driver 0.65 (2.0.3)
> > debug level is '8'
> > entering upsdrv_initups()
> > entering setline(1)
> >
> > entering shut_ups_start()
> >
> > sent: (1 bytes) => 16
> > received: 16
> > Syncing and notification setting done
> > Communication with UPS established
> > entering shut_get_descriptor(n 21, 9)
> > entering shut_packet_send (8)
> > shut_checksum = af
> > sent: (11 bytes) => 81 88 81 06 00 21 00 00 09 00 AF
> > received: 81
> > shut_wait_ack(): Nothing received
> > Retry = 1
> > sent: (1 bytes) => 15
> > received: 81
> > shut_wait_ack(): Nothing received
> > Retry = 2
> > sent: (1 bytes) => 15
> > received: 00
> > shut_wait_ack(): Nothing received
> > Retry = 3
> > sent: (1 bytes) => 15
> > received: 00
> > shut_wait_ack(): Nothing received
> > Max tries reached while waiting for ACK, still getting errors
> > Unable to get HID Descriptor
> >
> >
> > Atleast with utalk I was getting SOMEWHERE.
>
> not much in fact. However, I already had feedback for this kind of
> setup, so you're not far of having it working ;-)
>
I like to hear that...
>
> Can you validate that the nut user can write on the /dev/cuaa1device?
>
From the config.log of the ports build :
$ ./configure --sysconfdir=/usr/local/etc/nut --localstatedir=/var/db/nut --da
tadir=/usr/local/etc/nut --with-drvpath=/usr/local/libexec/nut --with-statepath=
/var/db/nut --with-altpidpath=/var/db/nut --with-pidpath=/var/db/nut --with-linu
x-hiddev=no --with-user=uucp --with-cgi --with-cgipath=/usr/local/www/cgi-bin/nu
t --with-gd-includes=-I/usr/local/include --with-gd-libs=-L/usr/local/lib -lgd -
-prefix=/usr/local i386-portbld-freebsd5.4
So the user is UUCP....
crw-rw---- 1 uucp dialer 242, 129 May 9 09:16 /dev/cuaa1
I'm not sure a good way to test it since I can't su to uucp....
But just LOOKING at it, it should be able to... If mge-utalk could talk,
shouldn't this ?
>
>
> The current mge-shut lacks some control, but I've partly finished to
> rewritte it using the standard nut serial functions, so that will be
> corrected in some time.
>
> If it's not a permission problem, try to reset the unit using:
> 1) power off all the UPS protected load,
> 2) power off the UPS (using the front panel button),
> 3) unplug the UPS power cord, wait for the long beep, and wait
> 10 more seconds,
>
I didn't get a long beep... Only a chirp. I waited 3
minutes for a long beep, none...
>
> 4) replug and restart everything
> 5) if everything went fine, launch "mge-shut ..." and
> check that the communication is established.
>
Just to verify the ports settings :
crw-rw---- 1 uucp dialer 242, 129 May 9 10:01 /dev/cuaa1
soekris# ls -l /dev/cuaa1
crw-rw---- 1 uucp dialer 242, 129 May 9 10:01 /dev/cuaa1
soekris# /usr/local/libexec/nut/mge-shut -D -D -D -D -D -D -D -D -a ellipse
Network UPS Tools - MGE UPS SYSTEMS/SHUT driver 0.65 (2.0.3)
debug level is '8'
entering upsdrv_initups()
entering setline(1)
entering shut_ups_start()
sent: (1 bytes) => 16
received: 16
Syncing and notification setting done
Communication with UPS established
entering shut_get_descriptor(n 21, 9)
entering shut_packet_send (8)
shut_checksum = af
sent: (11 bytes) => 81 88 81 06 00 21 00 00 09 00 AF
received: 81
shut_wait_ack(): Nothing received
Retry = 1
sent: (1 bytes) => 15
received: 81
shut_wait_ack(): Nothing received
Retry = 2
sent: (1 bytes) => 15
received: 00
shut_wait_ack(): Nothing received
Retry = 3
sent: (1 bytes) => 15
received: 00
shut_wait_ack(): Nothing received
Max tries reached while waiting for ACK, still getting errors
Unable to get HID Descriptor
Tuc
More information about the Nut-upsuser
mailing list