search for: shut_ups_start

...(which is not always the case), it usually lost it again after a while. ~# /usr/local/libexec/nut/oldmge-shut -DD -a ups-filesrv01 Network UPS Tools - Eaton / SHUT driver 0.70 (2.7.2) 0.000000 debug level is '2' 0.000882 entering upsdrv_initups() 0.001019 entering shut_ups_start() 0.028445 Communication with UPS established 0.028457 entering shut_get_descriptor(n 21, 9) 0.111394 shut_wait_ack(): ACK received 0.185328 entering shut_get_descriptor(n 01, 18) 0.273455 shut_wait_ack(): ACK received 0.423238 Device Descriptor: bLe...

...f everything is ok? > as a side note, debug timestamping is now available: ie: mge-shut -DDDT -a ... Network UPS Tools - MGE UPS SYSTEMS/SHUT driver 0.68 (2.4.1-1840:1845M) 14:27:25: debug level is '3' 14:27:25: entering upsdrv_initups() 14:27:25: entering setline(1) 14:27:25: entering shut_ups_start() ... This is effective for upsd, upsmon, upsdrvctl and the drivers by using "-T". The best, as told in the manpages, is to use it in conjunction with the debug flags (ie -D...) This should help out in troubleshooting timeframe problems. cheers, Arnaud -- Linux / Unix Expert R&D -...

...k(): Unknown byte 24 shut_wait_ack(): ACK received entering shut_get_report(id: 0a, len: 1800) shut_wait_ack(): Unknown byte 132 shut_wait_ack(): Unknown byte 136 shut_wait_ack(): Unknown byte 7 shut_wait_ack(): Unknown byte 119 Max tries reached while waiting for ACK, still getting errors entering shut_ups_start() I added the 'unknown byte x' stuff - I wanted to see what it was throwing away :) Does anyone have such a UPS working with NUT + RS232? It seems to me that the SHUT parser may be having difficulty with it but I guess it's possible data is being dropped.. I don't see any kernel...

...2.6.18 kernel (due to some ISDN driver that doesn't work with earlier kernels) 1) the most annoying is that I cannot shutdown the UPS. here is a trace : > Network UPS Tools - MGE UPS SYSTEMS/SHUT driver 0.66 (2.2.2) > debug level is '2' > entering upsdrv_initups() > entering shut_ups_start() > > Communication with UPS established > entering shut_get_descriptor(n 21, 9) > shut_wait_ack(): ACK received > entering shut_get_descriptor(n 01, 18) > shut_wait_ack(): ACK received > Device Descriptor: > bLength: 0x12 > bDescriptorType: 0x0...

...thing. Nevertheless I can't get it to react in any other way. This is what I get in both configurations: # /lib/nut/mge-shut -a mge-shut -D -D -D -D Network UPS Tools - MGE UPS SYSTEMS/SHUT driver 0.66 (2.2.2) debug level is '4' entering upsdrv_initups() entering setline(1) entering shut_ups_start() sent: (1 bytes) => 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 shut_wait_ack(): Nothing received Retry = 1 sent: (1 by...

...ost it again after a while. > > ~# /usr/local/libexec/nut/oldmge-shut -DD -a ups-filesrv01 > Network UPS Tools - Eaton / SHUT driver 0.70 (2.7.2) > 0.000000 debug level is '2' > 0.000882 entering upsdrv_initups() > 0.001019 entering shut_ups_start() > > 0.028445 Communication with UPS established > 0.028457 entering shut_get_descriptor(n 21, 9) > 0.111394 shut_wait_ack(): ACK received > 0.185328 entering shut_get_descriptor(n 01, 18) > 0.273455 shut_wait_ack(): ACK rece...

...), it usually lost it again after a > while. > > ~# /usr/local/libexec/nut/oldmge-shut -DD -a ups-filesrv01 > Network UPS Tools - Eaton / SHUT driver 0.70 (2.7.2) > 0.000000 debug level is '2' > 0.000882 entering upsdrv_initups() > 0.001019 entering shut_ups_start() > > 0.028445 Communication with UPS established > 0.028457 entering shut_get_descriptor(n 21, 9) > 0.111394 shut_wait_ack(): ACK received > 0.185328 entering shut_get_descriptor(n 01, 18) > 0.273455 shut_wait_ack(): ACK received > 0.42323...

...t again after a while. >> >> ~# /usr/local/libexec/nut/oldmge-shut -DD -a ups-filesrv01 >> Network UPS Tools - Eaton / SHUT driver 0.70 (2.7.2) >> 0.000000 debug level is '2' >> 0.000882 entering upsdrv_initups() >> 0.001019 entering shut_ups_start() >> >> 0.028445 Communication with UPS established >> 0.028457 entering shut_get_descriptor(n 21, 9) >> 0.111394 shut_wait_ack(): ACK received >> 0.185328 entering shut_get_descriptor(n 01, 18) >> 0.273455 shut_wait_ack(): ACK...

...ny buffer overflow type messages from my kernel so I think the PC is OK. Here is what it looks like starting up.. harrow:~>sudo /usr/local/libexec/nut/mge-shut -D -D -a mge Network UPS Tools - MGE UPS SYSTEMS/SHUT driver 0.65 (2.0.3) debug level is '2' entering upsdrv_initups() entering shut_ups_start() Communication with UPS established entering shut_get_descriptor(n 21, 9) shut_wait_ack(): ACK received entering shut_get_descriptor(n 01, 18) shut_wait_ack(): ACK received Device Descriptor: bLength: 0x12 bDescriptorType: 0x01 bcdUSB:...

...; ~# /usr/local/libexec/nut/oldmge-shut -DD -a ups-filesrv01 >> Network UPS Tools - Eaton / SHUT driver 0.70 (2.7.2) >> 0.000000 debug level is '2' >> 0.000882 entering upsdrv_initups() >> 0.001019 entering shut_ups_start() >> >> 0.028445 Communication with UPS established >> 0.028457 entering shut_get_descriptor(n 21, 9) >> 0.111394 shut_wait_ack(): ACK received >> 0.185328 entering shut_get_descriptor(n 01, 18) >>...

Hello Arno, Thanks for the quick reply. FreeNAS is FreeBSD-based. Yes, I could test a patch. As I have mentioned, this behavior is not seen at every single reboot but after most reboots. Also, some times, the connectivity can be lost without even rebooting. That is not very often can have happened a few times. Best regards, Panagiotis On 2/4/2015 5:44 ??, Arnaud Quette wrote: > Hello

Hello, I forgot nut since more than a year because a lot of job with other application My server nut failed since severals months We had 3 electric failure so I must install a new server nut I work with ubuntu 10.04.4 (64bits) / I installed nut 2.4.3 with deposits I have a MGE Pulsar evolution 2200 connected on usb last week when I began my tests all was ok (communication etc etc ..)

...ny buffer overflow type messages from my kernel so I think the PC is OK. Here is what it looks like starting up.. harrow:~>sudo /usr/local/libexec/nut/mge-shut -D -D -a mge Network UPS Tools - MGE UPS SYSTEMS/SHUT driver 0.65 (2.0.3) debug level is '2' entering upsdrv_initups() entering shut_ups_start() Communication with UPS established entering shut_get_descriptor(n 21, 9) shut_wait_ack(): ACK received entering shut_get_descriptor(n 01, 18) shut_wait_ack(): ACK received Device Descriptor: bLength: 0x12 bDescriptorType: 0x01 bcdUSB:...