[Nut-upsuser] load off on outlet 1 or 2 fails

2013-06-29 Thread deception
I assume turning the load off on outlets and failing miserable has nothing to do with nut. But can someone help me out with a HP R/T 3000? syslog: mail.pascallen.nl:~# tail -f /var/log/syslog | grep ups Jun 29 12:35:10 mail upsd[4006]: Set variable: pascal@192.168.0.23 set

Re: [Nut-upsuser] Server 2012 - 64bit UPSD Crash

2013-06-29 Thread Charles Lepple
On Jun 28, 2013, at 7:40 AM, Ge-org Brohammer wrote: 0.046800 Connected to UPS [sspro]: blazer_usb-sspro 0.046800 Can't open c:\Program Files (x86)\NUT\sbin\..\etc/upsd.users: No such file or directory [...] ←--- Connecting with upsc at this moment 46.238943 Out of

[Nut-upsuser] upsrw doesn't set variable

2013-06-29 Thread Mike.
NUT 2.6.5 on FreeBSD 9.1 Why isn't the variable outlet.1.delay.shutdown set with the following command? # upsc PW5125@localhost | grep outlet.1.delay.shutdown outlet.1.delay.shutdown: -1 # upsrw -u au -p ap -s outlet.1.delay.shutdown PW5125@localhost Enter new value for

Re: [Nut-upsuser] upsrw doesn't set variable

2013-06-29 Thread Mike.
On 6/29/2013 at 9:14 AM Mike. wrote: |NUT 2.6.5 on FreeBSD 9.1 | | |Why isn't the variable outlet.1.delay.shutdown set with the following |command? | | | |# upsc PW5125@localhost | grep outlet.1.delay.shutdown |outlet.1.delay.shutdown: -1 | |# upsrw -u au -p ap -s outlet.1.delay.shutdown

Re: [Nut-upsuser] upsrw doesn't set variable

2013-06-29 Thread Charles Lepple
On Jun 29, 2013, at 9:45 AM, Mike. wrote: On 6/29/2013 at 9:14 AM Mike. wrote: |NUT 2.6.5 on FreeBSD 9.1 | | |Why isn't the variable outlet.1.delay.shutdown set with the following |command? | | | |# upsc PW5125@localhost | grep outlet.1.delay.shutdown |outlet.1.delay.shutdown: -1 |

Re: [Nut-upsuser] upsrw doesn't set variable

2013-06-29 Thread Mike.
On 6/29/2013 at 9:59 AM Charles Lepple wrote: |On Jun 29, 2013, at 9:45 AM, Mike. wrote: | | On 6/29/2013 at 9:14 AM Mike. wrote: | | |NUT 2.6.5 on FreeBSD 9.1 | | | | | |Why isn't the variable outlet.1.delay.shutdown set with the following | |command? | | | | | | | |# upsc PW5125@localhost |

Re: [Nut-upsuser] upsrw doesn't set variable

2013-06-29 Thread Kjell Claesson
lördagen den 29 juni 2013 11.28.14 skrev Mike.: 8--snip- Hi Mike, Thanks for the quick reply. I checked the log file (which, admittedly, I should have done before I posted about the problem :) ). Here's the command and the corresponding log message:

Re: [Nut-upsuser] upsrw doesn't set variable

2013-06-29 Thread Mike.
On 6/29/2013 at 6:16 PM Kjell Claesson wrote: |lördagen den 29 juni 2013 11.28.14 skrev Mike.: |8--snip- |Hi Mike, | | Thanks for the quick reply. | | I checked the log file (which, admittedly, I should have done before I | posted about the problem :) ). | |

Re: [Nut-upsuser] upsrw doesn't set variable

2013-06-29 Thread Kjell Claesson
lördagen den 29 juni 2013 15.22.44 skrev Mike.: 8-snip- Sorry for the delay. Here is the console output of bcmxcp with -DDD specified: [snip] 13.721204 Auto delay on: 2 13.721243 send_command: (4 bytes) = ab 01 35 1f 13.821127

Re: [Nut-upsuser] upsrw doesn't set variable

2013-06-29 Thread Mike.
On 6/29/2013 at 10:49 PM Kjell Claesson wrote: |lördagen den 29 juni 2013 15.22.44 skrev Mike.: |8-snip- |Sorry for the delay. | | Here is the console output of bcmxcp with -DDD specified: | | | [snip] | 13.721204 Auto delay on: 2 | | 13.721243