similar to: The system doesn't shutdown

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,

> > 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

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 Mon, 26 Oct 2015, George Anchev wrote: > Hello, > I have been following the details in this article to configure my UPS: > > http://rogerprice.org/NUT.html > > However the system won't shutdown although file permissions look ok: > > ls -alF /usr/sbin/ups* > -rwxr--r-- 1 upsd daemon 64984 Oct 15 ?2014 /usr/sbin/upsd* > -rwxr--r-- 1 upsd daemon 48584 Oct 15

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:

Hello list, just a quick email to report that the following UPS was supported (mostly) out of the box: Model: PowerWalker VI 850 LCD Driver: blazer_usb upsc Output (please note I have manually populated the high and low voltages): battery.charge: 100 battery.voltage: 13.50 battery.voltage.high: 13.5 battery.voltage.low: 10 battery.voltage.nominal: 12.0 beeper.status: enabled device.type: ups

I?m wondering if what I have done is good : # get the source from github on my computer # autogen.sh # name=nut # ./configure --prefix=/ --sysconfdir=/etc/$name --mandir=/usr/share/man --libdir=/usr/lib --includedir=/usr/include --datadir=/usr/share/$name --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut --with-drvpath=/lib/nut --with-pidpath=/var/run/$name

I'm pretty sure, I've install pkg-config, but I will check it monday after my holliday. This is my test steps: - Shutting down nut-client (upsmon) - Only nut-server (driver + upsd) is running - upsmon.conf have been revert to normal shutdown, no upssched - upsc myups return ups stats then: upsmon -K -DDDDD, here is the output: kill: No such process UPS: myups at

On Jul 31, 2013, at 9:07 AM, James HORLEY wrote: > I?m wondering if what I have done is good : > # get the source from github on my computer > # autogen.sh > # name=nut > # ./configure --prefix=/ --sysconfdir=/etc/$name --mandir=/usr/share/man > --libdir=/usr/lib --includedir=/usr/include --datadir=/usr/share/$name > --with-statepath=/var/run/nut

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

On Tue, 27 Oct 2015, George Anchev wrote: > Oct 26 21:02:56 i7 upsd[2227]: Startup successful ... > Oct 26 21:02:56 i7 upsmon[2229]: Startup successful ... > Oct 26 21:04:51 i7 upsmon[2230]: UPS myups at localhost on battery > Oct 26 21:05:11 i7 upsmon[2230]: UPS myups at localhost on line power Power was off for 20 seconds so you should have seen upssched activity. Could you run

Dear all, I am using the Microsoft Windows XP SP3 and would like to use the Windows MSI installer 2.6.1-1 I tried to configure NUT manually, but until now failed. If possible I would like to use the PowerWalker Line-Interactive VI 1400 device which should work with blazer_usb Does anyone have possibility to provide me the correct configuration for the files (ups.conf, upsd.{users,conf} and

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

Is it possible to shutdown earlier by certain conditions: by battery level and estimated by UPS runtime. In APCUPSD this done by config options "BATTERYLEVEL" "MINUTES". By what condition NUT shutdown server? How to disable UPS shutdown?

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

On Aug 1, 2013, at 8:15 AM, Charles Lepple wrote: > On Jul 29, 2013, at 7:12 AM, James HORLEY wrote: > >> There?s a software advised by the constructor that work on linux (http://www.power-software-download.com/viewpower.html), unfortunately it?s heavy (tomcat and java) and I don?t find it as flexible as NUT. > > We have a development branch called "voltronic-driver"

Jim Klimov <jimklimov+nut at gmail.com> > > I believe some fixes were applied to the branch since your report (most visibly, about battery time settings), are you in position to test how it behaves now? :) Hi: I got another ups for testing. so I test the new commit for both APC SRT3000XL and SMT2200RM2U. the results below: 1. I get the new attribute "ups.test.result" for

Jim Klimov <jimklimov+nut at gmail.com> > > I believe some fixes were applied to the branch since your report (most visibly, about battery time settings), are you in position to test how it behaves now? :) Hi: I got another ups for testing. so I test the new commit for both APC SRT3000XL and SMT2200RM2U. the results below: 1. I get the new attribute "ups.test.result" for