similar to: parallel redundant ups systems and shutdown cmd handling

2018-02-28 21:11 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>: > Hello, > > I think that on this file nutdrv_qx_megatec.c the definition for > shutdown.stayoff may be wrong. In the file the definition is "S%sR0000\r"m > while on the megatec protocol description ( > http://networkupstools.org/protocols/megatec.html) the command is just > "S%s\r".

I've built NUT 2.8.0 from source. When the nut-monitor runs: fopen upsmon.pid fails. I'm running as root, upsmon has root:root permissions as well as the other daemons and .conf files. I've tried configuring with and without --prefixpath --prefixaltpath. Is there something I am missing? Please see attached. Dan -------------- next part -------------- An HTML attachment was

Angel Tsankov wrote, On 12/6/2013 12:31 PM: > Hello, Ren?. > >> You can change the parameter >> ups.delay.start into your UPS to set the "Interval to wait before >> (re)starting the load (seconds)" >> >> use upsset to change the value. > > So far, the ups.delay.start parameter in my MGE Protection Center 675 > has always been equal to the

On Wed, 5 Oct 2016, Jeff Bowman wrote: > I?m trying to better understand OffDelay and OnDelay: > http://networkupstools.org/docs/man/usbhid-ups.html#_extra_arguments > > My server requires ~3? minutes to shut itself down. Considering this I?m > comfortable setting OffDelay to 300 (five minutes). > > How does this work in conjunction with the UPS hardware? Does NUT >

Angel Tsankov wrote, On 12/24/2013 1:22 AM: > On 12/06/2013 10:57 PM, Kris Jordan wrote: > > [...] >> (*) Some UPS's do provide extra options to determine when they will >> restore power to load. > > That would be a nice feature. > > Anyway, it is a strange thing that I can set the waiting time for > power to be restored if main power comes back before

On 12/06/2013 10:57 PM, Kris Jordan wrote: > [...] > (*) Some UPS's do provide extra options to determine when they will > restore power to load. That would be a nice feature. Anyway, it is a strange thing that I can set the waiting time for power to be restored if main power comes back before offdelay has elapsed, but the UPS ignores this setting if main power comes back after

Hi everyone, I've got a dataset with 12,000 observations. One of the variables (cleary$D1) is for an individual's country, coded 1 - 15. I'd like to create a dummy variable for the Baltic states which are coded 4,6, and 7. In other words, as a dummy variable Baltic states would be coded 1, else 0. I've attempted the following for loop: dummy <- matrix(NA, nrow=nrow(cleary),

I'm trying to better understand OffDelay and OnDelay: http://networkupstools.org/docs/man/usbhid-ups.html#_extra_arguments My server requires ~3? minutes to shut itself down. Considering this I'm comfortable setting OffDelay to 300 (five minutes). How does this work in conjunction with the UPS hardware? Does NUT immediately send a command to the UPS to wait for 300 seconds and then shut

Set with upsrw: ups.delay.shutdown=60 is the same as offdelay = 30. This time was done correctly by UPS. Set with upsrw: ups.delay.start=90 is the same as ondelay = 40. The UPS shut down and reset and forget about the settings. If I use the program in Win 10 settings in the program from Eaton are stable!? Jan. > -----Original Message----- > From: Nut-upsuser

On Oct 3, 2018, at 8:13 PM, Gabriel <jarod125 at gmail.com> wrote: > > On Tue, Oct 2, 2018 at 3:59 PM Charles Lepple <clepple at gmail.com> wrote: >> >> On Sep 27, 2018, at 6:59 PM, Gabriel <jarod125 at gmail.com> wrote: >>> >>> Hi, >>> >>> I'm struggling with a peculiar issue with my UPS. After a power >>>

Dear list, Can't make upssched notify me on event occured. OS: Debian, 2.6.26-1-amd64 Nut: 2.4.3-1.1squeeze1 UPS: Ippon Smart Winner 3000 connected via COM On event ( plug out the cord from UPS ) upsmon detect's status change to OB and gives WALL and syslog notify, but no script starting. In syslog no errors and no upssched process occured, just upsmon. There're no PIPE and LOCK

fredag 9 september 2016 kl. 18:57:36 CEST skrev Jeff Bowman: > I learned earlier from Roger Price's excellent explanation that a proper > configuration includes sending a 'delayed shutdown' signal to the UPS > hardware prior to shutting down the server. > Hi Jeff. > How is this accomplished? Does the USB driver handle this for us or must we > do something

Thanks On Sat, 16 Mar 2024 at 18:57, Charles Lepple <clepple_at_gmail.com_chribonn at duck.com> wrote: > > On Mar 14, 2024, at 11:41?AM, Alan via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: > > > Hi, > > > > My Cyber Power reports these two values. Each pair has the same value. > > > > Would they normally be the same thing? >

On Sep 27, 2018, at 6:59 PM, Gabriel <jarod125 at gmail.com> wrote: > > Hi, > > I'm struggling with a peculiar issue with my UPS. After a power > outage, the devices powered by it properly shut down via nut. > Eventually, the UPS also goes down. Power is still out, however, > roughly 40 seconds after the UPS shut down, it turns back on and it > starts supplying

Now that upsstats.cgi works, I've noticed that dummy-ups changes state every 5 minutes between OL and OB (probably when the 300 second timer expires). The UPS state stays online. Also "online" and "onbatt" are broadcast to the console probably via WALL. (The state changes don't seem to be form the ups as upsshed-cmd doesn't run). Upssched-cmd does run when the UPS

On Tue, Oct 2, 2018 at 3:59 PM Charles Lepple <clepple at gmail.com> wrote: > > On Sep 27, 2018, at 6:59 PM, Gabriel <jarod125 at gmail.com> wrote: > > > > Hi, > > > > I'm struggling with a peculiar issue with my UPS. After a power > > outage, the devices powered by it properly shut down via nut. > > Eventually, the UPS also goes down.

Hello world! Please, help me :-) I have a APC RS-800 usb and it don't shutdown. I try every things but nothing: don't shutdown. Uhmmmm My actual situation: tux:/home/effem# uname -a Linux tux 2.6.26-1-686 #1 SMP Wed Aug 20 12:56:41 UTC 2008 i686 GNU/Linux tux:/home/effem# wajig policy nut nut: Installato: 2.2.2-6 Candidato: 2.2.2-6 Tabella versione: 2.2.2-7 0 -20

On Wed, 4 Jun 2014, Mick wrote: >> Some of the variables (those with HU_FLAG_ABSENT) are apparently not stored >> on the UPS itself-- they are sent to the UPS when the shutdown command is >> executed. Sending the value starts the timer, in some cases, but I think >> the ups.delay.start value should be safe to send at the time when it is >> set. > > I see. So if

On Fri, 22 Jun 2018 13:38:14 +0200 Bernd Markgraf <bernd.markgraf at med.ovgu.de> wrote: > On Wed, 2018-06-20 at 14:20 +0100, Rowland Penny via samba wrote: > > On Wed, 20 Jun 2018 15:01:12 +0200 > > Bernd Markgraf <bernd.markgraf at med.ovgu.de> wrote: > > > I would like to see that behaviour on my machine too ;-) > > > > Then just do what I do,

On Wed, 20 Jun 2018 15:01:12 +0200 Bernd Markgraf <bernd.markgraf at med.ovgu.de> wrote: > > > > On the OS level everything works flawlessly (without using > > > winbind). > > > Login upon first try, kerberos ticket properly issued, uid/gid set > > > to the numbers provided from the LDAP (Samba DC) backend.  > > Well, yes it would work to allow