similar to: Building and configuring nut 2.6.0 - documentation issue?

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:

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

I noticed that many configuration options (configure.txt) have environment variable overrides. However, an important one does not. In the configuration.txt file, there is one section: Directories used by NUT at run-time ----------------------------------- --with-pidpath=PATH Changes the directory where pid files are stored. By default this is /var/run. Certain programs like upsmon will

On Monday 22 June 2020 08:19:15 Charles Lepple wrote: > > On Jun 18, 2020, at 12:39 PM, Mike Dillinger wrote: > > > > ups.test.result: No test initiated > > I’d recommend a battery test. Starting the test via the front panel > should be sufficient, or you might be able to do it with upscmd. from man pi at rpi4:~ $ upscmd -l myups Instant commands supported on UPS

Hi, Just started using NUT with a Liebert PSI-XR 3000 with an Intellislot web card. It seems I can't get it to run properly. I am using NUT 2.6.0 built from source on Ubuntu 8.0.4 . My build parameters are : ./configure --enable-strip --with-linux-hiddev=/usr/include/linux/hiddev.h --with-udev-dir=/lib/udev \ --prefix=/usr \ --exec-prefix=/ \ --sysconfdir=/etc/nut \

On Jul 30, 2013, at 10:39 AM, Pavel Potcheptsov (EKTOS) wrote: > Is this a trouble? Driver use path /var/state/ups/ but upsd use path /var/db/nut/upsd.pid Yes, the driver and upsd need to agree on the path to the socket. From the FreeBSD ports tree: /usr/ports/sysutils/nut/Makefile: STATEDIR?= /var/db/nut [...] CONFIGURE_ARGS= --sysconfdir=${PREFIX}/etc/nut \

Currently, the 'upsd' server uses 'ups.conf' to find out which drivers should be running and uses this information to construct the socketname it needs. This means that drivers that have not been configured in 'ups.conf' can never be seen by the server. If we ever want to autodetect (by whatever means) what drivers are started (udev?) and we start them automatically, this

I'm trying to see if we can make upsd autodetect the driver sockets from the STATEPATH. This works quite well and uses surprisingly little code (much less than parsing the 'ups.conf' file). However, since I can no longer read the name from the 'ups.conf' file, I need to extract this from the name of the socket. We might simply strip the drivername from the socket name again,

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

Trying to build nut 2.6.0 on OpenBSD 4.8, I get a compiler error. Here's my configure: ./configure --with-user=_ups --with-group=_ups \ --sysconfdir=/etc/ups --with-usb=no ... and the result: -e Configuration summary: ====================== build serial drivers: yes build USB drivers: no build SNMP drivers: no build neon based XML driver: no build Powerman PDU client driver:

I've been wanting to build the trunk since Arjen added the powerpanel driver... been having a little trouble... after running these commands: /usr/local/libexec/automake19/aclocal -I m4 /usr/local/libexec/autoconf259/autoheader /usr/local/libexec/automake19/automake -ac /usr/local/libexec/autoconf259/autoconf ./configure --with-cgi --with-user=nutmon

On Tue, Mar 09, 2010 at 07:14:59PM -0500, Charles Lepple wrote: > On Mar 9, 2010, at 5:54 PM, Kelvin Ku wrote: > >> However, if I try to run usbhid-ups as user "nut", I get: >> >> $ sudo -u nut ./usbhid-ups -a usb > [...] >> Whereas if I run it as root: >> >> $ sudo ./usbhid-ups -a usb -u root > > Did you pass "--with-user=nut"

Hi all, New to NUT dev, i was hoping someone can clear up an issue i have with the unix socket naming for me (FYI my C is not that great). I'm using 2.0.5 and this stems from a problem with the general admin of Nut but looking at the code led me to think maybe it's a bigger issue (thus i joined this list). Right to start with if i have the following in ups.conf: [apc]

On 7/1/2013 2:55 PM, Charles Lepple wrote: > On Jul 1, 2013, at 12:47 PM, John Thurston wrote: > >> I'm running Solaris 10 on a dozen SPARC boxes. I'd like to explore NUT for use with our snmp UPS, but I'm unable to complete the configure/make/install process. >> >> Can anyone share a how-to for solaris? > > Here's some general NUT-on-Solaris

Carsten Aulbert <carsten.aulbert at aei.mpg.de> writes: > 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

On Mon, 2013-07-01 at 15:42 -0800, John Thurston wrote: > On 7/1/2013 2:55 PM, Charles Lepple wrote: > > On Jul 1, 2013, at 12:47 PM, John Thurston wrote: > > > >> I'm running Solaris 10 on a dozen SPARC boxes. I'd like to explore NUT for use with our snmp UPS, but I'm unable to complete the configure/make/install process. > >> > >> Can anyone

I?m wondering if what I have done is good : # get the source from github on my computer # autogen.sh # name=nut # ./configure --prefix=/ --sysconfdir=/etc/$name --mandir=/usr/share/man --libdir=/usr/lib --includedir=/usr/include --datadir=/usr/share/$name --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut --with-drvpath=/lib/nut --with-pidpath=/var/run/$name

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 Jul 31, 2013, at 9:07 AM, James HORLEY wrote: > I?m wondering if what I have done is good : > # get the source from github on my computer > # autogen.sh > # name=nut > # ./configure --prefix=/ --sysconfdir=/etc/$name --mandir=/usr/share/man > --libdir=/usr/lib --includedir=/usr/include --datadir=/usr/share/$name > --with-statepath=/var/run/nut

On Jul 7, 2015, at 4:12 PM, Rob Groner <rgroner at RTD.com> wrote: > 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 its output, I see that it says : > > Fatal error: A previous upsd instance is already