search for: fredericbohe

?Hello, There is a new intermediate Windows binaries release available at : http://www.networkupstools.org/package/windows/NUT-Installer-2.6.5-3.msi This fixes a regression about stopping the NUT service. Feedback is highly appreciated. Regards, Fred -- Eaton Opensource Team - http://opensource.eaton.com ----------------------------- -----------------------------

?With Arnaud Quette's help, I have tried to fix the regression concerning the APC Back UPS ES unit. This regression is related to an issue in this UPS firmware. It cannot be reverted to previous version because the current code fixes communication issue with others UPS (which behave correctly, but are not very permissive). So we (Arnaud and I) have decided to add a tweak (call it a hack if you

Hello all, There is a new Windows package of NUT. It now contains nut-scanner binary. Note that there is a known issue with libupsclient.dll with nut-scanner. The scan of NUT servers using nut-scanner will not work for now. You can find it at : http://www.networkupstools.org/source/2.6/NUT-Installer-2.6.3-1.msi Please send feedback to the list. Regards, Fred -- Team Open Source Eaton -

I was wondering what you guys do about UPS shutdown on Windows systems? Apcupsd has the same issue, so I'm assuming it is the same with NUT. Windows just makes it hard/impossible to do. Do you find draining the batteries down so much cause issues for longevity? Regarding my Eaton 5110, I found that automatic driver setup works just fine on Windows XP but not at all on Windows 7 x64 (I

Network UPS Tools version 2.6.5 has been released: http://www.networkupstools.org/ Among the many improvements and bugfixes, this release fixes the upssched regression, that rendered it unusable. Update to 2.6.5 is thus highly recommended. As noted in the news, website hosting is under migration. While I don't expect any service disruption, please report any issue you may face. Direct

My network at home/home office is primarily a Windows environment. However, I have 3 ReadyNAS Ultra machines which use NUT for UPS monitoring. The ReadyNAS devices are running a slightly modified Debian (2.6.37.6.RNx86_64.2.4) with NUT 2.0.5. What I would like to do is add some sort of web-based UPS monitoring on my intranet web server (IIS 7.5 on 2008 R2), however nut-cgi appears to be

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(

Hello! I have tested APC Back UPS ES 700 and NUT 2.6.5-3 a few days ago and I have got some news. This device is detected by nut-scanner as: [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "051D" productid = "0002" product = "Back-UPS ES 700 FW:829.D2 .I USB FW:D2 " serial =

Hi all ! I have a little problem using NUT from FreeNAS. Operating system FreeBSD 8.3-RELEASE-p4 (FreeNAS 8.3.0 BETA 2) UPS American Power Conversion/Back-UPS CS 650 FW:817.v7 .I USB FW:v7 NUT Driver Network UPS Tools - Generic HID driver 0.37 (2.6.5) USB communication driver 0.31 Trying to configure the UPS from FreeNAS failed so I try to investigate which is the problem. Running

Hello, I am currently working on the nut scanner. For detecting available upsd on the network, I rely on upscli_connect. The problem with this function is that it calls a blocking "connect" function. So the nut-scanner is blocked while waiting for the TCP timeout when trying to connect to an IP without upsd available . Since this timeout may be rather long (3 minutes on my host), I

Windows 7 Pro x64 Eaton 3S550 (brand new, battery mfg 8/15/2012) NUT 2.6.5-3 ups.status: OL CHRG CHRG was present even though it has been plugged in a few days turned on and battery.charge was 100%. Log includes me running upsc and removing power long enough to see that battery.charge will decrease. This UPS doesn't have controlled outlets despite what the upsc output says. ---

Hello! I tried NUT 2.6.5-1 (Windows port) with my APC Back UPS ES. It seems I have configured NUT properly, nut-scanner found my UPS: [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "051D" productid = "0002" product = "Back-UPS ES 525 FW:851.t3.I USB FW:t3" serial = "8B0745R23575

I'm trying to use a Nas4Free storage system. This same hardware worked fine on Freenas 0.7.2. O/S: Nas4Free 9.0.0.1.148 which comes with nut 2.6.4. UPS is an APC Back UPS RS 800. USB interface. Driver : usbhid-ups Port: auto my NAS is communicating with the UPS, but in testing power failures, I'm not getting the shutdown to be handled properly. When I pull the AC plug on the UPS,

Hello NUT Team! I continue playing with NUT for Windows and USBHID-UPS driver I've got from Frederic to fix "Data Stale" problem. It seems there is something wrong when Network UPS Tools service is starting with disconnected USB cable. UPSMON is writing "Data Stale" to output and continue do it infinitely, even the cable is connected back. Here is a short log: Network

Hello NUT Team! I am testing the early shutdowns in NUT 2.6.5-1 package for Windows (Windows 7 x64). My configuration files: upsmon.conf RUN_AS_USER upsmon MONITOR upsa at 192.168.10.200 1 upsmon pass master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD "upssched.exe" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG

Hello all, Thanks to early feedbacks from Dmitry Ogorodnikov, we have made a new Windows package of NUT with previously missing DLLs allowing to run netxml-ups and snmp-ups drivers as well as nut-scanner tool. You can find it at : http://www.networkupstools.org/source/2.6/NUT-Installer-2.6.3-3.msi Please send feedback to the list. Regards, Fred -- Eaton Opensource Team -

Hello all, In order to prepare the merge of the NSS branch to the trunk, I have validated the code in this branch by passing this validation document written by Emilien Kia : http://www.networkupstools.org/tmp/NUT-NSS_Mini_DVT_Plan-final.pdf The testing has been done on rev 3685 of the ssl-nss-port branch. As you can read, I have found no issue. Let me know if you have any comments on this.

?Hello, There is a new intermediate Windows binaries release available at : http://www.networkupstools.org/package/windows/NUT-Installer-2.6.5-4.msi This is based on SVN trunk revision 3774. This release include the porting of NSS. It uses NSS for SSL connections now, rather than OpenSSL previously. This release also fix a crash at exit time. Feedback is highly appreciated. Regards, Fred

?Hello, I would like to merge branches/serial_nutscanner to the trunk. The attached patch contains the needed modifications. You can read docs/man/nutscan_scan_eaton_serial.txt to see what it is about and docs/man/nut-scanner.txt to see modification to nut-scanner tool interface. This adds about 100K to the libnutscan.so file. Regards, Fred -----------------------------

On mar., 2011-01-18 at 19:52 +0000, Arjen de Korte wrote: > Author: adkorte-guest > Date: Tue Jan 18 19:52:02 2011 > New Revision: 2845 > URL: http://trac.networkupstools.org/projects/nut/changeset/2845 > > Log: > Prefer to use static variables locally over global variables (to prevent namespace conflicts) > > Modified: > branches/windows_port/common/common.c