similar to: Debian 9 : Can't open /etc/nut/upsd.users: Permission denied

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

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

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

On December 10, 2017 4:55:51 PM GMT+01:00, Roger Price <roger at rogerprice.org> wrote: >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)

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 tried adding SSL/TLS support to NUT following the User Manual chapter 9.5 "Configuring SSL". I got as far as generating a self-signed private key and a certificate (public key) in a single file gold.pem which has the form -----BEGIN CERTIFICATE----- MIID3DCCA... -----END CERTIFICATE----- -----BEGIN PRIVATE KEY----- MIIEvQIBA... -----END PRIVATE KEY----- I updated

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

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

On 12/16/2013 09:06 AM, Charles Lepple wrote: > If you want, we can take a look at the output of the aforementioned udevd > command from your system. Please compress the output, and if the list bounces > it, I'll extract the relevant portion from the bounce message. > > I have a funny feeling we might either have a Debian-specific dependency on > 91-permissions.rules, or

> 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

Hi, I've had NUT 2.6.1 on OpenIndiana working with a Tripp-Lite ECO550. I've been playing around with the config files a little bit, and I must have done something that messed up the demon. I now get wiley$ pfexec /opt/nut/sbin/upsd -DD Network UPS Tools upsd 2.6.1 0.000000 listening on 127.0.0.1 port 3493 0.000486 listening on ::1 port 3493 0.001279 Can't connect to

I'm using NUT 2.4.1 with openSUSE 11.2, my UPS is an MGE/Eaton Ellipse ASR 1500 USBS. The set-up is as described at http://rogerprice.org/NUT.html. Since NUT uses TCP wrappers, I have the /etc/hosts.allow entry upsd : 10.0.0/24, localhost, LOCAL, 127.0.0.1 : ALLOW When I pull the plug from the wall to test my setup, I get the sequence of KDE notifications and finally a

Dear List, I'm running NUT 2.4.1 on openSUSE 11.3 64 bits, kernel 2.6.34. The UPS is an Eaton Ellipse ASR 1500 USBS. With driver usbhid-ups NUT works perfectly _until_ I turn off IPv6. By default IPv6 is turned on in openSUSE 11.3. I visited YaST -> Network Settings -> Global options and deselected "Enable IPv6". I then restarted the box. When I entered the command

Hi thanks Roger. Well I'm just using Ubuntu Server 16.04 LTS I only ran that command as a few guides say that's how to establish if a daemon is compiled with tcp wrappers: https://www.cyberciti.biz/faq/tcp-wrappers-hosts-allow-deny-tutorial/ I haven't really used TCP wrappers before so I'm not even sure if my hosts.allow entries are correct: upsd : ipaddressofclientgoeshere ups

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

I would like to build a list of the user names and configuration file locations for the most common distributions which include NUT. So far I have: Distrib User Config directory debian nut /etc/nut/ opensuse upsd /etc/ups/ These will be used to produce more user-friendly tools and documentation for NUT. If you use some other distribution, could you report 1. How does

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

I'm reading man nut.conf, and trying to understand the MODE directive. Does the specification mode=netserver mean that only upsd and the driver(s) will be started, and that upsmon will not be started? The man page says "Distribution?s init script should source this file in order to determine which components have to be started." But looking at the code which starts upsd in the

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