Re: [Nut-upsuser] Eaton 5PX and Nuts - Ethernet connectivity?
On 27/07/15 04:40, Victor Hooi wrote: Hi, We're looking at getting a UPS to provide backup power for a Dell R610 and a 48-port Gigabit switch. The model we're thinking of getting is the Eaton 5PX 1500 VA: [snip] However, I'd prefer to use Ethernet support, using the Eaton Network Card-MS: http://powerquality.eaton.com/Products-services/Power-Management/Connectivity/Network-MS.asp Does anybody happen to know if Ethernet with Eaton devices is supported in NUTS, or how you'd get it working? Hi Victor, First of all it's NUT not NUTS :-) I'm using a NETWORK-MS network card in an Eaton 9130i. I'm not surprised the 5PX doesn't show up in the HCL under Ethernet as the behaviour of the network card governs the compatibility, rather than what the UPS itself provides. The NETWORK-MS card works fine with the NUT snmp-ups driver. Shutdown behaviour is good as long as you remember to make sure your switch is also on the UPS, but it sounds like you've got that covered (yes, oops, been there done that). I have mine configured like this in ups.conf: [pw9130] driver = snmp-ups port = [SNIP] community = public snmp_version = v1 pollfreq = 15 When I query NUT for UPS info it returns the following: ambient.humidity: 0.00 ambient.temperature: 0.0 battery.charge: 100.00 battery.charge.low: 20 battery.runtime: 6746.00 battery.runtime.low: 180.00 battery.voltage: 104.00 device.mfr: Eaton device.model: PW9130 3000VA-T device.serial: [SNIP] device.type: ups driver.name: snmp-ups driver.parameter.pollfreq: 15 driver.parameter.pollinterval: 2 driver.parameter.port: [SNIP] driver.parameter.snmp_version: v1 driver.version: 2.7.2 driver.version.data: mge MIB 0.5 driver.version.internal: 0.72 input.phases: 1.00 input.transfer.reason: outlet.desc: Main Outlet outlet.id: 0 output.current: 3.00 output.frequency: 50.00 output.phases: 1.00 output.voltage: 230.00 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.firmware: 1.29 ups.firmware.aux: JB ups.load: 30.00 ups.mfr: Eaton ups.model: PW9130 3000VA-T ups.serial: [SNIP] ups.start.auto: no ups.status: OL ups.test.result: done and passed ups.timer.reboot: -1.00 ups.timer.shutdown: -1.00 ups.timer.start: -1.00 I get a lot more info straight over SNMP, which I'm monitoring with Nagios and logging/graphing with Cacti. HTH, Chris -- Chris Boot bo...@bootc.net ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT v2.6.4 with HP AF401A won't start
Hi Arnaud, and apologies for the delay in getting back to you.
For a totally separate reason I’d intended to install NUT on a new VMware image
so, in view of your comments and to avoid confusion at a later date with a
hybrid installation, I decided to install on the new image from the tarball and
set up the start/stop script manually.
I unpacked the tarball, applied the patch you sent me and then ran the
configure/make/make install sequence. The driver started OK as it did on the
old image so I copied the /etc/init.d/ups script installed by the rpm package
from the old image to the new one and edited the paths. I then ran chkconfig
to set it up as a service. I haven’t fully tested that yet as I haven’t
completed the config but I see no reason why it won’t work.
Many thanks for your help with this.
Regards,
Chris.
Chris Pratt
Development Infrastructure Manager
T: +44 118 929 4176 | M: +44 7979 854 307 | F: +44 118 929 4001
From: Arnaud Quette [mailto:aquette@gmail.com]
Sent: 01 November 2012 11:50
To: Pratt Chris
Cc: nut-upsuser@lists.alioth.debian.org
Subject: Re: [Nut-upsuser] NUT v2.6.4 with HP AF401A won't start
2012/10/31 Pratt Chris chris.pr...@comptel.commailto:chris.pr...@comptel.com
Hi Arnaud.
Hi Chris,
I think you’ve cracked it. The following terminal output shows the package and
also shows that when I start it from /usr/local/ups/bin it doesn’t crash.
nice, I've committed the patch to the trunk (NUT development version), r3769:
http://trac.networkupstools.org/projects/nut/changeset/3769
[root@ups-monitor bin]# rpm -q nut
nut-2.6.4-1.el6.x86_64
[root@ups-monitor bin]# which upsdrvctl
/sbin/upsdrvctl
[root@ups-monitor bin]# pwd
/usr/local/ups/bin
[root@ups-monitor bin]# ./upsdrvctl start
Network UPS Tools - UPS driver controller 2.6.5
Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5)
Detected HP R12000/3UPS on host 192.168.0.89 (mib: cpqpower 1.5)
[UPS-HP01] snmp_ups_walk: data stale for ups.L1.realpower
[UPS-HP01] snmp_ups_walk: data stale for ups.L2.realpower
[UPS-HP01] snmp_ups_walk: data stale for ups.L3.realpower
[root@ups-monitor bin]#
I’ve uninstalled the package and re-run make install just to be sure and it
starts up fine with upsdrvctl start, with the following message in
/var/log/messages.
Oct 30 09:20:25 ups-monitor snmp-ups[32252]: Startup successful
Now it’s on to finishing the configuration and setting up the clients.
beware of 1 thing: the main difference with a source install, as you did
lastly, and a native package (RPM) is the system/shutdown integration.
the init.d / systemd script will look for binaries (upsd, drivers, ...), in the
known path, not /usr/local/ups/{bin,sbin}...
so you may want to keep your original rpm and overwrite snmp-ups with the new
one.
thus, uninstall first the current install and reconfigure using the following:
./configure --program-prefix= --prefix=/usr --exec-prefix=/usr
--bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share
--includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec
--localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man
--infodir=/usr/share/info --with-all --with-nss --with-libltdl --without-hal
--with-cgi --datadir=/usr/share/nut --with-user=nut --with-group=dialout
--with-statepath=/var/run/nut --with-pidpath=/var/run/nut
--with-altpidpath=/var/run/nut --sysconfdir=/etc/ups
--with-cgipath=/var/www/nut-cgi-bin --with-drvpath=/sbin
--with-systemdsystemunitdir=/usr/lib/systemd/system --disable-static
--with-udev-dir=/lib/udev
the above is a trimmed version of the one provided by Michal Hlavinka.
but you may want or need to trim it a bit more...
cheers,
Arnaud
--
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr
Disclaimer: This message and any attachments thereto are intended solely for
the addressed recipient(s) and may contain confidential information.
If you are not the intended recipient, please notify the sender by reply e-mail
and delete the e-mail (including any attachments thereto) without producing,
distributing or retaining any copies thereof. Any review, dissemination or
other use of, or taking of any action in reliance upon, this information by
persons or entities other than the intended recipient(s) is prohibited.
Thank you.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT v2.6.4 with HP AF401A won't start
Hi Arnaud. I think you’ve cracked it. The following terminal output shows the package and also shows that when I start it from /usr/local/ups/bin it doesn’t crash. [root@ups-monitor bin]# rpm -q nut nut-2.6.4-1.el6.x86_64 [root@ups-monitor bin]# which upsdrvctl /sbin/upsdrvctl [root@ups-monitor bin]# pwd /usr/local/ups/bin [root@ups-monitor bin]# ./upsdrvctl start Network UPS Tools - UPS driver controller 2.6.5 Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) Detected HP R12000/3UPS on host 192.168.0.89 (mib: cpqpower 1.5) [UPS-HP01] snmp_ups_walk: data stale for ups.L1.realpower [UPS-HP01] snmp_ups_walk: data stale for ups.L2.realpower [UPS-HP01] snmp_ups_walk: data stale for ups.L3.realpower [root@ups-monitor bin]# I’ve uninstalled the package and re-run make install just to be sure and it starts up fine with upsdrvctl start, with the following message in /var/log/messages. Oct 30 09:20:25 ups-monitor snmp-ups[32252]: Startup successful Now it’s on to finishing the configuration and setting up the clients. Many thanks for your help. Regards, Chris. Chris Pratt Development Infrastructure Manager T: +44 118 929 4176 | M: +44 7979 854 307 | F: +44 118 929 4001 Disclaimer: This message and any attachments thereto are intended solely for the addressed recipient(s) and may contain confidential information. If you are not the intended recipient, please notify the sender by reply e-mail and delete the e-mail (including any attachments thereto) without producing, distributing or retaining any copies thereof. Any review, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited. Thank you. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT v2.6.4 with HP AF401A won't start
Hi Arnaud. I think you’ve cracked it. The following terminal output shows the package and also shows that when I start it from /usr/local/ups/bin it doesn’t crash. [root@ups-monitor bin]# rpm -q nut nut-2.6.4-1.el6.x86_64 [root@ups-monitor bin]# which upsdrvctl /sbin/upsdrvctl [root@ups-monitor bin]# pwd /usr/local/ups/bin [root@ups-monitor bin]# ls apcsmart clone liebert-esp2 powerpanel upscode2 apcsmart-old clone-outlet masterguard rhinoupsdrvctl bcmxcpdummy-ups metasys safenet upslog belkinetapromge-shut skel upsrw belkinunv everups mge-utalk snmp-ups upssched-cmd bestfcom gamatronicmicrodowell solisvictronups bestfortress genericupsoldmge-shut tripplite bestuferrups isbmexoneac tripplitesu bestups ivtscdoptiups upsc blazer_serliebert powercom upscmd [root@ups-monitor bin]# ./upsdrvctl start Network UPS Tools - UPS driver controller 2.6.5 Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) Detected HP R12000/3UPS on host 192.168.0.89 (mib: cpqpower 1.5) [UPS-HP01] snmp_ups_walk: data stale for ups.L1.realpower [UPS-HP01] snmp_ups_walk: data stale for ups.L2.realpower [UPS-HP01] snmp_ups_walk: data stale for ups.L3.realpower [root@ups-monitor bin]# I’ve uninstalled the package and re-run make install just to be sure and it starts up fine with upsdrvctl start, with the following message in /var/log/messages. Oct 30 09:20:25 ups-monitor snmp-ups[32252]: Startup successful Now it’s on to finishing the configuration and setting up the clients. Many thanks for your help. Regards, Chris. Chris Pratt Development Infrastructure Manager T: +44 118 929 4176 | M: +44 7979 854 307 | F: +44 118 929 4001 From: Arnaud Quette [mailto:aquette@gmail.com] Sent: 29 October 2012 20:26 To: Pratt Chris Cc: nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] NUT v2.6.4 with HP AF401A won't start 2012/10/29 Pratt Chris chris.pr...@comptel.commailto:chris.pr...@comptel.com Hi Arnaud. Hi Chris, I’ve run the commands you suggested but it actually didn’t crash. I let it run for about 10 minutes and it was obviously repeating the same messages so I broke it with Ctrl-C. I’ve attached the terminal output (shortened to meet the file size limit) and at the end it shows the message from trying to start it with upsdrvctl and the message in /var/log/messages. just to be sure to understand since the end of the traces seems to be melted: - the driver doesn't crash when using /usr/local/ups/bin/snmp-ups -D ... - the driver crashes when using upsdrvctl start is upsdrvctl also located in /usr/local/bin or do you have another one installed (RPM)? could you please check using rpm -q nut? cheers, Arnaud -- Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.fr Disclaimer: This message and any attachments thereto are intended solely for the addressed recipient(s) and may contain confidential information. If you are not the intended recipient, please notify the sender by reply e-mail and delete the e-mail (including any attachments thereto) without producing, distributing or retaining any copies thereof. Any review, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited. Thank you. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT v2.6.4 with HP AF401A won't start
Hi Arnaud. I’ve run the commands you suggested but it actually didn’t crash. I let it run for about 10 minutes and it was obviously repeating the same messages so I broke it with Ctrl-C. I’ve attached the terminal output (shortened to meet the file size limit) and at the end it shows the message from trying to start it with upsdrvctl and the message in /var/log/messages. Regards, Chris. Chris Pratt Development Infrastructure Manager T: +44 118 929 4176 | M: +44 7979 854 307 | F: +44 118 929 4001 From: Arnaud Quette [mailto:aquette@gmail.com] Sent: 24 October 2012 22:23 To: Pratt Chris Cc: nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] NUT v2.6.4 with HP AF401A won't start 2012/10/22 Pratt Chris chris.pr...@comptel.commailto:chris.pr...@comptel.com Hi Arnaud. Hi Chris I’ve applied the patch but it still crashes. I started from scratch and did the following: strange! at least, it runs (a few seconds) longer... hem. this seems related to another issue here. I would need a gdb backtrace to shed some light. can you install gdb, if needed, and run as root: $ gdb /path/to/snmp-ups then enter snmp-ups params: (gdb) run -D -a UPS-HP01 once snmp-ups crashes, type bt in gdb, i.e: (gdb) bt and send me back the output. cheers, Arnaud -- Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.fr Disclaimer: This message and any attachments thereto are intended solely for the addressed recipient(s) and may contain confidential information. If you are not the intended recipient, please notify the sender by reply e-mail and delete the e-mail (including any attachments thereto) without producing, distributing or retaining any copies thereof. Any review, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited. Thank you. gbd_output.txt.gz Description: gbd_output.txt.gz ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT v2.6.4 with HP AF401A won't start
Hi Arnaud. I’ve applied the patch but it still crashes. I started from scratch and did the following: As user ‘nut’: Unpack the v2.6.5 tarball Apply the patch Run ./configure –with-user=nut –with-group=nut –with-snmp Run make As user ‘root’: Run make install mkdir –p /var/state/ups chmod 0770 /var/state/ups chown root:nut /var/state/ups As user ‘nut’; Run the debug command. The debug output is attached. Chris. Chris Pratt Development Infrastructure Manager T: +44 118 929 4176 | M: +44 7979 854 307 | F: +44 118 929 4001 From: Arnaud Quette [mailto:aquette@gmail.com] Sent: 18 October 2012 20:46 To: Pratt Chris Cc: NUT Users Subject: Re: [Nut-upsuser] NUT v2.6.4 with HP AF401A won't start 2012/10/17 Pratt Chris chris.pr...@comptel.commailto:chris.pr...@comptel.com Hi Arnaud. Hi Chris, first, please keep the traffic on the list, since other people may be interested in the topic. Unfortunately I'm not primarily a developer (I manage a room full of servers) so I don't have the normal array of development tools. I built NUT from the downloaded tarball following the instructions in the Installation Guide so If patching means simply amending files I can do that and then rebuild and test it, if you let me know what changes need to be made. it's exactly that, not harder. the patch is attached. please beware that if I've not committed it to the NUT code repository, it's because of a lack of testing! so even if my confidence level is good, not all my green lights are lit. to apply the patch, go into the NUT source directory and use: $ patch -p0 /path/to/snmp-ups-0outlet.diff note that it applies fine on 2.6.5. then just make make install as previously I'm interested in a driver debug trace, using: $ /path/to/snmp-ups -D -a UPS-HP01 If the driver doesn't crash, just Ctrl+C after a couple of minutes. in all cases, send back the trace in compressed form please. cheers, Arnaud -- Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.fr Disclaimer: This message and any attachments thereto are intended solely for the addressed recipient(s) and may contain confidential information. If you are not the intended recipient, please notify the sender by reply e-mail and delete the e-mail (including any attachments thereto) without producing, distributing or retaining any copies thereof. Any review, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited. Thank you. debug.txt.gz Description: debug.txt.gz ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] NUT v2.6.4 with HP AF401A won't start
Hi. I'm trying to configure NUT to manage a HP R12000/3 3-phase UPS fitted with an AF401A management module but it immediately crashes with a segmentation fault. O/S is CentOS 6.3 64-bit NUT built from tarball AF401A Firmware version 2.1.3 Extract from /etc/ups/ups.conf [UPS-HP01] driver = snmp-ups port = 192.168.0.89 desc = HP R12000/3 UPS Output from starting the driver [root@ups-monitor log]# upsdrvctl start Network UPS Tools - UPS driver controller 2.6.4 Network UPS Tools - Generic SNMP UPS driver 0.66 (2.6.4) kill: No such process Detected HP R12000/3UPS on host 192.168.0.89 (mib: cpqpower 1.5) Driver exited abnormally [root@ups-monitor log]# Extract from /var/log/messages Oct 15 15:02:32 ups-monitor kernel: snmp-ups[16840]: segfault at 0 ip 00354707a98c sp 7fff11f2a8b8 error 4 in libc-2.12.sohttp://libc-2.12.so[354700+189000] Debug output attached. I've downloaded the latest mib file (v1.64) from HP's website but I can't find any way to add it to the source files. I've seen references to the mib2nut mapping but, again, no help on how to achieve this. Thanks, Chris Pratt Development Infrastructure Manager Comptel Corporation 69 Suttons Business Park, Sutton Park Avenue, Reading, RG6 1AZ, UK T: +44 118 929 4176 | M: +44 7979 854 307 | F: +44 118 929 4001 chris.pr...@comptel.commailto:chris.pr...@comptel.com www.comptel.comhttp://www.comptel.com/ Disclaimer: This message and any attachments thereto are intended solely for the addressed recipient(s) and may contain confidential information. If you are not the intended recipient, please notify the sender by reply e-mail and delete the e-mail (including any attachments thereto) without producing, distributing or retaining any copies thereof. Any review, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited. Thank you. nut.txt.gz Description: nut.txt.gz ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Zigor Ebro 650 compatibility
On 11 August 2012 19:14, Arnaud Quette aquette@gmail.com wrote: 2012/8/11 Chris Rees utis...@gmail.com On 11 Aug 2012 13:03, Martyn Hill martyn.joseph.h...@gmail.com wrote: (...) My FreeBSD 8 appears to be running/linking against libusb20 - the 'new' one... We killed the old one a long time ago ;) not sure of what you exactly mean here! libusb 0.1 is still avail in FBSD 9: http://www.freebsd.org/cgi/ports.cgi?query=libusbstype=all Update: while reading the comment on libusb1.0 website [1], I now understand why you're using 2.0! FreeBSD 8 and above include a FreeBSD-specific reimplementation of the libusb-1.0 API, so your applications will probably work there too. The source code for this library can be found: http://svnweb.freebsd.org/base/head/lib/libusb/; but still, your killing comment leave me in a doubtful state ;) Oops, haha, sorry, that's right; we didn't kill it, just switched default, and loads of ports needed modification over it. Thinking this could be an issue, I have a Raspberry Pi here too, running Debian; I'll have a go to see if it makes any difference. Chris ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Zigor Ebro 650 compatibility
On 8 August 2012 10:07, Martyn Hill martyn.joseph.h...@gmail.com wrote: Arnaud Quette aquette.dev at gmail.com writes: 2012/6/3 Chris Rees crees at freebsd.org: Hi all, Hi Chris, After some research I've found that this device should run with the blazer_usb driver. Jun 3 16:15:38 pegasus kernel: ugen0.4: vendor 0x0001 at usbus0 Jun 3 16:15:38 pegasus kernel: uhid0: vendor 0x0001 product 0x, class 0/0, rev 1.00/1.00, addr 4 on usbus0 However, even after shoehorning it; [crees at pegasus]/usr/local/libexec/nut% sudo ./blazer_usb -a zigor -D -x vendorid=0x0001 -x productid=0x -x subdriver=krauler Password: Network UPS Tools - Megatec/Q1 protocol USB driver 0.04 (2.6.3-Unversioned directory) 0.00 send_to_all: SETINFO driver.parameter.vendorid 0x0001 0.13 send_to_all: SETINFO driver.parameter.productid 0x 0.18 send_to_all: SETINFO driver.parameter.subdriver krauler 0.20 debug level is '9' 0.000874 language ID workaround enabled (using '0x409') 0.001019 No appropriate HID device found 0.001025 No supported devices found. Please check your device availability with 'lsusb' and make sure you have an up-to-date version of NUT. If this does not help, try running the driver with at least 'subdriver', 'vendorid' and 'productid' options specified. Please refer to the man page for details about these options (man 8 blazer). This is on FreeBSD with NUT updated to 2.6.3 (I've modified the port). Hi Chris Any chance you could share the FreeBSD port? Using the version (2.6.1) currently available in the ports tree, I can get a step closer than your tests above, but without the enhanced blazer_usb driver (0.0.4) in nut 2.6.3, I don't think I can get any further. All you need to do is edit the PORTVERSION value in the Makefile, and run make makesum :) I've just successfully upgraded to 2.6.4 this way The UPS comes with UPSilon, but it's several years (!) old and I can't even get it to install, let alone work. Have I sent enough info? I'm willing to have a go at hacking the driver, but having trouble getting started. Chris [crees at pegasus]/usr/local/libexec/nut% grep -v ^# /usr/local/etc/nut/ups.conf [zigor] port = auto driver = blazer_usb langid_fix = 0x409 desc = Zigor UPS vendorid = 0001 productid = it's quite probably due to a permission issue. See 4) Permissions on http://people.freebsd.org/~thierry/nut_FreeBSD_HowTo.txt Thanks Arnaud, and sorry for the delay-- I've been on holiday. As I mentioned above I've now got it to 2.6.4, and have a new message; [crees@pegasus]/usr/local/libexec/nut% sudo ./blazer_usb -a zigor -D Network UPS Tools - Megatec/Q1 protocol USB driver 0.08 (2.6.4-Unversioned directory) 0.00 debug level is '13' 0.001081 Checking device (0001/) (/dev/usb//dev/ugen2.3) 0.001688 - VendorID: 0001 0.001694 - ProductID: 0.001697 - Manufacturer: unknown 0.001701 - Product: unknown 0.001705 - Serial Number: unknown 0.001708 - Bus: /dev/usb 0.001712 Trying to match device 0.001717 Device matches 0.001737 send_to_all: SETINFO ups.vendorid 0001 0.001744 send_to_all: SETINFO ups.productid 0.001751 send_to_all: SETINFO device.type ups 0.001758 send_to_all: SETINFO driver.version 2.6.4-Unversioned directory 0.001764 send_to_all: SETINFO driver.version.internal 0.08 0.001770 send_to_all: SETINFO driver.name blazer_usb 0.001775 Trying megatec protocol... 0.001786 send: Q1 0.002191 read: Unknown error 0.002242 Permissions problem: Input/output error [crees@pegasus]/usr/local/libexec/nut% I had already chmod'd 777 all the USB nodes (just for debugging of course!) and: [crees@pegasus]/usr/local/libexec/nut% grep -v ^# /usr/local/etc/nut/ups.conf [zigor] port = auto driver = blazer_usb Looks as though the UPS is answering in strange ways Chris ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Zigor Ebro 650 compatibility
On 10 August 2012 18:08, Chris Rees cr...@freebsd.org wrote: On 8 August 2012 10:07, Martyn Hill martyn.joseph.h...@gmail.com wrote: Arnaud Quette aquette.dev at gmail.com writes: 2012/6/3 Chris Rees crees at freebsd.org: Hi all, Hi Chris, After some research I've found that this device should run with the blazer_usb driver. Jun 3 16:15:38 pegasus kernel: ugen0.4: vendor 0x0001 at usbus0 Jun 3 16:15:38 pegasus kernel: uhid0: vendor 0x0001 product 0x, class 0/0, rev 1.00/1.00, addr 4 on usbus0 However, even after shoehorning it; [crees at pegasus]/usr/local/libexec/nut% sudo ./blazer_usb -a zigor -D -x vendorid=0x0001 -x productid=0x -x subdriver=krauler Password: Network UPS Tools - Megatec/Q1 protocol USB driver 0.04 (2.6.3-Unversioned directory) 0.00 send_to_all: SETINFO driver.parameter.vendorid 0x0001 0.13 send_to_all: SETINFO driver.parameter.productid 0x 0.18 send_to_all: SETINFO driver.parameter.subdriver krauler 0.20 debug level is '9' 0.000874 language ID workaround enabled (using '0x409') 0.001019 No appropriate HID device found 0.001025 No supported devices found. Please check your device availability with 'lsusb' and make sure you have an up-to-date version of NUT. If this does not help, try running the driver with at least 'subdriver', 'vendorid' and 'productid' options specified. Please refer to the man page for details about these options (man 8 blazer). This is on FreeBSD with NUT updated to 2.6.3 (I've modified the port). Hi Chris Any chance you could share the FreeBSD port? Using the version (2.6.1) currently available in the ports tree, I can get a step closer than your tests above, but without the enhanced blazer_usb driver (0.0.4) in nut 2.6.3, I don't think I can get any further. All you need to do is edit the PORTVERSION value in the Makefile, and run make makesum :) I've just successfully upgraded to 2.6.4 this way The UPS comes with UPSilon, but it's several years (!) old and I can't even get it to install, let alone work. Have I sent enough info? I'm willing to have a go at hacking the driver, but having trouble getting started. Chris [crees at pegasus]/usr/local/libexec/nut% grep -v ^# /usr/local/etc/nut/ups.conf [zigor] port = auto driver = blazer_usb langid_fix = 0x409 desc = Zigor UPS vendorid = 0001 productid = it's quite probably due to a permission issue. See 4) Permissions on http://people.freebsd.org/~thierry/nut_FreeBSD_HowTo.txt Thanks Arnaud, and sorry for the delay-- I've been on holiday. As I mentioned above I've now got it to 2.6.4, and have a new message; [crees@pegasus]/usr/local/libexec/nut% sudo ./blazer_usb -a zigor -D Network UPS Tools - Megatec/Q1 protocol USB driver 0.08 (2.6.4-Unversioned directory) 0.00 debug level is '13' 0.001081 Checking device (0001/) (/dev/usb//dev/ugen2.3) 0.001688 - VendorID: 0001 0.001694 - ProductID: 0.001697 - Manufacturer: unknown 0.001701 - Product: unknown 0.001705 - Serial Number: unknown 0.001708 - Bus: /dev/usb 0.001712 Trying to match device 0.001717 Device matches 0.001737 send_to_all: SETINFO ups.vendorid 0001 0.001744 send_to_all: SETINFO ups.productid 0.001751 send_to_all: SETINFO device.type ups 0.001758 send_to_all: SETINFO driver.version 2.6.4-Unversioned directory 0.001764 send_to_all: SETINFO driver.version.internal 0.08 0.001770 send_to_all: SETINFO driver.name blazer_usb 0.001775 Trying megatec protocol... 0.001786 send: Q1 0.002191 read: Unknown error 0.002242 Permissions problem: Input/output error [crees@pegasus]/usr/local/libexec/nut% I had already chmod'd 777 all the USB nodes (just for debugging of course!) and: [crees@pegasus]/usr/local/libexec/nut% grep -v ^# /usr/local/etc/nut/ups.conf [zigor] port = auto driver = blazer_usb Looks as though the UPS is answering in strange ways Just for fun, I noticed the #ifdef TESTING in blazer_usb.c. I defined that, and got this output when running ./blazer_usb -a zigor: http://www.bayofrum.net/~crees/scratch/zigor-testing.txt Any hints there? Chris ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut not working remotely
On 14/08/2011 18:30, Leslie Rhorer wrote: -Original Message- From: Charles Lepple [mailto:clep...@gmail.com] Sent: Sunday, August 14, 2011 10:29 AM To: lrho...@satx.rr.com Cc: nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut not working remotely On Aug 13, 2011, at 1:03 PM, Leslie Rhorer wrote: Hello everyone. I have NUT up and running on three servers, What version(s) of NUT? The system I can reach is running 2.2.2 under Debian Lenny, kernel 2.6.26-2-686. The systems I cannot reach are running 2.4.3 under Debian Squeeze, kernel 2.6.32-5-amd64. That doesn't actually tell us the versions of NUT you're using... But as I run Debian I think I know what the problem is. Edit /etc/nut/upsd.conf and add/change the LISTEN line to: LISTEN 0.0.0.0 3493 By default newer Debian version of NUT bind to localhost, so you won't be able to access it from other machines unless you make the change. Chris ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] How to shut down the running usbhid-ups driver and start with -DDD option?
On 18/11/2010 21:31, Niels Kristian Jensen wrote: Hi all, Well, I must be missing something so obvious, that it isn't even in the documentation: How to stop all instances of a driver. Please don't top post, it's considered rude. To stop the driver: upsdrvctl stop PingvinUPS Then you can start it again manually: /lib/nut/usbhid-ups -a PingvinUPS -DDD That's only useful if you want to debug the driver of course. Otherwise you'd start it like this: upsdrvctl start PingvinUPS HTH, Chris ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Alright, I'm geting some where! Found out that the mac terminal does some weird things with tabs and you cannot tab in it. I switched to linux and all is well. This is what I receive when I try to start the driver with tripplite_usb: Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.1) Warning: This is an experimental driver. Some features may not function correctly. Error: UPS [Tripp-Lite] is for driver usbhid-ups, but I'm tripplite_usb! This is what I receive when I try to start the usbhid-ups driver: Checking device (09AE/0001) (001/002) - VendorID: 09ae - ProductID: 0001 - Manufacturer: TRIPP LITE - Product: TRIPP LITE UPS - Serial Number: unknown - Bus: 001 Trying to match device This Tripp Lite device (09ae/0001) is not supported by usbhid-ups. Please use the tripplite_usb driver instead. This is what I receive when I am trying to start upsdrvctl with tripplite_usb Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.1) Warning: This is an experimental driver. Some features may not function correctly. No matching USB/HID UPS found Driver failed to start (exit status=1 And this is what I receive when I try to start upsdrvctl with usbhid-ups: 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 This Tripp Lite device (09ae/0001) is not supported by usbhid-ups. Please use the tripplite_usb driver instead. No matching HID UPS found Driver failed to start (exit status=1) Thanks for all the help guys. Now maybe I can help. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Arnaud Quette aquette@gmail.com writes: are you sure that you have re executed configure, and that you have the above build USB drivers: yes message? don't forget to call make too. I see no reason for not having tripplite_usb if the above are met. please, fix that point first. I suspect it is because of my limited knowledge of compiling from source. Basically I have the source directory in my home directory. I login as root and run this: ./configure --with-user=ups --with-group=nut --prefix=/usr --exec-prefix=/ --sysconfdir=/etc/nut --mandir=/usr/share/man --libdir=/lib --includedir=/usr/include --without-ssl --with-hal --with-cgi --with-dev --enable-static --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut --with-drvpath=/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut --with-htmlpath=/usr/share/nut/www --with-pidpath=/var/run/nut --datadir==/usr/share/nut --with-pkgconfig-dir=/usr/lib/pkgconfig That seems to configure correctly, but when I run make I do get a lot of errors; all from snmp-ups.c. Not sure if that is normal or not. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Arjen de Korte nut+us...@de-korte.org writes: In that case, try if adding --without-snmp to the configure command line helps. It shouldn't (since the prerequisites for building the snmp-ups driver should be checked automatically), but chances are this is failing for you. I think I'm getting some where. I installed smnp-dev and the make and make install went through with no errors, but I cannot find the directory it put nut. The only thing I can find is the directory: /lib/nut --with-cgipath=/usr/lib/cgi-bin/nut There is no /lib/nut directory. Maybe the ./configure is wrong? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Arjen de Korte nut+us...@de-korte.org writes: If you followed the instructions Arnaud send before, you told the configuration script --with-drvpath=/lib/nut So when you ran 'make install' the drivers were probably installed there, so you may need to try /lib/nut/tripplite_usb -D -u root -a Tripp-Lite Although I do have that tag in my ./configure, I do not have the directory /lib/nut after running make install. I have a lot of errors after running make and make install. All related to snmp-ups.c ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
I did manage to get tripplite_usb and upsdrvctl working with different tags in ./configure, but I still do not think it is correct. This is my output for tripplite_usb -D -a ups1: Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.1) Warning: This is an experimental driver. Some features may not function correctly. send_to_all: SETINFO driver.parameter.port auto debug level is '5' Can't chdir to /var/run/nut --with-altpidpath=/var/run/nut: No such file or directory This is my output for upsdrvctl start: Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.1) Warning: This is an experimental driver. Some features may not function correctly. Can't chdir to /var/run/nut --with-altpidpath=/var/run/nut: No such file or directory Driver failed to start (exit status=1) It seems that whenever I specify a different directory in a ./confgure tag it does not get applied right. Thanks for helping thus far. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
When I simply copy and replace the following I get this at the end of ./configure: checking user to run as... ups--with-group=nut--sysconfdir=/etc/nut/--mandir=/usr/share/man--libdir=/lib/cludedir=/usr/include/--without-ssl--without-hal--with-cgi--with-dev--enable-static--with-statepath=/var/run/nut/--with-altpidpath=/var/run/nut checking group membership of user to run as... nobody configure: error: If you specify --with-user, you also must specify --with-group The output in ssh when I paste your directions looks like this: ./configure --with-user=ups\ --with-group=nut\ --sysconfdir=/etc/nut/\ --mandir=/usr/share/man man/man-db/ --mandir=/usr/share/man\ --libdir=/lib/ Display all 161 possibilities? (y or n) --libdir=/lib/cludedir=/usr/include/\ --without-ssl\ --without-hal\ --with-cgi\ --with-dev\ --enable-static\ --with-statepath=/var/run/nut/\ --with-altpidpath=/var/run/nut Am I the only one that has trouble compiling this with Ubuntu? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Yes, This is my config summary: enable SSL development code: yes enable libwrap (tcp-wrappers) support: no enable IPv6 support: yes build CGI programs: no build and install the development files: no build serial drivers: yes build SNMP drivers: yes build USB drivers: yes enable HAL support: no build neon based XML driver: no build Powerman PDU client driver: no Is there another way to update to 2.4 other than building from source? I can't seem to get this to work and it is probably because I am relatively new to linux. After configuring it with those tags I still do not have upsdrvctl. When doing this upsdrvctl start I get this bash: /sbin/upsdrvctl: No such file or directory. There is now nothing in /usr/local/ups/bin or /usr/local/ups/sbin. Arnaud Quette aquette@gmail.com writes: have you done the make uninstall, then used the configure directives above, then make ; make install? ___ Chris Abel Systems and Network Administrator Wildwood Programs 2995 Curry Road Extension Schenectady, NY 12303 518-836-2341 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Arnaud Quette aquette@gmail.com writes: ok, before going to deep on this and wasting too much time on compilation, I'd like to have: - the output of lsusb -vv -d09ae:0001. Bus 001 Device 002: ID 09ae:0001 Tripp Lite Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x09ae Tripp Lite idProduct 0x0001 bcdDevice0.01 iManufacturer 1 TRIPP LITE iProduct2 TRIPP LITE UPS iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 60mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.00 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 52 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Device Status: 0x (Bus Powered) - your USB topology (ie is the UPS plugged on a root hub, are there other devices on the same bus, ...) Bus 002 Device 001: ID : Bus 001 Device 005: ID 05ac:0302 Apple Computer, Inc. Apple Optical Mouse [Fujitsu] Bus 001 Device 004: ID 05ac:0204 Apple Computer, Inc. Bus 001 Device 003: ID 05ac:1002 Apple Computer, Inc. Apple Extended Keyboard Hub [Mitsumi] Bus 001 Device 002: ID 09ae:0001 Tripp Lite Bus 001 Device 001: ID : Yes there are other devices on the same bus. - the result of ls -l /dev/bus/usb/XXX/YYY where XXX is the Bus number and YYY the Device number as shown by lsubs) crw-rw-r-- 1 root nut 189, 1 2009-09-04 12:50 /dev/bus/usb/001/002 once this part is ok, we'll check again to test 2.4.1 from the source tree. Hope that helps. ___ Chris Abel Systems and Network Administrator Wildwood Programs 2995 Curry Road Extension Schenectady, NY 12303 518-836-2341 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] [Nut-upsdev] CyberPower 550SL reports LB and OB when on line power
Hi, If it helps, I have a Cyberpower CP485SL/AE485, which may be similar enough to yours. I'm using a straight-through serial cable (no twists or jumpers anywhere) and I'm using the genericups driver (type 7, though I think the type 22 works the same). I have not had to redfine any of the serial control signals in ups.conf. Just running the driver (genericups -a MyUps -D) shows me sensible looking status values as the UPS goes first to battery, then to low battery, then shutting off. Chris On 2 Aug 2008 at 15:38, orangevixen wrote: Thanks, I just checked and there are no other processes using serial port 2 (/dev/ttyS1). I have my UPS connected to serial port 2, my modem on serial port 3, and nothing is connected to serial port 1. I tried connecting my UPS to serial port 1 but I got the same result. My setserial script looks like: SETSERIAL=/bin/setserial # Serial port 1 (COM1), onboard to nothing $SETSERIAL /dev/ttyS0 port 0x3f8 irq 4 # Serial port 2 (COM2), onboard to UPS $SETSERIAL /dev/ttyS1 port 0x2f8 irq 3 # Serial port 3 (COM3), ISA fax/modem $SETSERIAL /dev/ttyS2 port 0x3e8 irq 7 # Serial port 4 (COM4), USA nothing #$SETSERIAL /dev/ttyS2 port 0x3e8 irq 7 I also think that the whole problem might be my serial cable, since my CP550SL did not come with one and it says I need to contact them to get one. I contacted them and asked them to send me one yesterday. I hope they keep their promise. -Tara On 2008.08.02 08:45 Charles Lepple wrote: setserial requires no initialization; however, if you ran it before starting NUT, and then after starting NUT, you would probably see different results on the output pins. To double-check that there are no other programs using the serial port in the background, run 'lsof | grep ttyS' as root. -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser -- [EMAIL PROTECTED] www.gatcombe.com ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Genericups type 22 with Cyberpower CP485SL/AE485
Hi, I'm new to this list and I have a question concerning using the genericups driver (type 22) with the Cyberpower 485 in serial mode. When running the driver in debug mode: genericups -a myupsname_genericups22 -DD I observe the following statuses as the mains power dies, switching over to battery power, and then letting it discharge. Initially, with mains power on, status = OL. When mains power goes off, and we run on battery, status = OB. When battery level drops sufficiently the UPS starts beeping, and status = OB OL. Shortly before battery dies the UPS beeps more frequently, status = OB OL. Battery dies, then status = OB, and then changes to OL. When power is restored, status toggles from OB to OL to OB to OL a few times and then stays at OL. I assume that at the point we get OB OL this is the place we would be shutting down the computer? Why when the battery is discharged do we see the status OL? Is this just a limitation of using the genericups driver instead of one that is more appropriate for my UPS? I did try using the powerpanel driver but that timed out and did not find the UPS. Genericups type 7 seems to work the same as type 22. Is the genericups driver one that simply monitors the CTS, DTR etc. signals? If so should I care about these signals polarities, or does what I am already seeing indicate that everything is working as well as I can expect (that is without having a driver exactly for my UPS)? Thanks, Chris -- [EMAIL PROTECTED] www.gatcombe.com ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] MGE Ellipse Max 1100 configuration question
On Monday 02 June 2008 16:29:17 you wrote: 2008/6/1 Chris Cohen [EMAIL PROTECTED]: Sorry for the delay. On Friday 30 May 2008 09:30:45 you wrote: Hi Chris, I just booted into a non-xen kernel (linux-image-2.6.24-17-server). Ran /lib/nut/usbhid-ups -a mgeups. The UPS shut down again and so did my entire network... The error message is still the same. So I don't think my problem is xen related? One thing that is worth checking, if this system is HAL enabled. In that case, something like 'hald-addon-hid-ups' might be claiming the UPS and I have no idea how well this is handled (if at all). HAL isn't installed. :) point taken. can you send us a gzip'ed trace (level 3) of the driver, in the shutdown context. What do you mean? The output of /lib/nut/usbhid-ups -a mgeups -u root -DD? right, just add one more D (debug level 3 == -DDD) see attached trace.gz. UPS went off, but I traced from a machine nut beeing backed up so you can see how the ups gets back up I think. -- Thanks Chris trace.gz Description: GNU Zip compressed data ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] MGE Ellipse Max 1100 configuration question
On Monday 02 June 2008 17:44:57 you wrote: see attached trace.gz. UPS went off, but I traced from a machine nut beeing backed up so you can see how the ups gets back up I think. I see at least five 'Full update...' and dozens of 'Quick update...'. Unless you specified some insanely small values for 'pollfreq' and 'pollinterval' this should be much longer than 5-10 seconds. The end of the trace shows that the driver is killed by signal 15. This is *not* caused by the driver itself, but by another process. Yes, I rebooted that machine to connect it back on the ups power. Could it be you didn't configure enough (or any at all) power in upsmon.conf? In order to debug this, make sure that there is *no* upsd server running on the system during testing. Oh, uhm.. well :) This is what I have in upsmon.conf: # Generated by MGE Office Protection Systems - Personal Solution Pac (mgeops-psp, version 3.0.7) MONITOR [EMAIL PROTECTED] 1 monuser mgepass master MINSUPPLIES 1 SHUTDOWNCMD /sbin/shutdown -h +0 NOTIFYCMD /sbin/upssched POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG+EXEC NOTIFYFLAG ONBATT SYSLOG+EXEC NOTIFYFLAG COMMOK IGNORE NOTIFYFLAG COMMBAD IGNORE RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 The file was genereated by psp and worked just fine on the other pc. -- Thanks Chris ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] MGE Ellipse Max 1100 configuration question
Rejected by moderator... had to paste the attachment to http://paste.debian.net/3784/ On Thursday 22 May 2008 15:35:28 you wrote: Try to run the driver with '-u root -DD' to rule out permissions problems. Done. It shut down the UPS and my entire network. :( Weird. This is not something the driver can do, unless you specifically tell it to kill the power (-k). I see that you're using Linux 2.6.24-17-xen. I do. (Running Ubuntu Hardy LTS) But I redirected the output to a file which I attached. (I don't know what all this means...) Well, it appear to detect the UPS all right: Checking device (0463/) (001/008) - VendorID: 0463 - ProductID: - Manufacturer: MGE UPS SYSTEMS - Product: Ellipse MAX - Serial Number: PbAc - Bus: 001 Trying to match device Device matches HID descriptor length 882 Report Descriptor size = 882 Using subdriver: MGE HID 1.01 Short of the weird value reported for the serial number, nothing wrong so far. It only looks like it reports the wrong indexed string, which is very strange. What does 'lsusb -vvv' report? I attached the relevent part as a file since its pretty long. I'm not sure if this isn't due to the fact that you seem to be running Linux 2.6.24-17-xen. I don't know if the libusb library will work with that. Hmmm... I could install a non-xen kernel on dom0? -- Thanks Chris ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] MGE Ellipse Max 1100 configuration question
On Thursday 22 May 2008 16:07:08 you wrote: Weird. This is not something the driver can do, unless you specifically tell it to kill the power (-k). I see that you're using Linux 2.6.24-17-xen. I do. (Running Ubuntu Hardy LTS) The fact that you're able to run this driver on your desktop system without problems, leads me to believe that the problem is in Xen and not in either the driver and/or the UPS itself. A quick search via Google shows that USB support for anything other than a keyboard and mouse is experimental at best in Xen at the moment, so I think this may be where the problem is. Since I know crap about Xen (or any other virtualization software for that matter), I have no idea if and what can be done to correct this. I just booted into a non-xen kernel (linux-image-2.6.24-17-server). Ran /lib/nut/usbhid-ups -a mgeups. The UPS shut down again and so did my entire network... The error message is still the same. So I don't think my problem is xen related? One thing that is worth checking, if this system is HAL enabled. In that case, something like 'hald-addon-hid-ups' might be claiming the UPS and I have no idea how well this is handled (if at all). HAL isn't installed. :) -- Thanks Chris ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] trust pw4120m
hello can anyone say me if it is possible to upgrade the firmware of my ups? i mean.. for example i can only run a 10 sec selftest (with original software from trust: winpower...). i see that the internal driver is 1.5.4. thx -- Christian Ruppert signature.asc Description: PGP signature ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] apcsmart constant read failure errors
I get the following errors constantly in my messages log: Sep 21 11:53:37 cgydc002 upsd[22659]: Connection from 127.0.0.1 Sep 21 11:53:37 cgydc002 upsd[22659]: Host 127.0.0.1 disconnected (read failure) Sep 21 11:53:37 cgydc002 upsd[22659]: Connection from 127.0.0.1 Sep 21 11:53:37 cgydc002 upsd[22659]: Host 127.0.0.1 disconnected (read failure) Sep 21 11:53:37 cgydc002 upsd[22659]: Connection from 127.0.0.1 Sep 21 11:53:37 cgydc002 upsd[22659]: Host 127.0.0.1 disconnected (read failure) Sep 21 11:53:37 cgydc002 upsd[22659]: Connection from 127.0.0.1 Sep 21 11:53:37 cgydc002 upsd[22659]: Host 127.0.0.1 disconnected (read failure) Sep 21 11:53:37 cgydc002 upsd[22659]: Connection from 127.0.0.1 Sep 21 11:53:37 cgydc002 upsd[22659]: Host 127.0.0.1 disconnected (read failure) I've upgraded to the latest stable NUT, but the problem persists. With upsd debugging on I get: [EMAIL PROTECTED] sbin]# ./upsd -u nut -DDD -f Network UPS Tools upsd 2.0.4 /var/state/ups is world readable Connected to UPS [SmartUPS1400]: apcsmart-ttyS1 Synchronizing...UPS [SmartUPS1400]: dump is done done acl_check: localhost: match 1 ACL [localhost] matches, action=1 Connection from 127.0.0.1 acl_check: localhost: match 1 ACL [localhost] matches, action=1 write: [destfd=6] [len=33] [VAR SmartUPS1400 ups.status OL ] Host 127.0.0.1 disconnected (read failure) acl_check: localhost: match 1 ACL [localhost] matches, action=1 Connection from 127.0.0.1 acl_check: localhost: match 1 ACL [localhost] matches, action=1 write: [destfd=6] [len=39] [VAR SmartUPS1400 input.voltage 117.0 ] Anyone know what I can do to get this thing to quit complaining? Thanks, Chris ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] apcsmart constant read failure errors
Charles Lepple wrote: On 9/21/06, Chris Cameron [EMAIL PROTECTED] wrote: Anyone know what I can do to get this thing to quit complaining? Does 'upsc [EMAIL PROTECTED]' actually return anything? Can you tell us a little more about your system? Client programs work fine most the time. [EMAIL PROTECTED] bin]$ sudo ./upsc [EMAIL PROTECTED] battery.alarm.threshold: 0 battery.charge: 100.0 battery.charge.restart: 15 ... etc. Nagios has a client program, which fails maybe 20% of the time. I'm not sure what more useful information I can give. It's a RedHat 9 system running NUT 2.0.4. The UPS is a SmartUPS 1400, connected via a serial cable. At one point this was working fine, then these came out of no where. This was on NUT 2.0.1 I believe. I'm using the same config files now as with the previous version. ups.conf: [SmartUPS1400] driver = apcsmart port = /dev/ttyS1 upsd.conf: ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACL accounting 192.168.121.11/32 ACCEPT localhost accounting REJECT all upsd.users: [nut] password = password allowfrom = localhost accounting upsmon master ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Smart-UPS with SuSE 9.0/Nut
Anyone have any ideas? Sorry I'm just stuck at this point. Chris Boyd [EMAIL PROTECTED] 09/05/06 3:09 OK I've changed to a different machine as I don't think it install all of nut. Now I'm working with nut-1.2.2 I changed the driver to newapc and it's now finding the RT 3000 correctly. I'm still getting the reject TCP in messages: upsd[17078]: Rejecting TCP connection from 10.133.1.49 Sep 5 15:00:35 usit-hq-s03 upsmon[17077]: Poll UPS [EMAIL PROTECTED] failed - Read error: No such file or directory I've set the owner to nobody after trying to creating a user and setting it as owner on the conf files as well as /dev/ttyS0. Here is the message I get when starting ups: Starting service NUT: Network UPS Tools - UPS driver controller 1.2.2 Network UPS Tools (version 1.2.2) - APC Smart protocol driver Driver version 1.4, command table version 1.2 Detected Smart-UPS RT 3000 XL [NS0545001690 ] on /dev/ttyS0 Network UPS Tools - UPS driver controller 1.2.2 Network UPS Tools upsd 1.2.2 /var/lib/ups is world readable Read data for UPS [myups] successfully Data source for UPS [myups]: newapc-ttyS0 Network UPS Tools upsmon 1.2.2 UPS: [EMAIL PROTECTED] (master) (power value 1) Using power down flag file /etc/killpower done Broadcast Message from [EMAIL PROTECTED] (somewhere) at 15:00 ... UPS [EMAIL PROTECTED] is unavailable Here are the changes to the conf files: ups.conf [myups] driver = newapc port = /dev/ttyS0 cable = 940-0024C sdtype = 0 upsd.conf ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACL usit 10.133.0.0/16 ACCESS grant monitor localhost usit ACCESS deny all all upsd.users [monuser] password = password allowfrom = usit upsmon master upsmon.conf RUN_AS_USER nobody MONITOR [EMAIL PROTECTED] 1 monuser password master Charles Lepple [EMAIL PROTECTED] 09/04/06 4:41 On 9/4/06, Chris Boyd [EMAIL PROTECTED] wrote: stat /etc/ups/upsd.conf: No such file or directory This is key. ups.conf configures the drivers, whereas upsd.conf controls access to the driver from the network. If you are setting up a standalone system, you can use this as a starting point for upsd.conf: #== ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCEPT localhost REJECT all #== For more details, run 'man upsd.conf' -- - Charles Lepple - This email message is intended only for the addressee(s) and contains information that may be confidential and/or copyrighted. If you are not the intended recipient please notify the sender by reply email and immediately delete this email. Use, disclosure or reproduction of this email by anyone other than the intended recipient(s) is strictly prohibited. USIT has scanned this email for viruses and dangerous content and believes it to be clean. However, virus scanning is ultimately the responsibility of the recipient. - ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser - This email message is intended only for the addressee(s) and contains information that may be confidential and/or copyrighted. If you are not the intended recipient please notify the sender by reply email and immediately delete this email. Use, disclosure or reproduction of this email by anyone other than the intended recipient(s) is strictly prohibited. USIT has scanned this email for viruses and dangerous content and believes it to be clean. However, virus scanning is ultimately the responsibility of the recipient. - ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Smart-UPS with SuSE 9.0/Nut
I suspected as much. For some reason installing nut using apt didn't dl all the config files. SuSE isn't the greatest with apt (nor YAST). Anyway I copied over the old config files from 1.2.2 server to the 2.0.2 server, changed ACCESS to ACCEPT and shangri la. Thanks a milion Charles Lepple [EMAIL PROTECTED] 09/07/06 2:14 On 9/7/06, Chris Boyd [EMAIL PROTECTED] wrote: Anyone have any ideas? Not for NUT 1.2, no. That version is very old, and a number of fundamental changes have been made since then. -- - Charles Lepple - This email message is intended only for the addressee(s) and contains information that may be confidential and/or copyrighted. If you are not the intended recipient please notify the sender by reply email and immediately delete this email. Use, disclosure or reproduction of this email by anyone other than the intended recipient(s) is strictly prohibited. USIT has scanned this email for viruses and dangerous content and believes it to be clean. However, virus scanning is ultimately the responsibility of the recipient. - ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Question about slave shutdown
Dear all: I connect 2 PCs to the UPS, one is master and the other is slave. When the battery becomes low, the masteronly shutdown itself and the UPS load ! It seems that the slave can’t receive the FSD signal, and I didn't see the master send FSD to the slave.Perhaps something is wrong with my configuration. What shall I do? Any help is greatly appreciated ! Regards, Chris 你 不 想 试 试 今 夏 最 “酷” 的 邮 箱 吗 ？ 蕴 涵 中 华 传 统 文 化 于 世 界 一 流 科 技 之 中，创 新 Ajax 技 术，126 “D 计 划”火 热 体 验 中 ！ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Question about slave shutdown
Dear all: I connect 2 PCs to the UPS, one is master and the other is slave. When the battery becomes low, the masteronly shutdown itself and the UPS load ! It seems that the slave can’t receive the FSD signal, and I didn't see the master send FSD to the slave.Perhaps something is wrong with my configuration. What shall I do? Any help is greatly appreciated ! Regards, Chris 你 不 想 试 试 今 夏 最 “酷” 的 邮 箱 吗 ？ 蕴 涵 中 华 传 统 文 化 于 世 界 一 流 科 技 之 中，创 新 Ajax 技 术，126 “D 计 划”火 热 体 验 中 ！ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
