[Nut-upsuser] EATON 5PX with nut 2.6 on ubuntu 12.04
Hello, I have a EATON 5PX with a Network Management Card on ubuntu 12.04 I established a shutdown procedure like described in rogerprice.org It works I have an event mail on "onbatt" then another on "onbattdelay1" then the "upsmon -c fsd" order on "onbattedelay2" When "onbattdelay2" is finished, my server execute "auto logout and shutdown proceeding" then my ups shutdown too but when ? My second question is I don't find the "battery.charge.low" parameter on this ups my third question When electric power come back, ups restart, my server restart but the driver isn't connceted I have this message :"Can't connect to UPS (snmp-ups-MYUPS) : no such file or directory If I restart nut service, it's ok What can I do to avoid this problem ? and finally, last question When electric power come back, ups is started, my server is started how can I execute for example a "wake on lan" or a "reboot" for some computer which isn't connect on the ups Sorry my english isn't perfect Best regards Sabine ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Smart1500LCD USB and usbhid-ups
2012/12/11 Steve Salier > > Greetings all, > Hi Steve, > Anyone have a clue on this behavior (see below) on this behavior with > FreeNAS-8.3.0-RELEASE-x64 (r12701M) on a TrippLite 1500LCD UPS? NUT version > is 2.6.5 > > Using the following profile: Tripp-Lite ups 2 Smart1500LCD USB (usbhid-ups) > > I get the following: > > Dec 10 21:40:12 nas6 kernel: uhid0: rev 1.10/0.02, addr 2> on usbus1 > Dec 10 21:40:12 nas6 notifier: Will not 'restart' nut because nut_enable > is NO. > Dec 10 21:40:12 nas6 notifier: Will not 'restart' nut_upsmon because > nut_upsmon_enable is NO. > Dec 10 21:40:12 nas6 notifier: Will not 'restart' nut_upslog because > nut_upslog_enable is NO. > Dec 10 21:40:20 nas6 notifier: nut not running? (check > /var/db/nut/upsd.pid). > Dec 10 21:40:20 nas6 notifier: nut_upsmon not running? (check > /var/db/nut/upsmon.pid). > Dec 10 21:40:20 nas6 notifier: nut_upslog not running? (check > /var/db/nut/upslog.pid). > Dec 10 21:40:21 nas6 notifier: nut not running? (check > /var/db/nut/upsd.pid). > Dec 10 21:40:21 nas6 notifier: This TrippLite? device (09ae:3016) is not > (or perhaps not yet) supported > Dec 10 21:40:21 nas6 notifier: by usbhid-ups. Please make sure you have an > up-to-date version of NUT. If > Dec 10 21:40:21 nas6 notifier: this does not fix the problem, try running > the driver with the > Dec 10 21:40:21 nas6 notifier: '-x productid=3016' option. Please report > your results to the NUT user's > Dec 10 21:40:21 nas6 notifier: mailing list . > Dec 10 21:40:21 nas6 notifier: > Dec 10 21:40:21 nas6 notifier: Network UPS Tools - Generic HID driver 0.37 > (2.6.5) > Dec 10 21:40:21 nas6 notifier: USB communication driver 0.31 > Dec 10 21:40:21 nas6 notifier: No matching HID UPS found > Dec 10 21:40:21 nas6 notifier: Driver failed to start (exit status=1) > Dec 10 21:40:21 nas6 notifier: Network UPS Tools - UPS driver controller > 2.6.5 > Dec 10 21:40:21 nas6 root: /usr/local/etc/rc.d/nut: WARNING: failed precmd > routine for nut > Dec 10 21:40:21 nas6 notifier: /usr/local/etc/rc.d/nut: WARNING: failed > precmd routine for nut > Dec 10 21:40:21 nas6 notifier: nut_upsmon not running? (check > /var/db/nut/upsmon.pid). > Dec 10 21:40:21 nas6 notifier: Starting nut_upsmon. > Dec 10 21:40:21 nas6 notifier: kill: No such process > Dec 10 21:40:21 nas6 notifier: UPS: UPS1 (master) (power value 1) > Dec 10 21:40:21 nas6 upsmon[39737]: UPS [UPS1]: connect failed: Connection > failure: Connection refused > Dec 10 21:40:21 nas6 upsmon[39737]: Communications with UPS UPS1 lost > Dec 10 21:40:21 nas6 notifier: nut_upslog not running? (check > /var/db/nut/upslog.pid). > Dec 10 21:40:21 nas6 notifier: Starting nut_upslog. > Dec 10 21:40:21 nas6 notifier: Warning: initial connect failed: Connection > failure: Connection refused > Dec 10 21:40:21 nas6 notifier: Stopping nut_upslog. > Dec 10 21:40:21 nas6 notifier: Stopping nut_upsmon. > Dec 10 21:40:21 nas6 upsmon[39736]: upsmon parent: read > Dec 10 21:40:21 nas6 notifier: nut not running? (check > /var/db/nut/upsd.pid). > > According to latest HCL for NUT, the TrippLite? SmartUPS 1500 is supported: > http://www.networkupstools.org/stable-hcl.html > > > Not sure where the reference the "09ae:3016" model type is coming from. > these are the USB Vendor and Product IDs, that permits usbhid-ups to find supported devices. in the present case, this specific product ID 3016 is not currently part of our list. we can add it, but the first thing to do is to try if it works ;) as mentioned in the above log, just add "-x productid=3016" or add "productid=3016" in ups.conf, after the "port = auto" line. please report back if everything works, so that we can add this to usbhid-ups. cheers, Arnaud -- NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.fr ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] Smart1500LCD USB and usbhid-ups
Greetings all, Anyone have a clue on this behavior (see below) on this behavior with FreeNAS-8.3.0-RELEASE-x64 (r12701M) on a TrippLite 1500LCD UPS? NUT version is 2.6.5 Using the following profile: Tripp-Lite ups 2 Smart1500LCD USB (usbhid-ups) I get the following: Dec 10 21:40:12 nas6 kernel: uhid0: on usbus1 Dec 10 21:40:12 nas6 notifier: Will not 'restart' nut because nut_enable is NO. Dec 10 21:40:12 nas6 notifier: Will not 'restart' nut_upsmon because nut_upsmon_enable is NO. Dec 10 21:40:12 nas6 notifier: Will not 'restart' nut_upslog because nut_upslog_enable is NO. Dec 10 21:40:20 nas6 notifier: nut not running? (check /var/db/nut/upsd.pid). Dec 10 21:40:20 nas6 notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid). Dec 10 21:40:20 nas6 notifier: nut_upslog not running? (check /var/db/nut/upslog.pid). Dec 10 21:40:21 nas6 notifier: nut not running? (check /var/db/nut/upsd.pid). Dec 10 21:40:21 nas6 notifier: This TrippLite? device (09ae:3016) is not (or perhaps not yet) supported Dec 10 21:40:21 nas6 notifier: by usbhid-ups. Please make sure you have an up-to-date version of NUT. If Dec 10 21:40:21 nas6 notifier: this does not fix the problem, try running the driver with the Dec 10 21:40:21 nas6 notifier: '-x productid=3016' option. Please report your results to the NUT user's Dec 10 21:40:21 nas6 notifier: mailing list . Dec 10 21:40:21 nas6 notifier: Dec 10 21:40:21 nas6 notifier: Network UPS Tools - Generic HID driver 0.37 (2.6.5) Dec 10 21:40:21 nas6 notifier: USB communication driver 0.31 Dec 10 21:40:21 nas6 notifier: No matching HID UPS found Dec 10 21:40:21 nas6 notifier: Driver failed to start (exit status=1) Dec 10 21:40:21 nas6 notifier: Network UPS Tools - UPS driver controller 2.6.5 Dec 10 21:40:21 nas6 root: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut Dec 10 21:40:21 nas6 notifier: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut Dec 10 21:40:21 nas6 notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid). Dec 10 21:40:21 nas6 notifier: Starting nut_upsmon. Dec 10 21:40:21 nas6 notifier: kill: No such process Dec 10 21:40:21 nas6 notifier: UPS: UPS1 (master) (power value 1) Dec 10 21:40:21 nas6 upsmon[39737]: UPS [UPS1]: connect failed: Connection failure: Connection refused Dec 10 21:40:21 nas6 upsmon[39737]: Communications with UPS UPS1 lost Dec 10 21:40:21 nas6 notifier: nut_upslog not running? (check /var/db/nut/upslog.pid). Dec 10 21:40:21 nas6 notifier: Starting nut_upslog. Dec 10 21:40:21 nas6 notifier: Warning: initial connect failed: Connection failure: Connection refused Dec 10 21:40:21 nas6 notifier: Stopping nut_upslog. Dec 10 21:40:21 nas6 notifier: Stopping nut_upsmon. Dec 10 21:40:21 nas6 upsmon[39736]: upsmon parent: read Dec 10 21:40:21 nas6 notifier: nut not running? (check /var/db/nut/upsd.pid). According to latest HCL for NUT, the TrippLite? SmartUPS 1500 is supported: http://www.networkupstools.org/stable-hcl.html Not sure where the reference the "09ae:3016" model type is coming from. Many thanks in advance for pointers :-) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
