search for: upssh

Hi Manuel, thank you for pointing this. I know about upsshed but I have no idea how to let dependable server to discover that another server was shut down. Any examples of such scripts? чт, 17 сент. 2020 г. в 21:00, Manuel Wolfshant <wolfy at nobugconsulting.ro>: > On September 17, 2020 6:09:18 PM GMT+03:00, Kirill Nikonorov < > knikonor a...

...FYFLAG FSD SYSLOG+WALL NOTIFYFLAG COMMOK SYSLOG+WALL NOTIFYFLAG COMMBAD SYSLOG+WALL+EXEC NOTIFYFLAG SHUTDOWN SYSLOG+WALL NOTIFYFLAG REPLBATT SYSLOG+WALL+EXEC NOTIFYFLAG NOCOMM SYSLOG+WALL+EXEC NOTIFYFLAG NOPARENT SYSLOG+WALL RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 upsshed.conf CMDSCRIPT /etc/nut/upssched-cmd PIPEFN /var/run/nut/upssched.pipe LOCKFN /var/run/nut/upssched.lock AT ONBATT ippon at localhost START-TIMER fsd 30 #for testing AT ONLINE ippon at localhost CANCEL-TIMER fsd upsshed-cmd #!/bin/sh MSG="The UPS is running on battery about 2 minutes, doing...

Hi all I have most of the NUT system up and running. I?m in the process of writing the script to send email notifications for certain events. This is my upsshed-cmd file so far: # EC130 Commands ec130onbatt) echo "EC130 UPS has been on Battery for more then 10 seconds" \ | mailx -r "ups at fit.edu" -s"EC130 on battery" tarbeite at fit.edu ;; ec130combad)...

...ot;$UPS, $CHMSG - On line power - power supply had been restored." ;; onbatt) MSG="$UPS, $CHMSG - On battery - power failure - save your work!" ;; lowbatt) MSG="$UPS, $CHMSG - Battery is low - shutdown now!" ;; beeperoff) logger -i -t upsshed-cmd "Turning off Beeper" STATUS=`upsc ${UPS} ups.beeper.status 2>&1 | grep -v '^Init SSL'` if [[ "${STATUS}" == "enabled" ]] ; then upscmd -u ${UPS_USERNAME} -p ${UPS_PASSWORD} ${UPS} beeper.toggl...

...works fine for several month now. Due to the fact that different devices, connected to different UPS are generating a different load, the batteries of each UPS are discharged with a different speed. I now want to react on the events of each of the UPS separately by creating dedicated entries in the upsshed.conf file. As far as I understood that should be possible without greater problems except for one thing - the forced shutdown. The command "upsmon -c fsd" forces all UPS to shutdown at the same time. Now I wonder why it isn't possible to send a forced shutdown command to a specific...

...UPS, $CHMSG - On line power - power supply had been restored." ;; onbatt) MSG="$UPS, $CHMSG - On battery - power failure - save your work!" ;; lowbatt) MSG="$UPS, $CHMSG - Battery is low - shutdown now!" ;; beeperoff) logger -i -t upsshed-cmd "Turning off Beeper" STATUS=`upsc ${UPS} ups.beeper.status 2>&1 | grep -v '^Init SSL'` if [[ "${STATUS}" == "enabled" ]] ; then upscmd -u ${UPS_USERNAME} -p ${UPS_PASSWORD} ${UPS} beeper.to...

...UPS, $CHMSG - On line power - power supply had been restored." ;; onbatt) MSG="$UPS, $CHMSG - On battery - power failure - save your work!" ;; lowbatt) MSG="$UPS, $CHMSG - Battery is low - shutdown now!" ;; beeperoff) logger -i -t upsshed-cmd "Turning off Beeper" STATUS=`upsc ${UPS} ups.beeper.status 2>&1 | grep -v '^Init SSL'` if [[ "${STATUS}" == "enabled" ]] ; then upscmd -u ${UPS_USERNAME} -p ${UPS_PASSWORD} ${UPS} beeper.to...

...;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 is actually unplugged and plugged back in. It happens on two different installation. See attached screenshot and configuration. Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists...

Hello to All! It might be not exactly NUT question but implementation. I have a rack with one UPS and several servers getting power from this device. One server is a master and other are slaves. All systems are running Debian 4.15.3 kernel and APC UPS. Everything works fine but what I need is to make an order for shutting down servers as they have different roles. Is it possible to configure SQL

Hi, Great work Jim! I?m glad you could reproduce the problem and found a potential culprit. Just for my own interest I restored upsshed from my backups (version 2.7.4-13) and it seems to running ok, so no big runtime changes regarding that with Debian 12. It is not hogging CPU. From the daemon log the heartbeat seems to be working ok. Only difference between the old logs (pre Debian 12 update) is the there is this line (Network U...

Hi, Great work Jim! I?m glad you could reproduce the problem and found a potential culprit. Just for my own interest I restored upsshed from my backups (version 2.7.4-13) and it seems to running ok, so no big runtime changes regarding that with Debian 12. It is not hogging CPU. From the daemon log the heartbeat seems to be working ok. Only difference between the old logs (pre Debian 12 update) is the there is this line (Network U...

...ot 15270 Jun 7 15:58 /etc/nut//upsmon.conf* -rwxr-xr-x 1 root root 2252 Jun 9 15:25 /etc/nut//upssched-cmd* -rwxr-xr-x 1 root root 2155 Jun 7 15:24 /etc/nut//upssched-cmd.bak* -rwxr-xr-x 1 root root 4662 Jun 8 20:48 /etc/nut//upssched.conf* -rw-r--r-- 1 root root 4593 Jun 7 12:52 /etc/nut//upsshed.conf.bak ########### Custom NOTIFYCMD scheduler /etc/nut/upssched-cmd ########### logger -t upsched-cmd: "upsched-cmd running" UPS="ups at localhost" STATUS=$( upsc $UPS ups.status) CHARGE=$( upsc $UPS battery.charge) CHMSG="[$STATUS] : $CHARGE%" case $1 in...

After launching the command several times, with debug (posted by new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT

After launching the command several times, with debug (posted by new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT