search for: uspd

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: added 192.168.36.106:3495 0.000224...

...ss test.battery.start.deep - Start a deep battery test test.battery.start.quick - Start a quick battery test test.battery.stop - Stop the battery test pi at rpi4:~ $ upscmd myups test.battery.start.quick Username (pi): Password: Unexpected response from upsd: ERR ACCESS-DENIED Looking at /etc/nut/uspd.users, I (me, pi) should be able to do that. ??? Some help plz. > This should let the UPS firmware discharge the battery a bit, and see > how long it should last. > > Conceptually, “OL LB” is not inconsistent- it means the UPS has AC > power, but the battery state of charge is read...

This morning I finished building and configuring nut 2.6.0 on OpenBSD 4.8, and it is running fine. While I was in the config files, I noticed what looks like it may be a discrepancy between the config file commetns and the configure script default. uspd.conf has the following comment: # STATEPATH <path> # STATEPATH /var/run/nut # # Tell upsd to look for the driver state sockets in 'path' rather # than the default that was compiled into the program. When I read that, I thought the default path compiled into the program would be /...

Hi all, On 5/19/23 15:11, Greg Troxel wrote: > LB is baked in to nut behavior. So if a UPS doesn't report LB, then > it makes sense to synthesize it. Synthetic LB is the cleanest fix at > the earlier processing point. I fully agree and thus this ought to be done in/near uspd IMHO. I glanced over the server/ directory and was not sure where even to begin hooking this in. Should this be directly in upsd (upsd.c) or rather in/near the driver level (driver/main.c)? > > Yes, this could be in upsmon, but that's not synthetic LB, it's > choosing to...

...15:11, Greg Troxel wrote: >> LB is baked in to nut behavior. So if a UPS doesn't report LB, then >> it makes sense to synthesize it. Synthetic LB is the cleanest fix at >> the earlier processing point. > > I fully agree and thus this ought to be done in/near uspd IMHO. I > glanced over the server/ directory and was not sure where even to > begin hooking this in. Should this be directly in upsd (upsd.c) or > rather in/near the driver level (driver/main.c)? I think it belongs in upsd someplace, as what I want is a way to make LB appear based on a ru...

Bill S wrote, On 4/15/2014 11:18 AM: > The problem is that when I run upsset.cgi I first get a prompt for > user name and password. I then enter the same username and password > as I established in upsd.users and it seems to accept it. upsset.cgi doesn't check that user/password is valid, it just tries it when doing a command. I just tested it, it is working for me on a remote and

On Jun 22, 2020, at 8:52 AM, Gene Heskett wrote: > > pi at rpi4:~ $ upscmd myups test.battery.start.quick > Username (pi): > Password: > Unexpected response from upsd: ERR ACCESS-DENIED > > Looking at /etc/nut/uspd.users, I (me, pi) should be able to do that. ??? > Hi Gene, You have a [pi] section in upsd.users, then? If it's one of the example users from the man page or comments, you'll need to use that name with upscmd, or change upsd.users. Plus, you'll need "instcmds = all" (or...

...). /usr/local/ups/bin/upsc -l MGE (old ups is up) Configuration seems to be OK. ups.conf [MGE] driver = snmp-ups port = 192.168.200.252 desc = "Eaton Evolution S3000" community = public [MGE2] driver = snmp-ups port = 192.168.200.244 desc = "Eaton 5PX3000" community = public uspd.users [admin]     password = ***     allowfrom = localhost     upsmon master     actions = SET     instcmds = ALL cd /home/test/nut-master/server/ sudo ./upsd Network UPS Tools upsd 2.7.4.1 fopen /var/state/ups/upsd.pid: No such file or directory /usr/local/ups/etc/upsd.conf is world readable...

...e 2020 09:18:29 Charles Lepple wrote: > On Jun 22, 2020, at 8:52 AM, Gene Heskett wrote: > > pi at rpi4:~ $ upscmd myups test.battery.start.quick > > Username (pi): > > Password: > > Unexpected response from upsd: ERR ACCESS-DENIED > > > > Looking at /etc/nut/uspd.users, I (me, pi) should be able to do > > that. ??? > > Hi Gene, > > You have a [pi] section in upsd.users, then? If it's one of the > example users from the man page or comments, you'll need to use that > name with upscmd, or change upsd.users. > > Plus, you&...

Since there is apparently no immediate solution to upsstats.cgi not reading the output voltage correctly, I have moved on to trying to use upsset.cgi. To recap the UPS is a CyberPower CyberPower CP1500PFCLCD UPS running on a headless server running Slackware 14.1 with the 3.10.7 kernel. The version of NUT is 2.71 and I am using usbhid-ups for communication with the UPS The problem is that when

Hi, I have an MGE Ellipse 1000 connected to a FreeBSD 7.1 system and it works well except that if I yank the cable it doesn't detect a problem.. It seems to quite merrily read the old data (upsc reports the same values). There is nothing logged by NUT to indicate comms is lost (usbhid-ups is still running). In the attached log I yanked the able at the 28 second mark and plugged it back

My $0.02: LB is baked in to nut behavior. So if a UPS doesn't report LB, then it makes sense to synthesize it. Synthetic LB is the cleanest fix at the earlier processing point. One could have a config that is basically synthetic-lowbatt-percent that generates LB if (as Jim says) on battery, not calibrating, and batt% <= that. One could have a similar config

Hi, I'm using debian sarge on my server and connected a MGE-ups ellipse via the serial port. I searched the internet for the answer, but can't find it. My config files: <upsd.users> [admin] password = pwd allowfrom = 127.0.0.1/32 actions = set instcmds = all [upsmon] password = pwd allowfrom = 127.0.0.1/32 10.0.0.224/32 upsmon master [upsslave] password

Hello, I am having a heck of a time with false low battery alarms right now.  It has been going on for the last couple of months.  I originally started getting them with a UPS that was 1-2 years old so I thought it was time to change it out and buy a new one.  I'm still getting the false alarms with the brand new one.  The status is "OL LB" which is strange to me. I have a

...l wrote: >>> LB is baked in to nut behavior. So if a UPS doesn't report LB, then >>> it makes sense to synthesize it. Synthetic LB is the cleanest fix at >>> the earlier processing point. >> >> I fully agree and thus this ought to be done in/near uspd IMHO. I >> glanced over the server/ directory and was not sure where even to >> begin hooking this in. Should this be directly in upsd (upsd.c) or >> rather in/near the driver level (driver/main.c)? > > I think it belongs in upsd someplace, as what I want is a way to make L...

Hi Arjen, in server/upsd.c r731, you moved the call conf_load() from after check_perms() (~ l.1020) to before setupsignals() (~ l.989). The problem is that conf_load() needs to open the ups driver socket, and it assumes that STATEPATH is the current working directory. The directory is only set in l.1016. Therefore, the first attempt to open a socket will always fail. From the user's point of