similar to: unclear about expected shutdown behavior

> On Dec 24, 2016, at 3:14 AM, Roger Price <roger at rogerprice.org> wrote: > > On Sat, 24 Dec 2016, Spike wrote: > >> ... from reading the docs it seems the UPS should power off, is that the case? > > Yes, The UPS should be sent a "delayed shutdown" command, upsdrvctl shutdown, to tell it to shut down _after_ the box. The amount of the delay can be set

On Sat, 24 Dec 2016, Spike wrote: > ... from reading the docs it seems the UPS should power off, is that the > case? Yes, The UPS should be sent a "delayed shutdown" command, upsdrvctl shutdown, to tell it to shut down _after_ the box. The amount of the delay can be set in ups.conf. The UPS delayed shutdown turns off the output sockets on the UPS. On some UPS's this

Roger, So I'm pursuing the strategy of issuing the "upsdrvctl shutdown" command script when the OS (Porteus, in this case) is shutting down. I so far can't get it to do it, but I'm sure I'll overcome it, but I realized something else might be a problem. Won't that script execute every time Linux is shutting down, including rebooting? So, if I choose to reboot my

Hi Everyone, I recently bought a Tripp-Lite SMART1500LCD for my Linux Mint 19.3 machine, connected via a USB cable. I installed Nut 2.7.4 from the Mint package repository via sudo apt update && sudo apt install nut. Everything works great: NUT issues low battery warning when it reaches the set low battery point and then issues shutdown commands...computer shuts down..then the UPS shuts

Dear all, maybe not strictly a NUT question but I can't imagine a better place to ask, hope that's ok. last night we had what looked like a power spike and 3 machines plugged into 2 Eaton UPS went down instantly. I heard the click the UPS makes when it shuts the load on the ports and then shuts itself down (ie same thing if I simulate with upsmon -fsd). The machines instantly came back,

> Have you checked the BIOS option "Power on when AC Returns"? Yes, and I have set it to "always on" as opposed to "always off" or "last state". > Does the UPS unit perform a delayed power off some time after the box shuts > down? I have no idea. How would I find out? -------------- next part -------------- An HTML attachment was scrubbed...

Arno, thanks for taking the time to write back and no worries about lag, we're all busy and I'm grateful there is a community to interact with to begin with. You're right - the problem went away once I actually configured nut. I guess I was too "cautious" and when I saw the errors I thought something was wrong with the usb connection and didn't try to get nut going

2017-03-29 12:32 GMT+02:00 Arnaud Quette <arnaud.quette at gmail.com>: > > > 2017-03-29 5:49 GMT+02:00 Spike <spike at drba.org>: > (...) > >> Is this really the desired behavior? I can certainly work with it, but it >> seems it'd be nice if it could work with dns resolution (at least client >> side, the LISTEN statement I guess it's ok), but

Hi, I have a eaton 1500 that connects to an Ubuntu Xenial box via USB. The UPS works, however exactly *ever 5 minutes* it disconnects and reconnects and I see this in syslog: Mar 10 19:50:32 spike kernel: usb 4-5: USB disconnect, device number 103 Mar 10 19:50:33 spike kernel: usb 4-5: new low-speed USB device number 104 using ohci-pci Mar 10 19:50:34 spike kernel: usb 4-5: New USB device found,

On Thu, 8 Jun 2017, Robbie van der Walle wrote: > The "upsrw" command contacts upsd, so it sounds like you should be able to add a user to upsd.users on the NAS, and then run something like > this on the Mac: > > ??upsrw -s battery.charge.low=80 -u upsmaster -s sekret UPS at synology > > Per?http://networkupstools.org/docs/man/upsd.users.html?,

> > 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 itself down, thereby allowing the server enough time to safely > > shut itself down as well? > > Yes. Very good, thank you. > The command is "upsdrvctl shutdown". That's what I thought, but I

Hi, I've been setting up a few Eatons 1500 USB in master/slave mode and run into what I'm thinking is a hostname resolution problem. Basically, to avoid hardcoding ips, I'd love to be able to add a LISTEN on the lan's ip which has hostname, let's say, server1.local . If I set up upsd.conf such as LISTEN server1.local 3493 what I end up with is upsd listening on 127.0.0.1 .

I am having trouble with the rfImpute function in the randomForest package. Here is a sample... clunk.roughfix<-na.roughfix(clunk) > > clunk.impute<-rfImpute(CONVERT~.,data=clunk) ntree OOB 1 2 300: 26.80% 3.83% 85.37% ntree OOB 1 2 300: 18.56% 5.74% 51.22% Error in randomForest.default(xf, y, ntree = ntree, ..., do.trace = ntree, : NA not

Hi I am thinking about using the existing NUT software to tell the slave servers to shutdown if the temperature in the server room becomes too high. I was thinking of monitoring the temperature on the master NUT server and then just letting the slave clients shut down. But the slaves (and master server) needs to do a complete power off even though the UPS's does get 220v power all the

Is anyone in the leadership of the R-project going to contact the New York Times and clarify that the article gave remarkably short shrift to the people who designed the user interface for R, to a large extent AT&T researchers from an earlier generation? It would be the appropriate thing to do. The R team did not develop the user interface for R, the designers of the S programming language

thank you Arno, I'm with Manuel on the "IP address or hostname", maybe I didn't understand your previous explanation, but to me there's still a bigger issue/unclear behavior. Let's say I just installed ubuntu on a machine with hostname server1 and ip 192.168.0.1 . In /etc/hosts I end up with two lines (per

>> last night we had what looked like a power spike and 3 machines plugged >> into 2 Eaton UPS went down instantly. I heard the click the UPS makes when >> it shuts the load on the ports and then shuts itself down (ie same thing if >> I simulate with upsmon -fsd). The machines instantly came back, there was no >> actual downtime, and the machine next to them which is

Roger, Following your guide, it now works great, shutting down the UPS after the system has shutdown. I went with the bash script method. I have noticed, however, that the command to the UPS to do the delayed shutdown comes RIGHT as openSUSE is shutting down. While that is a good thing as far as timing and the potential race is concerned, I have seen it once where the UPS received the command

I've been wrasslin' with a problem on a CentOS 7 host that I'm using as my main NUT server. When the battery gets low while the server is shutting down it is supposed to signal the UPS to shut down as well. This is clear, well documented, and The Right and True Thing to Do<tm>. However, the default scripts provided in the EPEL RPM aren't actually doing it. The host halts as

Hello again. After an hour of Googling and just not "getting" it, I figured I'd call upon the list once more... I am starting upsd, upsmon, etc in my FreeBSD's /etc/rc.local, because it's easy. BUT... rc.shutdown seems kill off all those processes prior to excuting my upsdrvctl shutdown command, thereby preventing any ups communications and yup, the power don't get