FredericBohe at Eaton.com
2012-Sep-19 13:13 UTC
[Nut-upsuser] New intermediate Windows binaries release - 2.6.5-3
?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 ----------------------------- -----------------------------
Denis Serov
2012-Sep-25 18:07 UTC
[Nut-upsuser] New intermediate Windows binaries release - 2.6.5-3
Hello! Stopping problem has gone in 2.6.5-3 version. But something wrong with closing of UPSMON. Every time then I am stopping NUT service (stable reproducing), the following error appears in Event Log: Faulting application name: upsmon.exe, version: 0.0.0.0, time stamp: 0x5059adc8 Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f Exception code: 0xc0000005 Fault offset: 0x0002e41b Faulting process id: 0x5b0 Faulting application start time: 0x01cd9b45a55919d2 Faulting application path: C:\Program Files (x86)\NUT\sbin\upsmon.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: 10040c12-0739-11e2-981e-001dbab5966a And I think I have found another issue. I started UPSMON process manually when NUT service was stopped during my experiments. After that, I started NUT service. There was a garbage in UPSMON output (in manually executed instance, once detected): Execute command "cmd.exe /C C:\NUT\1.cmd upslost" OK 6.205691 Trying to connect to UPS [upsa at 192.168.10.200] 7.250892 UPS [upsa at 192.168.10.200]: connect failed: Connection failure: Unknown error 7.250892 do_notify: ntype 0x0008 (NOCOMM) 7.250892 UPS upsa at 192.168.10.200 is unavailable 7.250892 Current power value: 1 7.266492 Minimum power value: 1 12.277778 Trying to connect to UPS [upsa at 192.168.10.200] 12.277778 Login on UPS [upsa at 192.168.10.200] failed - got [ERR ACCESS-DENIED] 12.277778 Current power value: 1 12.277778 Minimum power value: 1 17.285387 pollups: upsa at 192.168.10.200 17.300987 get_var: upsa at 192.168.10.200 / status 17.300987 parse_status: [OL] 17.300987 do_notify: ntype 0x0004 (COMMOK) 17.300987 Communications with UPS upsa at 192.168.10.200 established 17.316587 parsing: [OL] 17.316587 ups_on_line: upsa at 192.168.10.200 (first time) 17.316587 Current power value: 1 17.T3i1m6e5r8 7q uMeiunei meummp tpyo,w eerx ivtailnuge : 1 22.338275 pollups: upsa at 192.168.10.200 22.353875 get_var: upsa at 192.168.10.200 / status 22.369475 parse_status: [OL] 22.369475 parsing: [OL] 22.369475 ups_on_line: upsa at 192.168.10.200 (no change) 22.400675 Current power value: 1 It may be possible problem with a memory buffer. I will continue testing this version... OS: Windows 7 x64 Ultimate English UPS: APC Back-UPS ES-525 Thanks, Denis -----Original Message----- From: nut-upsuser-bounces+dns-srv=yandex.ru at lists.alioth.debian.org [mailto:nut-upsuser-bounces+dns-srv=yandex.ru at lists.alioth.debian.org] On Behalf Of FredericBohe at Eaton.com Sent: Wednesday, September 19, 2012 5:14 PM To: nut-upsuser at lists.alioth.debian.org Subject: [Nut-upsuser] New intermediate Windows binaries release - 2.6.5-3 ?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 ----------------------------- ----------------------------- _______________________________________________ Nut-upsuser mailing list Nut-upsuser at lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Seemingly Similar Threads
- Back UPS ES and data stale with disconnected device
- Early shutdowns and 2.6.5-1 package for Windows
- Problem with upsmon on x64 Windows
- Data stale and Back UPS ES
- battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error