similar to: Compilation error: NUT 2.6.2 --without-snmp

Hi, the terminating part of nut-scanner can crash in pthread code, because some threads won't exist. For example snmp part: ============================== if( allow_snmp && nutscan_avail_snmp ) { if( start_ip == NULL ) { printq(quiet,"No start IP, skipping SNMP\n"); } else { printq(quiet,"Scanning SNMP bus.\n"); #ifdef HAVE_PTHREAD if(

Hi Sergey, 2011/7/15 Sergey Talchuk <tals1975 at gmail.com> > Hi Arnaud, > > both configurations are ok :). Please find the file attached. > logic since the 2nd is automatically guessed from the first using USB Vendor and Product ID ;-) can you please send in upsc, upscmd and upsrw output. and also report the shutdown testing as described here:

Hi Arnaud, I received several replies from technical support. It turned out that according to the UPS serial number it had been manufactured in 2012. So, the device should support the ability to disable the beeper. But still I can not disable the beeper using the latest version of UPSMON Plus in Windows: http://www.pcm.ru/data/download/public/soft/setup_upsmon_v2.9.rar (don't know why; the

Hi ALL, Powercom Imperial IMP-525AP seems to be fully compatible with NUT. Unfortunately, I can not disable beeper. upscmd -u {NUT_USER} -p {NUT_PASSWORD} powercom beeper.toggle returns *OK*, however, ups.beeper.status=enabled Thank you, Sergey ========== Additional info: 1) $ upsc powercom battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 30 battery.date: 2010/01/01

Hi Charles, Yes, it looks like my g++ does contain STL library which might be just my specific case... However, as a temporary solution I disabled nutclient in Makefile (please find the file attached). And nut-2.7.3 can be compiled now. Thanks, Sergey On Wed, Jul 8, 2015 at 4:13 AM, Charles Lepple <clepple at gmail.com> wrote: > On Jul 6, 2015, at 10:32 AM, Sergey Talchuk

Hi Charles, Thanks for the prompt reply! Errors occur when execute make: /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 .deps/nutclient.Tpo -c

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 provide better compatibility with older gcc versions please (since libnutclient is an alternative to

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 provide better compatibility with older gcc versions please (since libnutclient is an alternative to

Hello guys, Please help me to resolve the issue. I bought 'SVEN Power Pro+ 500 USB' UPS few days ago and tried to setup NUT 2.6.0 to work with it. blazer_ups driver doesn't recognize the UPS :( The Manufacturer provides 'PowerD' software for linux with installation instractions on a CD (see example below). --------===------- Welcom to PowerManager System!

2012/3/23 Vladi Belperchinov-Shabanski <cade at datamax.bg> > > hello, > Hi, I'm adding -upsuser list for info > from the source documentation I figured you are dev coordinator. > I'm sorry if I got it wrong and please forward to the correct person > if possible, thanks! > I'm indeed leading NUT, but the preferred support way is through the mailing

2011/6/1 Sergey Talchuk <tals1975 at gmail.com> > Hi Arnaud, > Hi Sergey, > Vivaldi 650VA UPS works with richcomm_usb driver. > (USB ID 0925:1234) > http://www.vivaldi.su/products/ups/1949.htm > thanks for your report, I've committed an entry in the hardware compatibility list (r3017), and it's part of the just-release 2.6.1. cheers, Arnaud -- Linux / Unix

I set the ups.conf to: driver = richcomm_usb port = auto now it is connected. There were the vendor variable and product id wrong. These are the variables i get in my OMV service output: device.mfr: Richcomm dry-contact to USB solution device.model: UPS USB MON V1.4 device.serial: unknown device.type: ups driver.name: richcomm_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto

Linux-2.4.28 libusb-0.1.8 nut-2.6.5 [+most recent drivers from GIT] - from tarball EATON 3S700DIN [mfr.date 09/28/14] ---------------------------------- ISSUES: I) Too many kernel logs: --- In /var/log/kernel.log usbdevfs: usb_submit_urb returned -28 In /var/log/daemon.log: usbhid-ups[744]: libusb_get_interrupt: No error usbhid-ups[744]: libusb_get_interrupt: error submitting URB: No space left

Thanks for reply. when i try richcomm_usb or blazer_usb or other usb i get the output of : sudo /lib/nut/usbhid-ups -a trust -DD this is the output: Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.32 Error: UPS [trust] is for driver richcomm_usb, but I'm usbhid-ups! i tried to set the ups.conf to: [trust] driver = usbhid-ups port = auto vendorid = 0925

Greets... ..just bought a cheap UPS today, works in debian 7.0 wrt nut 2.6.4 using richcomm_usb driver... ....output of upsc..... //// root at debian7:~# upsc starpower at localhost device.mfr: Richcomm dry-contact to USB solution device.model: UPS USB MON V1.4 device.serial: unknown device.type: ups driver.name: richcomm_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto

On Thu, Dec 4, 2008 at 4:51 PM, Arjen de Korte <adkorte-guest at alioth.debian.org> wrote: > Author: adkorte-guest > Date: Thu Dec 4 21:51:28 2008 > New Revision: 1596 > > Log: > Added new richcomm_usb driver based on the lakeview_usb driver (using libusb). Sorry if I wasn't clear - I was advocating *renaming* the lakeview_usb driver to richcomm_usb. Is there another

Hi, are this UPS supported by any other driver than "richcomm_usb". The device works with richcomm_usb, but only signals online, offline etc. Not voltage, batterylevels etc. Bus 006 Device 009: ID 0925:1234 Lakeview Research Bus 006 Device 009: ID 0925:1234 Lakeview Research Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10

I have a Gentoo linux (OpenRC) desktop connected to a UPS, the brand is Vultech, but lsusb gives me this: Bus 003 Device 006: ID 0925:1234 Lakeview Research and I found an article about this hardware here, someone had it working with the richcomm_usb driver: http://verahill.blogspot.it/2012/12/kstar-australia-1500-va-ups-on-debian.html So, I installed nut and configured my UPS to work with the

I am a complete novice in this area so please bear with me. I have installed nut version 2.6.2-1 for my debian 64bit system. I am trying to implement 'nut' for a new VIX2120 home UPS and have determined that I need the richcomm_usb driver [usb 0925:1234]. But it is not in /lib/nut although referenced in the documentation (driver.list) How do get hold of a copy? Due to ignorance I am not

Digitus DN-170014 root at home:/home/scripts# upsc ups device.mfr: Richcomm dry-contact to USB solution device.model: UPS USB MON V1.4 device.serial: unknown device.type: ups driver.name: richcomm_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.6.4 driver.version.internal: 0.04 ups.mfr: Richcomm dry-contact to USB solution ups.model: UPS USB MON V1.4