similar to: Patch: upssched puts UPS name in the command line

Dear Arnaud, Now I started to write a driver that simulates continous power breaks. (E.g. in every 30 minutes.) This could be used for testing of setup of client upsmons. I have to simulate a behaviour of a real UPS. The physical model contains an extra attribute: the charging current that needed to compute recharge time and actual battery charge during the recharge process. Can we call this

Dear Arnaud, Now I started to write a driver that simulates continous power breaks. (E.g. in every 30 minutes.) This could be used for testing of setup of client upsmons. I have to simulate a behaviour of a real UPS. The physical model contains an extra attribute: the charging current that needed to compute recharge time and actual battery charge during the recharge process. Can we call this

Hi, I've stumbled over a race condition in upssched when using 3 or more UPSes in combination with START-TIMER/CANCEL-TIMER. I have a solution that works but is ugly, so I'm going to describe the bug here in the hope somebody can come up with a better solution. The problem is in upssched.c:629 check_parent() (see https://github.com/networkupstools/nut/blob/master/clients/upssched.c ).

What is the sign of battery.current value? I wonder if the negative number means charging or discharging. Gabor

Dear folks, I'm thinking about writing a multithreaded driver. I wonder if library routines (like dstate_*) are thread-safe? Regards Gabor

I wonder if ups.status: OB LB OFF is valid? Or OB and OFF are mutually exclusive flags? Regards Gabor

Dear folks, strace shows that snmp-ups driver writes to stderr: [pid 21825] write(2, "No log handling enabled - turnin"..., 52) = 52 | 00000 4e 6f 20 6c 6f 67 20 68 61 6e 64 6c 69 6e 67 20 No log h andling | | 00010 65 6e 61 62 6c 65 64 20 2d 20 74 75 72 6e 69 6e enabled - turnin | | 00020 67 20 6f 6e 20 73 74 64 65 72 72 20 6c 6f 67 67 g on std err logg | | 00030 69 6e

Dear folks, According to mge-mib.c (NUT 2.6.2) LB condition is gained from variable .1.3.6.1.4.1.705.1.5.14.0 (i.e. upsmgBatteryLowBattery.0). The test device of me does not set this variable to yes(1) even if runtime drops below the preconfigured limit. I complained about this at Schneider Electric. They replied that low battery status is indicated by .1.3.6.1.4.1.705.1.5.14.0

Hi Arnaud, I played a bit with dummy driver in repeater mode. It is the concept what I need. Unfortunately I found that if connection to another upsd gets broken the driver does not try to repair it. Gabor

Roger, I did and it didnt work. Hence why I was trying to run just the shell script manually. I am not sure if this works though with the timer defined in it? Cheers, James Date: Mon, 27 Apr 2015 15:03:44 +0200 From: roger at rogerprice.org To: nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] upssched setup On Mon, 27 Apr 2015, James Hammond wrote: > I am unable to get

Hi Charles, Running upsdrvctl -D start on the host with all three configured to SNMPv3 kicks out 56 different "unhandled ASN 0x81 from ..." lines on all three but importantly they all start up and keep running. I'm starting to suspect the startup is taking so long that systemd is timing out and killing it. time -p reports real time of 133.27. I'm not a fan of systemd but

Hi, I'm having problems to configure upssched in order to notify me only when the disconnection exceeds the 30 seconds. Now, I'm getting a mail if it is disconnected just for a second, or even worse, when I got low tension. So, mail notifications are well configured, I guess... I think the problem is in upssched. I'm new to this, so it could be a stupid thing that I'm missing...

ut 10. 3. 2020 o 16:34 Roger Price <roger at rogerprice.org> napísal(a): > > On Tue, 10 Mar 2020, Radoslav Chovan wrote: > > > I have problem with upssched on windows. Upssched is not executed. I > > have 2 scripts, 1 for notification in upsmon and second for scheduling > > in upssched. Monitoring is working fine, script write to log. I'm > > using binary

Hi Roger, I get: Apr 27 20:50:05 unifi upsmon[1022]: UPS ups on batteryApr 27 20:50:05 unifi upssched[2688]: Timer daemon startedApr 27 20:50:06 unifi upssched[2688]: New timer: onbatt (20 seconds)Apr 27 20:50:26 unifi upssched[2688]: Event: onbattApr 27 20:50:26 unifi upssched[2688]: exec_cmd(/sbin/upssched-cmd.sh onbatt) returned 126Apr 27 20:50:41 unifi upssched[2688]: Timer queue empty,

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

Hi, i am running nut-2.0.0-5 on Fedora core 3. I have the following Problem: In my upssched.conf i have set the Following Parameter: CMDSCRIPT /usr/local/guzman/sbin/upssched-cmd ... AT COMMBAD * START-TIMER upsgone 10 AT COMMOK * CANCEL-TIMER upsgone ... Now if I pull the serial Plug, in my log i see the following error: Event: upsgone Execute command failure:

Hi, I am unable to get upssched working correctly as my UPS calls low battery too late and there is no way to change it. I am running Nut 2.7.3 on Ubuntu 14.04 I have made this script, called /sbin/upssched-cmd.sh #!/bin/sh case $1 in onbatt) /sbin/upsmon -c fsd;; *) echo "shutdown implemented";; esac I am trying to run the script manually to break down my issues. All that

Hello, I'm using nut with my MG Ellipse on serial port. No problem since one year. Two days ago, I wanted to add a phone alert through my asterisk box when power is down. Since then, upssched doesn't make his job anymore. here is the "syslog" I get when the power cord is unplugged : > > May 9 11:39:34 serveur upsmon[6411]: UPS ellipse@localhost on battery > May 9

Hello, I am currently building a new server using debian amd64. Therefore I need to use my UPS EATON Evolution 1550 on it, using usbhid-ups driver. I installed nut with apt (version 2.4.3-1.1squeeze1) on debian 2.6.32-5 amd64. I can currently use nut with the drivers, upsc and upsmon: my UPS is detected and works. Actually everything works except upssched: I can shut down the server using

Hi everyone, Here I am with my second attempt to persuade upssched to do things; for some reasons it just won't! Or if it runs, it never runs the script. OK, the story first: 2.0.3 (conveniently comes as RPMs by default on FC6) running on FC6; APC Smart-UPS 750 via serial connection all working fine. Here are the main files: /etc/sysconfig/ups SERVER=yes MODEL=apcsmart DEVICE=/dev/ttyS0