[Nut-upsuser] Dynamix UPS-650VA
Peter McKenna
peter.mckenna at bitt.co.nz
Sun May 11 18:29:16 UTC 2008
Hi Carlos
It appears to succeed.
>From syslog
May 12 06:17:51 test1 upsd[12154]: Connection from 127.0.1.1
May 12 06:17:51 test1 upsd[12154]: Instant command: nut at 127.0.1.1 did
beeper.toggle on ups1
May 12 06:17:51 test1 upsd[12154]: Client nut at 127.0.1.1 logged out
May 12 06:17:51 test1 megatec[12152]: Toggling UPS beeper.
May 12 06:18:59 test1 megatec[12152]: Communications with UPS lost: No
status from UPS.
May 12 06:19:01 test1 megatec[12152]: Communications with UPS
re-established
May 12 06:19:15 test1 upsd[12154]: Connection from 127.0.1.1
May 12 06:19:15 test1 upsd[12154]: Client on 127.0.1.1 logged out
May 12 06:20:23 test1 megatec[12152]: Communications with UPS lost: No
status from UPS.
May 12 06:20:25 test1 megatec[12152]: Communications with UPS
re-established
May 12 06:25:05 bitt1 megatec[12152]: Communications with UPS lost: No
status from UPS.
May 12 06:25:07 bitt1 megatec[12152]: Communications with UPS
re-established
May 12 06:26:01 bitt1 upsd[12154]: Connection from 127.0.1.1
May 12 06:26:10 bitt1 upsd[12154]: Instant command: nut at 127.0.1.1 did
beeper.toggle on ups1
May 12 06:26:10 bitt1 upsd[12154]: Client nut at 127.0.1.1 logged out
May 12 06:26:10 bitt1 megatec[12152]: Toggling UPS beeper.
But upsc shows,
ups.beeper.status: disabled
after each toggle command
I've tried this via the cgi interface and upscmd.
Regards,
Peter
On Thu, 2008-05-08 at 09:46 +0100, Carlos Rodrigues wrote:
> On Thu, May 8, 2008 at 4:20 AM, Peter McKenna <peter.mckenna at bitt.co.nz> wrote:
> > That's correct. I used to be able to toggle it in Nut 2.0 and
> > the response from upsc would show off/on, but if you unplugged it it would
> > still beep. I assumed there where other less critical beep alerts being
> > turned off.
>
> Then it never actually worked, it only appeared to work. The driver
> was probably assuming the beeper was on at startup and just changing
> its internal state when you issued the toggle command without actually
> getting that state from the UPS.
>
> Can you check the logs (/var/log/messages or similar, depending on the
> distribution you're using) to see if there's any message there
> indicating the beeper.toggle command didn't succeed?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20080512/ac9c176e/attachment.htm
More information about the Nut-upsuser
mailing list