Re: [Nut-upsuser] Problems with upscmd ACCESS-DENIED
Thanks for clearing that out, I was going to do a battery test because I was afraid that my batteries might be dying but as it turns out one of the batteries had a loose plug, fixed that and the ups is running strong :) Only if the UPS finds that the battery needs to be replaced it will report the 'RB' status (replace battery). If it doesn't, all is well. The Q1 protocol that is used by your UPS doesn't support more verbose messages (and neither does it report runtime or charge capacity) so there is nothing more to report. When using the software supplied from the manufacturer I do see runtime and charge capacity messages. Best regards -Gardar On Fri, Mar 11, 2011 at 7:28 AM, Arjen de Korte nut+us...@de-korte.orgwrote: Citeren Garðar Arnarsson gar...@giraffi.net: Thanks a bunch, that worked like a charm :) Glad to hear that. But now I've got another question... After I run commands (tests) with upscmd, where do I see the results? You don't. Ran a battery test check and it did not give any output. Only if the UPS finds that the battery needs to be replaced it will report the 'RB' status (replace battery). If it doesn't, all is well. The Q1 protocol that is used by your UPS doesn't support more verbose messages (and neither does it report runtime or charge capacity) so there is nothing more to report. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser -- Garðar Arnarsson kerfisstjóri Giraffi sf. gar...@giraffi.net http://gardar.giraffi.net ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Problems with upscmd ACCESS-DENIED
Citeren Garðar Arnarsson gar...@giraffi.net: I have defined the user in the /etc/ups/upsd.users 74 [gardar] 75 password = hidden 76 allowfrom = local 77 actions = SET 78 instcmds = ALL 79 [local_mon] 80 password = hidden 81 allowfrom = localhost 82 upsmon master Device and driver info: device.mfr: Inform device.model: SINUS1KURM device.type: ups driver.name: blazer_ser driver.version: 2.6.0 driver.version.internal: 1.51 What am I doing wrong? Did you check your syslog lately? The 'allowfrom' keyword is no longer used (since a couple of versions actually) and has been replaced by tcp-wrappers, which most likely is compiled in the version you're using. If there is a blanket 'deny all' in /etc/hosts.allow, this requires you to setup access permissions through /etc/hosts.allow. See the UPGRADING document, 'man 8 upsd' and 'man 5 hosts_access'. Adding something like upsd : garder@localhost : ALLOW should work. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Problems with upscmd ACCESS-DENIED
Thanks a bunch, that worked like a charm :) But now I've got another question... After I run commands (tests) with upscmd, where do I see the results? Ran a battery test check and it did not give any output. Thanks in advance. On Thu, Mar 10, 2011 at 8:25 AM, Arjen de Korte nut+us...@de-korte.orgwrote: Citeren Garðar Arnarsson gar...@giraffi.net: I have defined the user in the /etc/ups/upsd.users 74 [gardar] 75 password = hidden 76 allowfrom = local 77 actions = SET 78 instcmds = ALL 79 [local_mon] 80 password = hidden 81 allowfrom = localhost 82 upsmon master Device and driver info: device.mfr: Inform device.model: SINUS1KURM device.type: ups driver.name: blazer_ser driver.version: 2.6.0 driver.version.internal: 1.51 What am I doing wrong? Did you check your syslog lately? The 'allowfrom' keyword is no longer used (since a couple of versions actually) and has been replaced by tcp-wrappers, which most likely is compiled in the version you're using. If there is a blanket 'deny all' in /etc/hosts.allow, this requires you to setup access permissions through /etc/hosts.allow. See the UPGRADING document, 'man 8 upsd' and 'man 5 hosts_access'. Adding something like upsd : garder@localhost : ALLOW should work. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser -- Garðar Arnarsson kerfisstjóri Giraffi sf. gar...@giraffi.net http://gardar.giraffi.net ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Problems with upscmd ACCESS-DENIED
Citeren Garðar Arnarsson gar...@giraffi.net: Thanks a bunch, that worked like a charm :) Glad to hear that. But now I've got another question... After I run commands (tests) with upscmd, where do I see the results? You don't. Ran a battery test check and it did not give any output. Only if the UPS finds that the battery needs to be replaced it will report the 'RB' status (replace battery). If it doesn't, all is well. The Q1 protocol that is used by your UPS doesn't support more verbose messages (and neither does it report runtime or charge capacity) so there is nothing more to report. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Problems with upscmd ACCESS-DENIED
I'm trying to execute some commands on my ups, but I keep getting ERR ACCESS-DENIED upscmd -l sinus Instant commands supported on UPS [sinus]: beeper.toggle - Toggle the UPS beeper load.off - Turn off the load immediately load.on - Turn on the load immediately shutdown.return - Turn off the load and return when power is back shutdown.stayoff - Turn off the load and remain off shutdown.stop - Stop a shutdown in progress test.battery.start - Start a battery test test.battery.start.deep - Start a deep battery test test.battery.start.quick - Start a quick battery test test.battery.stop - Stop the battery test An example: upscmd sinus test.battery.start.quick Username (root): gardar Password: Unexpected response from upsd: ERR ACCESS-DENIED I have defined the user in the /etc/ups/upsd.users 74 [gardar] 75 password = hidden 76 allowfrom = local 77 actions = SET 78 instcmds = ALL 79 [local_mon] 80 password = hidden 81 allowfrom = localhost 82 upsmon master Device and driver info: device.mfr: Inform device.model: SINUS1KURM device.type: ups driver.name: blazer_ser driver.version: 2.6.0 driver.version.internal: 1.51 What am I doing wrong? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser