similar to: [2.0.3] upsd.conf: Permission denied even if correctly set ?

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):

I have a new APC Back-UPS XS 1200. It is detected properly by the Linux kernel (2.6.16): # dmesg usb 5-3.4: new low speed USB device using ehci_hcd and address 9 usb 5-3.4: new device found, idVendor=051d, idProduct=0002 usb 5-3.4: new device strings: Mfr=3, Product=1, SerialNumber=2 usb 5-3.4: Product: Back-UPS XS 1200 FW:8.g1 .D USB FW:g1 usb 5-3.4: Manufacturer: American Power Conversion usb

I installed nut 2.7.4-5 on a fresh Debian 9.2.1 system. I updated the configuration files, started nut in standalone mode, and got the error message Can't open /etc/nut/upsd.users: Permission denied This is because the file has ownership and permissions -rw------- 1 root nut 91 Aug 3 11:44 upsd.users I changed the ownership and permissions in /etc/nut/ to drwxr-xr-x

On Sun, 10 Dec 2017, Jim Klimov wrote: > I am not sure the rights offered in that bug are fully ok: generally you > wouldn't want the configs to be writable by the service daemon if you > can avoid it (so if it's hacked - it can be abused to a lesser extent). > I think the only writable bit is the killpower file, which might better > belong in /var/run/nut or state-dir

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 recently had a failure with my old MGE ESV8 ups, it just died on me so I had to get a new one. I found a MGE ESV8+ cheap and everything seems to work fine with it except the communication with the computer. The old ESV8 (non +) worked fine with NUT after applying some patches I got from the mailing list, but I think they are in the source tree now. I'm using the same cable that

After updating from NUT 2.0.3 to 2.0.5 I got this error from upsd during startup: Can't connect to UPS [myups] (myups): No such file or directory The problem was that newhidups created a pipe on /var/run/nut/newhidups-auto while upsd was looking for /var/run/nut/myups. The solution to the problem was to add the option "-a myups" to the newhidups command line in the init script.

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

On Dec 10, 2017, at 6:10 AM, Roger Price <roger at rogerprice.org> wrote: > > The nut:nut ownership seems to me to be more natural, and the root:nut ownership looks like a bug in the Debian package. I would argue it slightly differently: upsd has no need to write to upsd.users (or change permissions on that file), so root:nut makes sense to me, but with group-read permissions

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

Hi all, I know there are some howto's about Powerware 5115 and Ubuntu, but I can't still get that thing working. Can someone give some light... 1. Powerware 5115, serial port (ttyS0) 2. Ubuntu 6.06.1 as LTSP-server As reference: http://gentoo-wiki.com/HOWTO_NUT http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ --- a. I try to start driver as root. root at

Hi all, I know there are some howto's about Powerware 5115 and Ubuntu, but I can't still get that thing working. Can someone give some light... 1. Powerware 5115, serial port (ttyS0) 2. Ubuntu 6.06.1 as LTSP-server As reference: http://gentoo-wiki.com/HOWTO_NUT http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ --- a. I try to start driver as root. root at

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

On Sun, 10 Dec 2017, Charles Lepple wrote: > Either way, the default permissions are under the packager's control, so > I would recommend that you file a bug with Debian: > https://www.debian.org/Bugs/Reporting (feel free to mention the bug > number here) Debian Bug Tracker told me that the URL is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884021. Roger

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

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

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

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

[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: >