search for: eaton5e

Hi, I have been running nut successfully for a long time with my Debian 11 server. I upgraded my server to Debian 12 today, which upgraded nut also from 2.7.4-13 to 2.8.0-7. I noticed that after upgrade there was a upssched process running and taking 100% cpu time. I checked if there were any changes to configuration file formats with nut upgrade and only differences I noticed were a terminology

Device manufacturer and name: *Eaton 5E 1100i USB* *upsc eaton5e* Init SSL without certificate database eaton5e root at eger:/home/siposg# upsc eaton5e Init SSL without certificate database battery.charge: 100 battery.runtime: 3160 battery.type: PbAc device.mfr: EATON device.model: 5E 1100i device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 d...

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,

...clearly truncated; I guess this correlates to approximately floor((100 * 60)/2200)) It took me a while to remember that I needed to configure upsd.users and use a completely different command ( upscmd instead of upsc ) to interact with the UPS and get it to run a battery test. In my case upscmd eaton5e test.battery.start.quick allowed me to see a maximum default.battery.voltage.high of 26.5 (This typically reads at ~27.50 (27.20 - 27.80) while on line power) It took me a bit of effort to arrange a larger load that I don't care about, but after setting it up this weekend I have an initial...

...-reload-rules > > I think I recall hearing systemd ate udev? > > # systemctl daemon-reload > > Then I disconnected/reconnected the UPS, since that was faster than looking up re-triggering udev rules. > > > # cat >> /etc/ups/ups.conf << HEREDOC > > [eaton5e] > driver = blazer_usb > port = auto > vendorid = 06da > productid = 0003 > HEREDOC New work is being done on nutdrv_qx rather than blazer_*, but fortunately it is fairly similar to configure: http://networkupstools.org/docs/man/nutdrv_qx.html...

...dev1] driver = "usbhid-ups" port = "auto" vendorid = "0463" productid = "FFFF" product = "5E" bus = "002"I have put that exact info into /etc/ups/ups.conf - it's the only info not commented with a # in the file. I changed the name to eaton5e though. When I then run: [root at fedora ~]# /usr/sbin/usbhid-ups -DDDD -a eaton5e Network UPS Tools - Generic HID driver 0.41 (2.7.4)USB communication driver 0.33 0.000000 debug level is '4' 0.002054 upsdrv_initups... 0.017685 Checking device (0463/FFFF) (002/120) 2.024057 - Vend...

...ages and bad power quality. Thanks to its small size the 5E can be installed easily in a business environment or at home." Network UPS Tools upsc 2.7.4-151-g9209e18 The git development version was required to get any communication with the UPS; however a number of surprises awaited me. upsc eaton5e at localhost device.mfr: CTN device.model: USB UPS device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 0003 driver.parameter.synchronous: no driver.parameter.vendorid: 06da driver.version: 2....

Dear all, I got nut going on one machine as standalone and on another 2 as master/slave and would like to add some checks to nagios to make sure that things are in order. Most of the checks I've seen out there use upsc to check the ups. This is a step forward compared to no monitoring, however as far as I can tell it doesn't really address what I think is a critical point: upsmon is

...t;, GROUP="nut" HEREDOC # udevadm control --reload-rules I think I recall hearing systemd ate udev? # systemctl daemon-reload Then I disconnected/reconnected the UPS, since that was faster than looking up re-triggering udev rules. # cat >> /etc/ups/ups.conf << HEREDOC [eaton5e] driver = blazer_usb port = auto vendorid = 06da productid = 0003 HEREDOC I still need to perform the following calibrations: default.battery.voltage.high = value Maximum battery voltage that is reached after about 12 to 24 hours charging. If you want the driv...

On my Nagios monitoring system I use check_nut_plus (that in turn calls upsc) to monitor the status (ups.status), load (ups.load), battery charge (battery.charge) and runtime (battery.runtime). If these return "unknown", it means upsd is no longer monitoring the UPS. As long as you get data, upsd is working. PS: as an example, this is my check for the status: /usr/bin/perl -w

...t; > > vendorid = "0463" > > productid = "FFFF" > > product = "5E" > > bus = "002" > > I have put that exact info into /etc/ups/ups.conf - it's the only info not commented with a # in the file.  I changed the name to eaton5e though. > > When I then run: > > [root at fedora <mailto:root at fedora> ~]# /usr/sbin/usbhid-ups -DDDD -a eaton5e > > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > > USB communication driver 0.33 > >    0.000000 debug level is '4' > &...

Hi, Thanks Jim! Here is more system information from the commands you mentioned. Kari root at fricka:~# lsof -p 1716171 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1002/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME upssched 1716171 root cwd DIR 8,2 4096 2 /

Hi, Thanks Jim! Here is more system information from the commands you mentioned. Kari root at fricka:~# lsof -p 1716171 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1002/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME upssched 1716171 root cwd DIR 8,2 4096 2 /

...tes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 20 Device Status: 0x0001 Self Powered | Content of |/etc/nut/ups.conf| |[Eaton5E] driver = blazer_usb port = auto | Result of |$ upsdrvctl start| for |usbhid-ups| driver: |Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 No matching HID UPS found Driver failed to start (exit status=1) | Result o...

So, got some good news: I hear(*) I managed to reproduce the problem with current NUT master and an adapted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT

So, got some good news: I hear(*) I managed to reproduce the problem with current NUT master and an adapted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT

After launching the command several times, with debug (posted by new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT

After launching the command several times, with debug (posted by new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT

> On Oct 31, 2016, at 10:15 PM, Michael Evans <mjevans1983 at gmail.com> wrote: > > Are there any other tests I can perform or ways that I can help gather data to get the longer tests supported? > The "test.battery.start" command takes a parameter in seconds (defaults to 600): https://github.com/networkupstools/nut/blob/v2.7.4/drivers/nutdrv_qx_blazer-common.c#L286