<br><br><div><span class="gmail_quote">On 11/10/06, <b class="gmail_sendername">Arjen de Korte</b> <<a href="mailto:nut+users@de-korte.org">nut+users@de-korte.org</a>> wrote:</span><div> <br>[...] <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If you're willing to try a few more things, comment out the part in the<br>NUT startup script where 'upsmon' is started/stopped and fire it up. With<br>'upsc myups@localhost' you should be able to see the status of the UPS,
<br>without the risk of shutting down your system when things are not<br>configured properly. Try at least /dev/ttyS[0-3] with the UPS in different<br>serial ports on your server. Remember to stop the script before modifying
<br>and starting it again. Good luck!<br><br>Kind regards,<br>Arjen<br><br></blockquote></div><br>Ok, I 've done some more testing. <br>I did comment out the upsmon entry in /etc/default/nut<br>Then loaded the driver like:
<br>/lib/nut/genericups -x upstype=7 /dev/ttyS0<br>It loaded and according syslog:<br>Nov 11 10:19:47 radius1 genericups[8469]: Startup successful<br>However when I tried: <br>radius1:/etc/nut# upsc ups_name@localhost<br>
Error: Connection failure: Connection refused<br>radius1:/etc/nut# <br><br>I've done this for ttyS0 & ttyS1 (there are no more, 2 results in an error at fire up)<br>I also changed the permissions on ttyS1 like <br>
radius1:/etc/nut# ls -al /dev/ttyS0<br>crw-rw---- 1 root nut 4, 64 2005-02-26 07:39 /dev/ttyS0<br>radius1:/etc/nut# <br><br>Same problem.<br>The only things left here are.<br>1. There is a problem with the serial cable. (I tried 2 of them)
<br>How will I know if the cable that came with the UPS is the right one?<br>2. That thing just won't ever work for linux.<br><br>The new series of MGE are Ellipse ASR I hope someone can confirm these things work as they should
<br>with NUT running on debian stable.<br><br>Many tnx<br>Yves<br><br>