similar to: Remote Monitoring From Web

Attempting to install the SNMP driver on Enterprise SuSE 10.0. The version of NUT is 2.6.0. To begin with, I installed the net-snmp and net-snmp-devel packages, using YAST. If I do this command: net-snmp-config --version --base-cflags --libs The result is: 5.3.0.1 -DINET6 -O2 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -g \ -fno-strict-aliasing -fstack-protector-all -Dlinux \

Does v4.13 fix your issues? v4.10 also included significant rework related to DP-MST, and I wouldn't be surprised if it fixed a few DP issues along the way. (Also, please don't drop the list from your replies.) On Mon, Sep 4, 2017 at 9:30 AM, Marko Schuetz-Schmuck <MarkoSchuetz at web.de> wrote: > I'm running 4.9.43-1-MANJARO > > Ilia Mirkin <imirkin at

On 12/17/2013 10:43 AM, David C. Rankin wrote: > Huh? Why the : in Servname? So I just hardwired it passing the port "Servname" > as "3493" (could have just used "nut" from /etc/services): Sheepishly looking for a place to hide.... Yes there was a ':' there all right. Seems I was hit by a vi error: [12:04 phoinix:/etc/ups] # grep 3493 *.conf

So....seems so better... Each time I rebbot, I miss the /var/run/nut folder... root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) Can't chdir to /var/run/nut: No such file or directory Driver failed to start (exit status=1) root at artu:~# upsd Network UPS Tools upsd 2.7.2 fopen

O.S. Ubuntu 10.10, Maverick Meerkat 32 bit. NUT 2.4.3-1ubuntu5, package installed Belkin F6C1500-TW-RK I am having trouble starting uspd whenever I add a client from my lan to uspd.conf: LISTEN 127.0.0.1 3493 LISTEN 192.168.36.106 3493 naknight at nak-server:~$ sudo upsd -DDDD Network UPS Tools upsd 2.4.3 0.000000 listen_add: added 127.0.0.1:3493 0.000093 listen_add:

$ sudo /usr/sbin/upsd -DDDD Network UPS Tools upsd 2.4.3 0.000000 listen_add: added ::1:3493 0.000084 listen_add: added 127.0.0.1:3493 0.000102 setuptcp: try to bind to 127.0.0.1 port 3493 0.000185 listening on 127.0.0.1 port 3493 0.000204 setuptcp: try to bind to ::1 port 3493 0.001328 setuptcp: socket: Address family not supported by protocol 0.001381

Bonjour ? tous, Je n'arrive pas a faire marcher NUT avec HomeAssistant. Cela fait des mois que je suis la-dessus, mais sans succ?s ! Je ne vois plus quoi faire ! Help ! * Ubuntu 23.10 * NUT version = 2.7.4-14ubuntu2 * NUT installation method: Package * exact device name and related information : Riello IDG800 Voici les commandes que je tape sur le PC connect?

On 12/03/2016 10:08 AM, Charles Lepple wrote: >> On Dec 3, 2016, at 11:01 AM, Jack McGee <jack at greendesk.net> wrote: >> >> I did restart those services, no change. >> > $ ps auxww|grep [/]nut > root 13074 0.0 0.0 37844 2628 ? Ss 08:42 0:00 /lib/nut/upsmon > nut 13076 0.0 0.0 45632 5148 ? S 08:42 0:00 /lib/nut/upsmon

I have a Dell 500w UPS and it works great with Ubuntu 12.04 LTS and Network UPS tools 2.6.3 via usb. This powers a standalone server for the purposes of clean shutdowns. This was installed using "sudo apt-get install nut" and there are no issues with the Server > nut > ups chain. I am using the usbhid-ups driver and haven't had any issues. I am trying to also add an NAS to the

On 12/16/2013 09:23 PM, Charles Lepple wrote: > Not sure - I didn't write the getaddrinfo() code in upsd, but it seemed to > follow all of the recommendations on how to use that function. So if there is > a way to fix it in the NUT code, I am not aware of it (and would appreciate > any updates if that turns out to be the case). > > The odd part is that it looks like you went

NUT recently stopped working on my debian. I'm not sure which upgrade broke it. ups.conf: [mustek] driver = megatec port = /dev/ttyS0 desc = "mustek ups" # upsd -DDDD Network UPS Tools upsd 2.4.1 listen_add: added ::1:3493 listen_add: added 127.0.0.1:3493 setuptcp: try to bind to 127.0.0.1 port 3493 listening on 127.0.0.1 port 3493 setuptcp: try to bind

Hello, I am trying to get nut running on a Windows 2012 R2 server (x64). I am using the MSI release of 2.6.5-3. The attached UPS is an APC xs1500 (model bx1500g). The connection is an RJ45 to USB cable. Here is my ups.conf: [xs1500] driver = usbhid-ups port = auto desc = "APC Back-UPS xs1500" The problem I am encountering is upsd crashing with an 'Out of memory' error. I can

Hi Charles, Thanks for your response. No, I only put 192.168.1.64 as an extra option as I want to allow Slave access from another computer. Otherwise, access will normally only be from localhost. There is only one network interface on this machine. I will try it out with "LISTEN 0.0.0.0 3493" and see what happens. I must confess I usually run without a firewall as I'm only running a

Hello, I have a Raspberry Pi model B running Raspbian Stretch. I have installed version 2.7.4-5 of nut from the raspbian repos. I have a CyberPower 1500PFCLCD UPS. When I reboot the Pi, the nut-server service fails to start. root at nut:~# service nut-server status ? nut-server.service - Network UPS Tools - power devices information server Loaded: loaded

hi, I recently upgraded my Debian Lenny system to Squeeze, and have been happily running nut as a MODE=standalone system talking to my Cyberpower 1500 avr lcd via the usbhid-ups driver for a couple of weeks or so. No problems. Now I'm trying to hang another machine off the same ups as a slave, and it isn't working. The problem I'm getting is best illustrated by what

On Jan 24, 2015, at 12:45 AM, Ryan Sizemore <ryan.sizemore at gmail.com> wrote: > Hello, > > I am trying to get nut running on a Windows 2012 R2 server (x64). I am using the MSI release of 2.6.5-3. I am not sure why they are not listed on the main download page, but there are actually three Windows MSI releases after that: http://www.networkupstools.org/package/windows/ I

On 12/03/2016 10:35 AM, Charles Lepple wrote: > On Dec 3, 2016, at 11:16 AM, Jack McGee <jack at greendesk.net> wrote: >> Dec 3 08:38:16 amethi upsd[18234]: not listening on ::1 port 3493 >> Dec 3 08:38:16 amethi upsd[18234]: listening on 127.0.0.1 port 3493 >> Dec 3 08:38:16 amethi upsd[18234]: no listening interface available > I can't say I fully understand

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 all, sorry for this message, but maybe I am the most dumb user in here, so, please accept my appologies asking novice questions. I have tried 6 searched for more than 4 hours now, read all html-man files I could think need to be read and also the major one, but I did not manage to get the NUT to successfully run on my Vista machine. (it runs, but I cannot use it ... see later). I am

On Nov 9, 2014, at 3:48 PM, Steve Read <sd_read at hotmail.com> wrote: > I would like to verify my understanding keeping in mind I have a one master and one slave computer. > > When the master gets the low batt/noAC signal it initiates a broadcast packet(s) on port 3493. > > 1) Is this correct? No, the slave computer's upsmon process connects to the master (via TCP, so