similar to: upsmon cannot start on windows

Hi, I just installed NUT-Installer-2.6.5-6.msi on Windows 2012 server, set config as netclient and start windows service. I found service is running but monitoring is not working. After some investigation I discovered that I had to copy libgcc_s_dw2-1.dll from c:\Program Files (x86)\NUT\bin\ to c:\Program Files (x86)\NUT\sbin\ I suppose it is a bug and should be corrected with next windows

Thank you for this. I appreciate your detective work as it saved my day to get it working! For anyone else finding this post you also need to set the SHUTDOWNCMD line in upsmon.conf to: SHUTDOWNCMD "shutdown /s /f /t 10" to force shutdown after 10 seconds using windows commands. The software ships with the linux shutdown configured which is clearly inappropriate. I couldnt find this

On Sun, Apr 17, 2016 at 3:56 PM, Denis Serov <intrudo at outlook.com> wrote: > Hello! > > I performed lightweight review of Windows port source code (Windows-v2.6.5-7 branch). I have some ideas I would like to share with NUT community. > > First of all, Frederic did great job to port NUT sources to Windows platform and we have the path in dark forest. Unfortunately, the port

On Saturday, 1 September 2018 17:50:13 BST Charles Lepple wrote: > I don’t have the code in front of me at the moment, but my guess is that the > config parser stopped parsing at the “#” character. I suspected a rogue character was being interpreted and used `backticks`, 'single quotes' and then "double quotes", but all failed. I ended up removing the offending #

Hi All, I have noticed these messages in my logs: ========================================= Sep 01 13:14:22 osmc upsd[1450]: listening on 127.0.0.1 port 3493 Sep 01 13:14:22 osmc upsd[1450]: listening on ::1 port 3493 Sep 01 13:14:22 osmc upsd[1450]: listening on 127.0.0.1 port 3493 Sep 01 13:14:22 osmc upsd[1450]: listening on ::1 port 3493 Sep 01 13:14:22 osmc upsd[1450]: Connected to UPS

Hi Larry, [please use reply-all to include the list - the NUT lists do not add a reply-to header.] On Oct 21, 2015, at 3:23 PM, Larry Baker <baker at usgs.gov> wrote: > > I use the NUT RPM package for CentOS 6.7, which is version 2.6.5-2. I admit I am not too familiar with the RH/CentOS family these days. Is there a CentOS site for keeping tabs on the NUT RPMs, or is it sufficient

Hi, I have UPS Socomec ITYS 3000 with Netvision card. OS is Centos 6.5 64-bit. NUT installed with yum,. nut-2.6.5-2.el6.x86_64 nut-client-2.6.5-2.el6.x86_64 Why is ups.status empty? Here is upsc output: upsc myups at localhost battery.charge: 97.00 battery.runtime: -60.00 battery.voltage: -0.10 device.mfr: Net Vision v6.01 (SN 0101414290) device.model: ITYS 3 kVA device.serial: 3I14450043

On Sep 1, 2018, at 2:44 PM, Mick wrote: > > On Saturday, 1 September 2018 17:50:13 BST Charles Lepple wrote: >> I don’t have the code in front of me at the moment, but my guess is that the >> config parser stopped parsing at the “#” character. > > I suspected a rogue character was being interpreted and used `backticks`, > 'single quotes' and then "double

Windows 7 Pro x64 NUT 2.6.5-4 upsmon, when there is a problem, spams the event log every 5 seconds. Poll interval is 5 seconds also. I have witnessed the below messages filling up the event log. upsmon - UPS [ups at localhost]: connect failed: Connection failure: Unknown error. upsmon - Poll UPS [ups at localhost] failed - Data stale. I've already reported earlier how I've been

Is nobody using pm-suspend or pm-hibernate with upsmon? Or any other shutdown command besides the default one? Thanks, Jan On 22.4.2016 4:43, holomek at seznam.cz wrote: > Hi, > > While using pm-suspend script as the SHUTDOWNCMD, upsmon does not > correctly handle its returned values and leaves UPS in the > "ups.status: FSD OL CHRG" state forever. > > This is

Hi, While using pm-suspend script as the SHUTDOWNCMD, upsmon does not correctly handle its returned values and leaves UPS in the "ups.status: FSD OL CHRG" state forever. This is with upsmon 2.6.5 from official Fedora Project packager. Box running Centos 6.7. Initially, upsmon would not execute pm-suspend at all. Creation of a custom SELinux module or changing to Permissive mode

I don’t have the code in front of me at the moment, but my guess is that the config parser stopped parsing at the “#” character. This ends up with a shorter password in upside.users, but a truncated MONITOR line in upsmon.conf. I forget the precedence, but either “\#”, or double quotes around the password should fix it. > On Sep 1, 2018, at 10:09 AM, Mick <michaelkintzios at gmail.com>

I use the NUT RPM package for CentOS 6.7, which is version 2.6.5-2. I am testing implementation of NUT features with APC and Tripp-Lite USB UPS interfaces. Things are going reasonably well. However, I'm seeing many more messages than I would like in /var/log/messages when I boot the system without the UPS connected (testing a failure scenario). I have configured NOCOMMWARNTIME 3600, which

???? ?? *Ubuntu 12.04 LTS ? ? ??? * NUT 2.6.5 ? ? ??? * From Ubuntu terminal ---> sudo apt-get install nut ? ? ??? * Openups from mini-box.com ? ? ??? * - Intelligent UPS, USB interface ? ? - SMBUS slave and I2C master ? ? - Input 6-34V ? ? - Programable output 6-24V ? ? - Default output is 12V ? ? - Input/Output current 6A/10A peak ? ? - Charge between 6-30V, 3A ? ? - Voltage and current

I use the NUT RPM package for CentOS 6.7, which is version 2.6.5-2. I am testing implementation of NUT features with APC and Tripp-Lite USB UPS interfaces. Things are going reasonably well. However, I'm seeing many more messages than I would like in /var/log/messages when I boot the system without the UPS connected. I have configured NOCOMMWARNTIME 3600, which takes care to only broadcast

Hi, I had named a module as "global" and it appears not to be recognized. It appears a section [global] path=xxx etc. is interpreted as global parameters and not as a module named global. Is that the expected behaviour? Any pointers as to what names are allowed for modules will be appreciated. Thanks, Selva -------------- next part -------------- An HTML attachment was scrubbed...

> I suspect you will want the newer version for production (there was some > issue regarding the popups when certain events happen), but let's get this > version working first before changing another variable. Appreciate that. Agreed. > For reference, I think the source code to NUT.exe is here: > https://github.com/networkupstools/nut/blob/Windows-v2.6.5- >

Hello! I performed lightweight review of Windows port source code (Windows-v2.6.5-7 branch). I have some ideas I would like to share with NUT community. First of all, Frederic did great job to port NUT sources to Windows platform and we have the path in dark forest. Unfortunately, the port looks like experimental. I think that the next major iteration is required. Here are many words, sorry

On Nov 8, 2014, at 6:12 PM, Selva Nair <selva.nair at gmail.com> wrote: > Everything works rather well, except that the cgi-interface does not report input/output voltages and load for the C 1500 unit. > upsc also reports these values only for model 1000, not for 1500. Battery charge is and runtime are reported. For the 1000, do the values match this page?

Using the HOWTO in http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ I installed nut on an Ubuntu Edgy LAMP Server with an Eaton Powerware 5110 attached to it via usb. But nut fails to start properly (see the error message "Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon" below). It then complains about communication with the UPS being lost ("UPS