search for: cuuut

Displaying 6 results from an estimated 6 matches for "cuuut".

2017 Apr 03
1
battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
On 03/04/17 22.11, Gene Heskett wrote: > On Monday 03 April 2017 14:13:08 Stuart D. Gathman wrote: > > Back on the mailing list, where such belongs. > [cuuut] >> We want the ALARM that the nut driver is >> generating, and upsd is passing on - to be acted on in some way by >> upsmon. Which NOTIFYCMD is run when there is an ALARM? [cuuut] I dont think any NOTIFYCMD is run when there is an ALARM Stuart. > I've not read the do...
2017 Apr 03
3
battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
On Mon, 3 Apr 2017, Gene Heskett wrote: >> > Nut, IIRC, can do a periodic battery test by putting it offline, using > the battery, for a predetermined length of time, weekly, monthly etc, We definitely don't want that in this instance either! (Unless it is a dual PS server.) We want the ALARM that the nut driver is generating, and upsd is passing on - to be acted on in some
2017 Apr 04
4
battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
2017-04-04 14:18 GMT+02:00 Jon Bendtsen <jon.bendtsen at jonix.dk>: > On 04/04/17 14.10, Roger Price wrote: > >> On Tue, 4 Apr 2017, Arnaud Quette wrote: >> >> > [cuuuuut] > > Hi Arnaud, It seems to me that, looking out into the future, there are >> three >> things upsmon needs: >> >> 1. A fall-through <notify type> of
2017 Apr 04
0
battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
On 04/04/17 15.19, Arnaud Quette wrote: > [cuuut] > there is a Github issue: https://github.com/networkupstools/nut/issues/415 > + a branch with the implementation: > https://github.com/networkupstools/nut/tree/upsmon_alarm > > For now: > - upsmon can react on the ALARM notify type, as with other events, and > WALL+SYSLOG+EX...
2017 Apr 12
0
HP R1500 G2 USB on Ubuntu
...udev rules > mv /lib/udev/rules.d/52-nut-usbups.rules /lib/udev/rules.d/62-nut-usbups.rules > cp /lib/udev/rules.d/62-nut-usbups.rules /etc/udev/rules.d/ > udevadm control --reload-rules > udevadm trigger > reboot server to be sure everything is OK what was the issue before that? [cuuut] > ups.serial: 3C80341001 if you put that in the ups.conf definition, would it have made it detect it without the issues above? [HPR1500] driver=usbhid-ups port=auto serial = 3C80341001 JonB
2017 Apr 12
4
HP R1500 G2 USB on Ubuntu
Hello, Control HP R1500 G2 with nut via USB. Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-72-generic x86_64) nut V2.7.1 installed from repository /etc/nut/ups.conf [HPR1500] driver=usbhid-ups port=auto After dealing hours with this, hope this will help some : rename udev rule to higher priority and move it to its right location, reload udev rules mv /lib/udev/rules.d/52-nut-usbups.rules