similar to: problems with nut - openSUSE 10.3

hi i bought a ultra ULT31502 ups someone seem able to run this ups with nut just see Dean thread on: http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=770423&Tab=11&NoMapp=0 i use suse 10.1, i installed nut the ups is connected directely to my computer with an usb cable lsusb return Bus 001 Device 004: ID 0d9f:0001 Powercom Co., Ltd with lsmod, i can see

P.S.2 Today I experienced something weird. As I was working, the system started a shutdown and did shut down, then the UPS got powered off and then back on - an expected behavior for a power fail situation. However there was no power failure! I ran nut-journal to check what happened: Previous complete boot through shutdown Oct 29 10:09:33 i7 upsdrvctl[1966]: Using subdriver: MGE HID

On Tue, 27 Oct 2015, George Anchev wrote: > Yes, that was the power off test. However the upssched-cmd script gave > absolutely no signs of activity. Even it's logger lines don't show up in > journalctl. No any permission error messages - nothing. Only the 2 > messages from upsmon - on battery and then on line power. > > Here is the nut-report: >

This note describes a heartbeat technique for validating the integrity of a NUT installation. Introduction ------------ A NUT configuration may run for months with little or no output to a system administrator to assure that the combined processes are running correctly. The technique described in this note verifies that the ups driver, upsd, upsmon, upssched and upssched-cmd components are

Yes: Previous complete boot through shutdown Oct 26 21:02:54 i7 upsdrvctl[1955]: Using subdriver: MGE HID 1.32 Oct 26 21:02:55 i7 upsdrvctl[1955]: Network UPS Tools - Generic HID driver 0.38 (2.7.1) Oct 26 21:02:55 i7 upsdrvctl[1955]: USB communication driver 0.32 Oct 26 21:02:56 i7 upsdrvctl[1955]: Network UPS Tools - UPS driver controller 2.7.1 Oct 26 21:02:56 i7 upsd[2226]: fopen

Yes, that was the power off test. However the upssched-cmd script gave absolutely no signs of activity. Even it's logger lines don't show up in journalctl. No any permission error messages - nothing. Only the 2 messages from upsmon - on battery and then on line power. Here is the nut-report: http://www.filehosting.org/file/details/518300/NUT.report --- George Anchev On Tue, Oct 27,

On Tue, 4 Apr 2017, Arnaud Quette wrote: > Hi Jon, Stuart and the list > > 2017-04-04 1:09 GMT+02:00 Stuart Gathman <stuart at gathman.org>: > Which NOTIFYCMD is run when there is an ALARM? > Have you specified that in your upsmon.conf? > > And that is the question of the hour.? How do you specify that?? Note > that this is not the REPLBATT

Dear Chales, Thanks for your quick reply. I have Raspberry with last Kernel [Linux pi1 3.18.6+ #753 PREEMPT Sun Feb 8 14:47:22 GMT 2015 armv6l GNU/Linux] If <upsdrvctl>, <upsd> and <upsmon> are stopped <nutdrv_atcl_usb> Works well without any error as "Device or resource busy". If I run <upsc> command never receive any value from my ups <upsc ups at

Dear List, The driver usbhid-ups does not detect my MGE Ellipse 1500. I'm running openSuSE Linux 10.3, kernel 2.6.22 with mgeups-psp-3.0.4-2, nut-2.2.0-20 installed from MGE's rpm's. (Merci MGE!) lsusb shows: Bus 001 Device 004: ID 0463:ffff MGE UPS Systems UPS /etc/ups/ups.conf says: [myups] driver = usbhid-ups port = auto desc = "Local UPS"

On Thu, 8 Sep 2016, Jeff Bowman wrote: > That said, is there a way to manually poll the driver for UPS/power line > status? I ask because I can foresee a scenario such as this: ... > So I'd like to be able to remote in and check the status to make sure > everything is OK. If not, then I can manually run my shutdown > script/process and start the cycle all over again. (Note:

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

Hi all, I would like to check two UPS in two different buildings with an ubuntu server. I use SNMP on both UPS. The cgi-page displayed all information as expected, but if I pull the fuse for one UPS in building A, none action occur. I expected that I get a mail "UPS A on Batt" and that after 5 minutes the shotdownscript starts. But no action. I saw that there is no upsmon process

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,

> > Did you see a line in the journal similar to this ? > Oct 06 22:49:54 pinta nut-delayed-ups-shutdown[1854]: > nut-delayed-ups-shudown.service calling > upsdrvctl to shut down UPS unit Never after I disabled the service. I pasted the whole journal section of the successful shutdown from last email. However I have been thinking about this line

Greetings! I have successfully installed and configured nut package. All i want now is to power off ups. If i run upsmon -c fsd as root - everything goes fine, system and ups gracefully shutting down. If i unplug power cable from an ups, then system is down, but ups still on load. Any help would be appreciated. Debian Lenny x86 ups.conf [ippon] driver = megatec port = /dev/ttyS0

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 "UNKNOWN" so that all status changes, no > matter how wierd, can be caught. Such a catch-all <notify type> would also

Thank you VERY much, Roger, for your detailed explanations. I'm going to choose to heed your warning. > On Thu, 8 Sep 2016, Jeff Bowman wrote: > > > 1. CLI error: I get an error when running ?upsdrvctl start?: ?Can't > > claim USB device [051d:0003]: libusb0-dll:err [claim_interface] could not > claim interface 0, win error: The requested resource is in use.? The

Beautiful! The shutdown succeeded. Thank you very much. However there was no any notification on desktop at all. Only in journalctl. Here it is: Oct 27 23:38:11 i7 upsmon[2224]: UPS myups at localhost on battery Oct 27 23:38:11 i7 upssched[2244]: Timer daemon started Oct 27 23:38:11 i7 upssched[2244]: New timer: two-minute-warning-timer (5 seconds) Oct 27 23:38:11 i7 upssched[2244]: New timer:

On Thu, 29 Oct 2015, George Anchev wrote: > Today I experienced something weird. As I was working, the system > started a shutdown and did shut down, then the UPS got powered off and > then back on - an expected behavior for a power fail situation. However > there was no power failure! ... > Oct 29 10:46:46 i7 upsmon[2239]: UPS myups at localhost battery is low > Oct 29