Comments on: Monitoring a UPS with nut on Debian or Ubuntu Linux http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/ tech, politics, etc. Thu, 25 Feb 2010 18:47:30 -0600 http://wordpress.org/?v=2.9.2 hourly 1 By: SirPete http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/#comment-4537 SirPete Thu, 25 Feb 2010 18:47:30 +0000 http://blog.shadypixel.com/?p=6#comment-4537 no i use netserver option. no i use netserver option.

]]> By: btmorex http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/#comment-4527 btmorex Wed, 24 Feb 2010 19:56:09 +0000 http://blog.shadypixel.com/?p=6#comment-4527 Do you have "MODE=standalone" in /etc/nut/nut.conf? Do you have “MODE=standalone” in /etc/nut/nut.conf?

]]> By: SirPete http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/#comment-4524 SirPete Wed, 24 Feb 2010 19:43:55 +0000 http://blog.shadypixel.com/?p=6#comment-4524 Hallo, i think there are no errors. but wenn i uses "sudo /etc/init.d/nut status" there ist noch pid for upsd upsc is running. i have to start upsd manually by "sudo upsd" than it runs fine. but the start on boot is not possible, only by starting with sudo. peter Hallo,
i think there are no errors. but wenn i uses
“sudo /etc/init.d/nut status” there ist noch pid for upsd
upsc is running.
i have to start upsd manually by
“sudo upsd”
than it runs fine.
but the start on boot is not possible, only by starting with sudo.

peter

]]> By: btmorex http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/#comment-4523 btmorex Wed, 24 Feb 2010 17:40:56 +0000 http://blog.shadypixel.com/?p=6#comment-4523 Glad you got it working. Unfortunately, nut 2.2 -> 2.4 was a big change to how configuration worked and I just haven't had a the time to update the guide. Glad you got it working. Unfortunately, nut 2.2 -> 2.4 was a big change to how configuration worked and I just haven’t had a the time to update the guide.

]]> By: Marc http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/#comment-4518 Marc Wed, 24 Feb 2010 05:36:09 +0000 http://blog.shadypixel.com/?p=6#comment-4518 yes the /etc/nut/nut.conf mode=standalone was my missing link. after adding that in I did a fresh boot and loaded up the upsc command it is showed the ups unit information, then pulled the plug and the unit displayed it was unplugged in the upsc screen then shut down the system. Thank you for you help, been over this guide so many times but I had clearly overlooked some of the important comments. Thanks again, everything appears to be working correctly now. yes the /etc/nut/nut.conf mode=standalone was my missing link.

after adding that in I did a fresh boot and loaded up the upsc command it is showed the ups unit information, then pulled the plug and the unit displayed it was unplugged in the upsc screen then shut down the system. Thank you for you help, been over this guide so many times but I had clearly overlooked some of the important comments.

Thanks again, everything appears to be working correctly now.

]]> By: Marc http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/#comment-4517 Marc Wed, 24 Feb 2010 05:18:59 +0000 http://blog.shadypixel.com/?p=6#comment-4517 BTW running ubuntu 9.10 Ok I changed the info to LISTEN as noted above, then also tried just clearing out the file completely and leaving blank. This is with # /etc/nut/upsd.conf Blank after fresh boot. On fresh boot. $ sudo upsc apc Error: Connection failure: Connection refused $ sudo upsd Network UPS Tools upsd 2.4.1 listening on 127.0.0.1 port 3493 listening on ::1 port 3493 Can't connect to UPS [apc] (usbhid-ups-apc): No such file or directory $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31 Using subdriver: APC HID 0.93 $ sudo upsd Network UPS Tools upsd 2.4.1 not listening on 127.0.0.1 port 3493 $ upsc apc ***Yield UPS info**** Does not shut down computer when unplugged. ------------------------------------------------------------------------ This is with # /etc/nut/upsd.conf as follows after fresh boot. # /etc/nut/upsd.conf LISTEN 127.0.0.1 Leaving it blank seems to yeild same results $ sudo upsc apc Error: Connection failure: Connection refused $ sudo upsd Network UPS Tools upsd 2.4.1 listening on 127.0.0.1 port 3493 Can't connect to UPS [apc] (usbhid-ups-apc): No such file or directory $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31 Using subdriver: APC HID 0.93 $ sudo upsd Network UPS Tools upsd 2.4.1 not listening on 127.0.0.1 port 3493 $ upsc apc ***Yields UPS Info**** Does not shut down computer when unplugged and drained.... ---- So clearly not starting on boot, and I've missed something to configure how it shuts down the system? # /etc/default/nut START_UPSD=yes START_UPSMON=yes still correct? BTW running ubuntu 9.10

