similar to: howto force shutdown if nut-snmp Communications lost

On Sep 3, 2014, at 9:38 AM, Heiko L. <HL at fh-lausitz.de> wrote: > Howto force shutdown if nut-snmp Communications lost? > > My 1. suggestion was option DEADTIME, but seem to be information only. (s. below) DEADTIME expiration is a critical condition if the UPS is on battery when comms are lost, otherwise you are correct, it is only informative. What about a NOTIFYCMD script

Hallo I wanted to compile libvirtd on xen-4.2 but on [3] wrote: ...current version of libvirt is not compatible with xen 4.2... Which version that I can test? regards heiko -------------------------------------------------- - details 130305.xen.make.libvirtd #### var tmp=/tmp libvirtver="0.10.2" pkgs="libxml2-dev libdevmapper-dev" #### dl cd $tmp ## dl [2] wget

Hi, I have a Liebert UPS which I have connected to a FreeNAS Box. I had all sorts of issues making FreeNAS (FreeBSD based) talk to the UPS over USB. My solution seemed to be to buy a Raspberry Pi then connect it to the UPS (works fine), then make my NAS read the UPS status from the Pi over a TCP/IP connection. Convoluted I know, but it works well...for about a month, then it just loses

Hi, Sorry, I will keep the instructions in mind. I tried ./autogen.sh with --system but there was a version mismatch. I guess someone should write a patch for debian based system.  I tried to install libvirt 1.1.1 with Fedora and when I did make, I got the following error:  Making all in src make[2]: Entering directory `/home/peeyush/Downloads/libvirt-1.1.1/src'   GEN    

On Thu, 8 Jun 2017, Robbie van der Walle wrote: > After the first test and the NAS is restarted I had to change the > setting battery.charge.low again to 80? Does the NAS DSM reset battery.charge.low to 10 or is it internal to the UPS? You will have to experiment by disconnecting the UPS control lead from the NAS and connecting it (if possible) to the Mac. After setting to 80 and a

Hey, I have the problem that my timer daemon doesn't start. I checked my configuration more than two times and I don't find the failure. Maybe someone can help me and tell me where the failure could be. --- syslog --- May 13 21:50:34 s-monitor1 upsmon[1674]: UPS usv3 at localhost on battery May 13 21:50:34 s-monitor1 upssched[855]: Executing command: ONBATT May 13 21:50:34 s-monitor1

hello, i've got a problem with the notifycmd here is a part of my upsmon.conf : NOTIFYCMD /usr/local/ups/bin/nut_notify NOTIFYMSG ONLINE "UPS %s is getting line power" NOTIFYMSG ONBATT "UPS %s is on battery" NOTIFYMSG REPLBATT "The UPS %s battery is bad and needs to be replaced" NOTIFYMSG LOWBATT "UPS %s is being shutdown by the master" NOTIFYMSG FSD

On Feb 9, 2015, at 6:48 AM, PERE (yahoo.es) <pererivers at yahoo.es> wrote: > 0.028188 Can't set USB configuration: could not set config 1: Device or resource busy > 0.029246 detached kernel driver from USB device... > 0.030559 USB device [0001:0000] opened > 0.866216 read: (8 bytes) => 03 00 00 00 00 00 00 00 > 0.866413 reply[0] = 0x03

On Mon, 3 Apr 2017, Gene Heskett wrote: >> > Nut, IIRC, can do a periodic battery test by putting it offline, using > the battery, for a predetermined length of time, weekly, monthly etc, We definitely don't want that in this instance either! (Unless it is a dual PS server.) We want the ALARM that the nut driver is generating, and upsd is passing on - to be acted on in some

Ah! So I can detect the source UPS in the upssched.conf and pass it as a distinct event to the shell script. That sounds like an excellent approach. Thanks! GMH From: O'Shaughnessy, Mike [mailto:Mike.OShaughnessy at gd-ms.com] Sent: Tuesday, October 31, 2017 12:46 PM To: Garrett Michael Hayes <Garrett at VerbalImaging.com>; nut-upsuser at lists.alioth.debian.org Subject: RE: Email

Hi All, I'm using a recent post 2.6.1 build provided by Fred (executables have modified date of 9th August) I have configured upsmon.conf with :- NOTIFYCMD C:\NUT\etc\NotifyCmd.bat and :- NOTIFYFLAG ONLINE SYSLOG+EXEC NOTIFYFLAG ONBATT SYSLOG+EXEC NOTIFYFLAG LOWBATT SYSLOG+EXEC NOTIFYFLAG FSD SYSLOG+EXEC NOTIFYFLAG COMMOK SYSLOG+EXEC NOTIFYFLAG COMMBAD SYSLOG+EXEC

I've not been able to connect to my ups using NUT 2.7.4 or NUT 2.8.0. 2.7.4 was installed as a package, 2.8.O was compiled from source. I've messed with permissons, everything is root:root and has the approprate read/execute permissons. I've tried two differnt UPS(es) APC & CyperPower. I'm running PI OS (Raspbian) on a Raspberry Pi3 model B. The port 3493 is open (UFW). I can

Dear Chales, Thanks for your quick reply. I have Raspberry with last Kernel [Linux pi1 3.18.6+ #753 PREEMPT Sun Feb 8 14:47:22 GMT 2015 armv6l GNU/Linux] If <upsdrvctl>, <upsd> and <upsmon> are stopped <nutdrv_atcl_usb> Works well without any error as "Device or resource busy". If I run <upsc> command never receive any value from my ups <upsc ups at

Everything runs fine for several hours, then communication is lost and nut doesn't reestablish communication on its own. Running sudo upsdrvctl stop then sudo upsdrvctl start reestablishes communication. OS Version: Linux piaware 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux Nut Version: 2.7.2-4 Nut Installation Method: apt Device: CyberPower PR1500LCD Uses ? ? Generic

Hi, I'm using qemu+ssh://username at hostname/system as the remote URI. Libvirt seems to be communicating fine until some 2 minutes (we poll every 5 seconds) and then it throws up RPC error and many counters are wrong. But if I collect on localhost the counters seems to be coming fine. Test and testvm are guests on the local machine where as Win8 and Ubuntu* are remote URI's connected

Hi, - The device never re-connects to the system, i have to physically remove the USB plug and insert it again for the device to come back. - This does not happen when running the driver from the supplier. (java process) - When i poll every 60s it works for about 3 days, anything lower or higher causes it to disconnect faster - The big log i sent is not the output of the driver? if not how can i

Hello list. I’m using samba4 authorization with debian 8 without any problems. But in debian 9 very same config causes problems - unable to change GID. Here is my smb.conf: [global] netbios name = testvm security = ADS workgroup = WRKGRP realm = EXAMPLE.COM password server = 172.24.0.253 wins server = 172.24.0.253 wins proxy = no

Hello guys Yesterday i started do configure my Mustek Powermust650 with nut using the megatec_usb driver. Everything works fine except for the mailing when something happens. My upsmon looks like this: MONITOR powermust650 at localhost 1 local controller master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /root/upsmailer POLLFREQ 10 POLLFREQALERT 5 HOSTSYNC 15

Background: ---------- I'm trying to debug a two-node pacemaker/corosync cluster where I want to be able to do live migration of KVM/qemu VMs. Storage is backed via dual-primary DRBD (yes, fencing is in place). When moving the VM between nodes via 'pcs resource move RES NODENAME', the live migration fails although pacemaker will shut down the VM and restart it on the other node.

Hello, After searching the archives, I''ve found only two messages regarding this case, but there were no solution. I have a similar problem, so I try to ask here. I have twi HFC chipset ISDN cards in my pc: 0000:00:0d.0 Network controller: Cologne Chip Designs GmbH ISDN network controller [HFC-PCI] (rev 02) Subsystem: Cologne Chip Designs GmbH ISDN Board Flags: bus