similar to: a slight bug of upsd?

Hi, all! Actually I have two questions for a same reason: I want to share my NUT to my LAN, or read UPS from remote device. /**************** firstly *****************/ I downloaded tcp-wrapper, but NUT could not detected it. Previously I successfully configured and make NUT into my embedded system. It worked and UPS is recognized. I downloaded tcp-wrapper (Ver 7.6, most files in the package

Hi, When I start upsd under normal conditions, I get this: -------------------------------------------------------------------------------- Network UPS Tools upsd 2.0.4 /etc/nut/upsd.conf is world readable Can't connect to UPS [tripplite] (tripplite_usb-auto): No such file or directory /etc/nut/upsd.users is world readable Synchronizing........ giving up

Hello all, I'm new to nut, i've donwloaded and installed without problem apparently nut 2.0.3 on a slackware 10.x (1 i think). /usr/local/ups/bin/upsdrvctl start seems to work correctly. but when i do: /usr/local/ups/sbin/upsd i've got: Network UPS Tools upsd 2.0.3 stat /usr/local/ups/etc/upsd.conf: Permission denied but upsd.conf is 0640 and set with root.ups as stated in some

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 Mar 21, 2014, at 1:39 PM, Schauer, Peter wrote: > 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

Hi, I have had a long standing problem with NUT talking to 110V MGE UPSs on FreeBSD, I was recently investigating again and noticed that upsd seems overly noisy, eg.. May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5 03:50:36 egbert upsd[96662]: Data for UPS [ups1] is stale - check driver May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5

The upsmon.conf has the option of setting RUN_AS_USER username Might it be possible to add a similar option to the upsd.conf file? I see the -u command-line option for both upsmon and upsd, however, upsd doesn't seem to carry that to the configuration file, as upsmon does. Thanks.

Hello, I am having trouble getting upsd to start. I am using the Debian NUT packages version 2.0.3 (current in Debian/sid). I am using the newhidups driver with an APC Back-UPS BR 800. The init.d script wasn't functioning, so I backtracked to running upsd manually and I get: foxstar:/etc/nut# upsd -u root Network UPS Tools upsd 2.0.3 Can't connect to UPS [foxstarups] (newhidups-auto):

Parsing bug was discussed here: <http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-September/006230.html> Parsing bug summary ------------------- working /etc/hosts.allow: upsd 127.0.0.1 [::1] : ALLOW broken in /etc/hosts.allow: upsd localhost : ALLOW It looks like upsd originally intended to match nut username with system username? This is not the case now. This causes

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

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

Hi all, Have a strange behaviour that I don't know how to debug. This is when I use the Eaton PW5125 ups. I have it connected And running in standby. Starting up the drivers (pw3105 and pw5125) and they run. Start up the upsd and can read info from both of them. The 3105 is supplying the computer and the 5125 have a dummy load. The 5125 is showing that it is off line. Now when I hit the on

Hello, I'm having problems when trying to execute an deep battery test. UPS Model: PowerWalker VI 1000. root at HP-Opreon:/# upscmd PowerWalker at localhost test.battery.start.deep Username (root): admin Password: Unexpected response from upsd: ERR ACCESS-DENIED /etc/hosts.allow: <code> # /etc/hosts.allow: list of hosts that are allowed to access the system. # See

Hello, I'm facing problems as I'm installing NUT to monitor a MGE Ellipse ASR600USBS on a FreeBSD 6.1 box. UPS is recognized as : ugen0: MGE UPS SYSTEMS ELLIPSE, rev 1.10/42.41, addr 2 I'm temporarily using root profile (devfs/devd scripts not modified atm). newhidups starts & runs fine (unplugging mains makes newhidups outputs lots of data when started with -DDDD flags)

On Jun 18, 2014, at 1:51 PM, Mike. <the.lists at mgm51.com> wrote: > The upsmon.conf has the option of setting RUN_AS_USER username > > Might it be possible to add a similar option to the upsd.conf file? > > I see the -u command-line option for both upsmon and upsd, however, > upsd doesn't seem to carry that to the configuration file, as upsmon > does.

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:

Windows 7 Pro x64 SP1 NUT 2.6.5-4 upsd is crashing when stopped and I think it has only started with the latest version. Nothing shows up in 5'D upsd output, the normal output just quits. Windows 7 event log output below. It's also crashing on XP, though I do have one XP system where it doesn't crash. One difference on WinXP is the upsd process gets stuck running and doesn't

I am running tests on my system and UPS, making sure that it is reliably able to come up, detect power loss, shutdown safely, and then come back up when the power returns. It does that MOST of the time. However, a significant part of the time, the system comes up, and then doesn't respond to loss of power. Doing some checking, I find that the reason is because upsd never started. Capturing

Hi, We are having a performance issue with UPSD. OUR ENVIRONMENT -------------------------- We are using a custom script on a SUN V240 server running Solaris 8. The script employs UPSC to interrogate UPSD. UPSD is configured (using upsdrvctl) to talk to two MGE Galaxy 3000 UPS's via the MGE-SNMP ups driver. Our problem is this. When the server runs the backup processes it becomes

On Wed, 16 Oct 2013 08:19:11 +0100 Chris Boot <bootc at bootc.net> wrote: > >> > I forgot to mention: by default, NUT listens on localhost. If > >> > you are using Linux, you could add a "-m owner --uid-owner" rule > >> > to iptables to only match the UID for the NUT system user. > > > > Thanks; if it listens on localhost by default,