Ok I changed the info to LISTEN as noted above, then also tried just clearing out the file completely and leaving blank.

This is with # /etc/nut/upsd.conf Blank after fresh boot.

On fresh boot.
$ sudo upsc apc
Error: Connection failure: Connection refused

$ sudo upsd
Network UPS Tools upsd 2.4.1
listening on 127.0.0.1 port 3493
listening on ::1 port 3493
Can’t connect to UPS [apc] (usbhid-ups-apc): No such file or directory

$ sudo upsdrvctl start
Network UPS Tools – UPS driver controller 2.4.1
Network UPS Tools – Generic HID driver 0.34 (2.4.1)
USB communication driver 0.31
Using subdriver: APC HID 0.93

$ sudo upsd
Network UPS Tools upsd 2.4.1
not listening on 127.0.0.1 port 3493

$ upsc apc
***Yield UPS info****

Does not shut down computer when unplugged.

————————————————————————

This is with # /etc/nut/upsd.conf as follows after fresh boot.
# /etc/nut/upsd.conf
LISTEN 127.0.0.1

Leaving it blank seems to yeild same results

$ sudo upsc apc
Error: Connection failure: Connection refused

$ sudo upsd
Network UPS Tools upsd 2.4.1
listening on 127.0.0.1 port 3493
Can’t connect to UPS [apc] (usbhid-ups-apc): No such file or directory

$ sudo upsdrvctl start
Network UPS Tools – UPS driver controller 2.4.1
Network UPS Tools – Generic HID driver 0.34 (2.4.1)
USB communication driver 0.31
Using subdriver: APC HID 0.93

$ sudo upsd
Network UPS Tools upsd 2.4.1
not listening on 127.0.0.1 port 3493

$ upsc apc

***Yields UPS Info****

Does not shut down computer when unplugged and drained….

—-

So clearly not starting on boot, and I’ve missed something to configure how it shuts down the system?

# /etc/default/nut
START_UPSD=yes
START_UPSMON=yes

still correct?

]]> By: btmorex http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/#comment-4516 btmorex Wed, 24 Feb 2010 04:44:27 +0000 http://blog.shadypixel.com/?p=6#comment-4516 Strange that you're not getting any other error message. My guess is that making the changes in: http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/#comment-1549 will fix your problem. Strange that you’re not getting any other error message. My guess is that making the changes in:

http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/#comment-1549

will fix your problem.

]]> By: Marc http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/#comment-4514 Marc Wed, 24 Feb 2010 03:49:59 +0000 http://blog.shadypixel.com/?p=6#comment-4514 # /etc/nut/upsd.conf ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCEPT localhost REJECT ALL # /etc/nut/upsd.conf
ACL all 0.0.0.0/0
ACL localhost 127.0.0.1/32
ACCEPT localhost
REJECT ALL

]]> By: btmorex http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/#comment-4512 btmorex Tue, 23 Feb 2010 22:28:12 +0000 http://blog.shadypixel.com/?p=6#comment-4512 What error are you getting from running <code>sudo /etc/init.d/nut start</code>? Also, see the comments above about nut >= 2.4. Specifically, http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/#comment-785 and http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/#comment-1549 mention solutions to particular problems. What error are you getting from running sudo /etc/init.d/nut start?

Also, see the comments above about nut >= 2.4. Specifically,

http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/#comment-785

and

http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/#comment-1549

mention solutions to particular problems.

]]> By: SirPete http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/#comment-4510 SirPete Tue, 23 Feb 2010 19:34:53 +0000 http://blog.shadypixel.com/?p=6#comment-4510 Hallo, im using Ubuntu 9.10 server 64 bit. And have problems to start nut. all the setting are done, how they are listed above, with an other dist i think it was 8.04 it runs perfectly, but i don't know wath nut version ist was. today under 9.10 i use 2.4.1. the problem is that upsd doesn't start at booting, i think becourse of missing promissions. lateron starting by "sudo upsd" it work fine. but this is no acceptable solution. Does anybody have an idea? Hallo,
im using Ubuntu 9.10 server 64 bit. And have problems to start nut. all the setting are done, how they are listed above, with an other dist i think it was 8.04 it runs perfectly, but i don’t know wath nut version ist was. today under 9.10 i use 2.4.1.

the problem is that upsd doesn’t start at booting, i think becourse of missing promissions. lateron starting by “sudo upsd” it work fine. but this is no acceptable solution.

Does anybody have an idea?

]]>