similar to: Re: Nut-upsuser Digest, Vol 1, Issue 28

I've got persistent trouble getting nut to work, though I think I've done everything by the book (the Debian specific readme included). I've tracked it down to upsd not working as it should: it just won't keep going. :( I.e. checking the process list (or using its reload command) shows that there just isn't a upsd process, at all. Starting upsd with a few -D's for

I have followed the instructions according to: http://rcom.univie.ac.at/download.html#RExcel -- "You will have to install . a suitable version of R (I have installed R 3.0.1, CRAN Amsterdam) . a matching version of rscproxy . statconnDCOM or rcom with statconnDCOM Download RExcel 3.2.13

Hi Philip, I've updated NUT to 2.7.3 and finally found the root cause for the unexpected shutdown: It is recommended to increase pollinterval to 10 seconds in ups.conf for usbhid-ups driver due to a known issue: http://www.networkupstools.org/docs/man/usbhid-ups.html Default DEADTIME=15 in upsmon.conf was triggering shutdown. Increasing the value to 30 seconds resolved the issue. Now when

Oh oops, I see you already did. -- Peter selinger wrote: > > You could send it without "submitting" it. That's the advantage of > patches - they can be discussed. There are lots of eyeballs here that > might see what's wrong. Thanks, -- Peter > > Eric S. Raymond wrote: > > > > Peter Selinger <selinger at mathstat.dal.ca>: > > > I

Hello! Looks like Lau Kim Ping stepped on another Ablerex box, just like I did: http://lists.alioth.debian.org/pipermail/nut-upsdev/2005-December/000461.html The problems he is describing are exactly the same I had. Eventually I ran out of ideas and moved on to other things, but I still wish to get the thing to work. --Max -- Open WebMail Project (http://openwebmail.org)

> driver.name: newhidups [...] > ups.status: OL CHRG Euhm, there is no status 'CHRG' according to 'docs/new-drivers.txt' folks. If you feel the need to create new status flags, at the very least mention them in the section 'Status data' in this file. Unless you document it somewhere, it's of no use to clients. [soapbox] Before doing so, ask yourself (and

On 1/2/07, Eric A. Hall <ehall@ehsco.com> wrote: > I can hack up a Cacti PHP script to monitor UPS state via the upsc client > in the meantime. I'll have to manually enumerate the UPS names associated > with a host target (is there a way to probe for them with upsc now?), but > otherwise it ought to be pretty straightforward scripting. NUT developers, The NUT protocol

On 2/27/07, A.Lizard <alizard@ecis.com> wrote: > terrarium:/home/alizard# /usr/local/ups/bin/newhidups -DDD -a belkin-ups > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5-pre2) > > debug level is '3' > Checking device (050D/0551) (002/006) the '002/006' part is "bus->dirname, dev->filename" in libusb.c. Does

sure enough, I checked, and when you enable maintainer mode and touch configure.in, auto* stuff gets rebuilt. I will check this in later this evening. On 4/2/07, Charles Lepple <clepple@gmail.com> wrote: > On 4/2/07, Zoltan Farkas <zoly@daxtechnologies.com> wrote: > > main-hal.c: In function `main': > > main-hal.c:454: error: `HAL_USER' undeclared (first use in

> It is a pleasure for me to help NUT Project and I will order a SNMP Web > card 66102 to following address [ address information removed ] > Is it OK ? (if yes, the order could be issued on next Monday) That would be a great help, I appreciate that. It's just too bad that you CC'ed the NUT development mailinglist with my full (private) address information. I'd rather keep

> Today's Topics: > > 1. Re: Possible support for Trust 1300VA LCD Management UPS? > (Charles Lepple) > Hmm, you have both libusb-compat and libusb-legacy. Unfortunately, > that alone doesn't tell us what NUT is linked against. > > What does "otool -L <path-to-drivers>/blazer_usb" show? Not sure what > that path would be for MacPorts, but

On Jul 6, 2015, at 4:40 AM, Sergey Talchuk wrote: > Dear developers, > > libnutclient has been added as a C++ alternative to libupsclient in 2.7.1. As a result I can't compile nut 2.7.3 with gcc-3.3.6. What does the error message look like? Does the configure script fail when checking for the C++ compiler, or later on? > There wasn't such a problem with nut-2.6.5. > >

On Jul 6, 2015, at 10:32 AM, Sergey Talchuk <tals1975 at gmail.com> wrote: > /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../include -MT nutclient.lo -MD -MP -MF $depbase.Tpo -c -o nutclient.lo nutclient.cpp &&\ > mv -f $depbase.Tpo $depbase.Plo > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -MT nutclient.lo -MD -MP -MF

Hi Arnaud, You are an officer and a gentleman, very helpful on the email lists when time permits, and I am very happy to support the NUT infrastructure! I hope that my donation makes the hosting easier to run for a while! Cheers, Greg On 3/07/2015 2:49 am, Arnaud Quette wrote: > Dear NUT Community, > > It's not something you've been used to from me, but... > I've been

2015-07-06 10:40 GMT+02:00 Sergey Talchuk <tals1975 at gmail.com>: > Dear developers, > > libnutclient has been added as a C++ alternative to libupsclient in 2.7.1. > As a result I can't compile nut 2.7.3 with gcc-3.3.6. There wasn't such a > problem with nut-2.6.5. > > Is it possible to add a configuration parameter like > '-without-libnutclient' to

Drew, Another thing to consider is the NUT driver documentation. This is the template, but since it originally predated the USB drivers, feel free to draw on the other man pages for inspiration: https://github.com/networkupstools/nut/blob/master/docs/man/skel.txt - Charles

Hello Gene, > I just had a similar situation using heyu on /dev/ttyUSB0. I could > find the udev rule that had changed it, so I took the next best > route, got root and put a chmod and a chown of that port in my > /etc/rc.local file, which runs last at bootup. And heyu is once > again a happy camper. > > This might not be your problem, but its something to check. thank for

I am also having Windows Issues, Refer back to the post I received from Charles Lepple. He gave me the details on how to resolve the missing USB driver issue - Although I would be very interested in what you find as I have not found time to revisit the issue yet.. ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 19 Jul 2016 17:28:51

On Sat, 03 Dec 2016 15:33:13 +0000 nut-upsuser-confirm+ef647a6e4286da06f08adbb25da1e1621b800121 at lists.alioth.debian.org wrote: > Mailing list removal confirmation notice for mailing list Nut-upsuser > > We have received a request for the removal of your email address, > "erghdebergh at gmail.com" from the nut-upsuser at lists.alioth.debian.org > mailing list. To

On Sat, 03 Dec 2016 15:33:13 +0000 nut-upsuser-confirm+ef647a6e4286da06f08adbb25da1e1621b800121 at lists.alioth.debian.org wrote: > Mailing list removal confirmation notice for mailing list Nut-upsuser > > We have received a request for the removal of your email address, > "erghdebergh at gmail.com" from the nut-upsuser at lists.alioth.debian.org > mailing list. To