similar to: [CVE-2012-2944] NUT vulnerability: upsd can be remotely crashed

2009/5/16 Arnaud Quette <aquette.dev at gmail.com> > > > 2009/5/7 Daniel O'Connor <doconnor at gsoft.com.au> > >> On Wed, 6 May 2009, Arnaud Quette wrote: >> > I think I've found something, but I would need an upsd debug output >> > (level 3) to see what going on the state socket. >> >> I've attached a log for you. >>

2017-03-29 5:49 GMT+02:00 Spike <spike at drba.org>: > Hi, > Hi again Spike ;) I've been setting up a few Eatons 1500 USB in master/slave mode and run > into what I'm thinking is a hostname resolution problem. > > Basically, to avoid hardcoding ips, I'd love to be able to add a LISTEN on > the lan's ip which has hostname, let's say, server1.local .

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

> Feature Requests item #310492, was opened at 07/01/2008 09:57 > Status: Open > Priority: 3 > Submitted By: Arnaud Quette (aquette) > Assigned to: Nobody (None) > Summary: Allow to specify hostnames in ACL (upsd.conf) > Category: None > Group: None > > > Initial Comment: > allow a new ACL form: > ACL hostname/mask > > example: > ACL localhost

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

2007/2/19, Glen Ogilvie <nelg@linuxsolutions.co.nz>: > Hi, > > I have a Fenton Powerpal L660, when I try and configure nut with either the > metatec or fentonups driver, and start upsd, the UPS instantly turns itself > off. > > It used to work, until I changed my motherboard and CPU, which means it has > a different bios and serial port setup. > > This is

2007/2/19, Glen Ogilvie <nelg@linuxsolutions.co.nz>: > Hi, > > I have a Fenton Powerpal L660, when I try and configure nut with either the > metatec or fentonups driver, and start upsd, the UPS instantly turns itself > off. > > It used to work, until I changed my motherboard and CPU, which means it has > a different bios and serial port setup. > > This is

My apologies, I don't know why my brain is stuck on NTPD, I meant UPSD. Regards Ge-org Brohammer -----Original Message----- From: Nut-upsuser [mailto:nut-upsuser-bounces+ge-org=kingbro.co.za at lists.alioth.debian.org] On Behalf Of Ge-org Brohammer Sent: 28 June 2013 01:06 PM To: nut-upsuser at lists.alioth.debian.org Subject: [Nut-upsuser] Server 2012 - 64bit NTPD Crash Good day I?m

After issuing this command: /upsrw -s ups.delay.shutdown=180 -u admin -p mypassword myups /I obtain this error:/ Unexpected response from upsd: ERR READONLY /After issuing this command:/ upsrw myups /I obtain no output./ /In my /upsd.users/ file I have these settings: /[admin]// //password = mypassword// //actions = SET// //instcmds = ALL// // //[myuser]// //password = mypassword//

I'm using an APC Back-UPS XS with nut 2.0.3. I've recompiled/reinstalled the source, and switched over to the newhidups driver (instead of the old hidups driver). I modified by ups.conf to use newhidups. The hotplug files were not automatically installed, I had to copy those from the scripts directory to my hotplug/usb directory. The newhidups driver loads find and then works for a

Hi! I found that if upsd had been running, then another "upsd" was typed. The upsd.pid file would be deleted and the previous upsd could not quit normally unless using "pkill upsd". The second upsd detects port conflict, and then deletes the upsd.pid. As a result, any further "upsd -c stop" or "upsd -c reload" would detect no upsd.pid and simply quit. I

OK, so I made this file: ------------------------------------------ #!/bin/sh<\n> #chkconfig: 2345 60 99 #description: NUT ups daemon if [ ! -f /usr/local/ups/bin/upsd ] then echo "NUT startup: cannot start" exit fi case "$1" in "start") chmod 0600 /proc/bus/usb/005/002 chown nut:nut /proc/bus/usb/005/002 /usr/local/ups/bin/upsdrvctl

Charles, All, I just updated the kernel on my Arch box (the one we have been working on nut with on this list). Now upsd fails to start. (upsdrvctl is fine). I've posted working then -- Reboot -- the failing log information below. The 'Reboot' was for the kernel upgrade: Dec 14 14:02:00 phoinix systemd[1]: Starting Network UPS Tools - power devices information server... Dec 14

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

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

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

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

[please keep the list CC'd] On Jul 4, 2015, at 8:09 AM, Sami M?ntysaari <sm at sami-mantysaari.com> wrote: > I have reloaded it, but still the same result. > > Any ideas? Not sure. Can you provide any additional details about the OS and version of NUT? > snip from syslog: > <code> > Jul 4 15:04:25 HP-Opreon kernel: [66083.548290] usb 2-1: usbfs: >

On 03/29/2017 02:28 PM, Arnaud Quette wrote: > > > 2017-03-29 12:32 GMT+02:00 Arnaud Quette <arnaud.quette at gmail.com > <mailto:arnaud.quette at gmail.com>>: > > > > 2017-03-29 5:49 GMT+02:00 Spike <spike at drba.org > <mailto:spike at drba.org>>: > (...) > > Is this really the desired behavior? I can certainly work

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