similar to: Tripplite_usb Driver fail on OMNIVS1500

- Charles > On Oct 16, 2016, at 3:34 AM, Daniel Shields <grungelizard9 at hotmail.com> wrote: > > I've been testing with debug further and there's a few extra lines when the nut-server stops communicating as opposed to when it's running. > > > Backtrace after stale data, UPS nailbunny at localhost is unavailable: > Sorry to take a while to get back to you

Thank You for You reply, Charles D?a 07.10.2017 o 14:30 Charles Lepple nap?sal(a): > Is the "lan4.1" cable different from this one? > http://networkupstools.org/cables.html#_tripp_lite Yes, it is different. The correct cable for this interface version looks like this: http://pinouts.ru/UPS/tripplite_smartpro_cable_pinout.shtml > Are you comfortable with rebuilding the

Hi Arnaud & Charles, You?ll have to forgive my low level of Linux Understanding here?. I downloaded the source files, modified the appropriate driver file, re-compiled it (all of this was a lot of research and learning!) When I use the new driver I get ? Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.93 (2.7.4.1) Can't chdir to

Got the: git clone git://github.com/networkupstools/nut.git To work. Had to all so do this: apt-get install autoconf apt-get install libtool Did put driver = usbhid-ups in the /etc/nut/ups.conf file like you said. Here is what I got for it all: root at odroid-u2:~/nut# ./autogen.sh Calling autoreconf... libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'. libtoolize: copying

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

Hi, Charles I'm trying compilation but there is no configure command in the cloned git directory of nut. D?a 08.10.2017 o 23:47 Charles Lepple nap?sal(a): > On Oct 8, 2017, at 4:34 PM, tuharsky at misbb.sk wrote: >> Thank You for You reply, Charles >> >> >> D?a 07.10.2017 o 14:30 Charles Lepple nap?sal(a): >>> Is the "lan4.1" cable different

El 18/07/15 a les 17:03, Charles Lepple ha escrit: > On Jul 17, 2015, at 9:42 AM, dmanye <dmanye at urv.cat> wrote: > >> so i reinstalled again... but instead of using four separate partitions for /, /usr, /var and /tmp, put all the stuff under an unique / partition and... it works! why exactly? no idea, because if i'm not wrong, nut sensitive stuff is under /lib, /sbin,

I see, so you kept the load.on.delay command but removed the check to see if it was handled. Did you do the same thing for the shutdown.stayoff logic? https://github.com/networkupstools/nut/blob/master/drivers/usbhid-ups.c#L562 This might be a dumb question but did this require you to recompile the kernel? These types of changes are way beyond my depth. Thank you for the direction! On Thu, Jan

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 \

Anybody knows what configure command settings FreeNAS use to compile NUT? More info on my journey: http://forums.freenas.org/index.php?threads/nobreak-bz1200-br-back-ups-rs-1200va-600w-bivolt-115-nt.20247/ Thanks Bruno -------------- next part -------------- An HTML attachment was scrubbed... URL:

While attempting to package up the HEAD version of nut for our department/campus, I've run into a couple of minor issues with the latest HEAD - I'm going to give it another whack at a PW9170+ UPS and want to make sure I have the latest revision. :) First is, whilst building the drivers (SNMP required), I get: gmake[1]: Entering directory `/fsys2/source/nut-2.1/nut-2.1_cvs/drivers'

Network UPS Tools version 2.4.3 has been released. http://www.networkupstools.org/ Note: this is only a bugfix release that only solves the regression on IPv6 activation. Direct access: - Download: http://www.networkupstools.org/source/2.4/nut-2.4.3.tar.gz - News: http://www.networkupstools.org/source/2.4/new-2.4.3.txt - ChangeLog: http://www.networkupstools.org/source/2.4/ChangeLog the NUT

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

Hi, my nut version is 2.2.2-6.4, debian lenny The ups we use is a tripplite OMNIVS1000 USB The drivers i tried are tripplite_usb and usbhid-ups, googled very long about the problems, but didn't get it to run. Does someone has experiences or similar problems? lsusb and lsmod are all right in /etc/udev/rules.d/52_nut-usbups.rules I found one line according to the modell ---- # Tripp Lite -

Hi, I have set up a RaspberryPi computer to do monitoring of two UPSs. One is an MGE evolution 800, one is an Eaton Powerware 5110. The MGE was being monitored by another Linux (Ubuntu 12.04) computer, and I just copied and pasted in the relevant nut config and it works just fine with nut. I've tried to set up the Powerware 5110 with nut, and the bcmxcp_usb driver can't communicate

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"

[resend of message because of wrong 'From' in the first run, sorry] nut 2.0.4 When configuring with different --prefix and --exec_prefix, the drivers by default go into $prefix/bin where they should go into $exec_prefix/bin IMHO. Dito for the CGIPATH. If this is agreed upon, I would be happy to provide a patch... R'

Thanks Dan and Charles - I've found the usb passthrough will be a non-starter (not supported on my host). Dan - is your recommendation to build Nut from source or just the driver? I'm trying to build the whole project but am obviously missing dependencies... I've come across a configure error syntax error near unexpected token `CPPUNIT,' which I've seen in a previous

Hello, I was thinking about what could be going wrong here, and a few ideas pop up: 1) If you installed NUT from packaging, there should have been no need to add OS groups/users manually. There is a valid use-case for running different daemons under different accounts, as long as they talk over network and access same files or UNIX sockets at best by sharing a group for that, but it does need

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 \