OK I reproduce the crash. It was indeed not related to the configuration.
It is now fixed and commited in windows_port branch. It will be available in 
the next binary release (not scheduled yet).

thanks for your report.

Fred

--
Eaton Opensource Team - http://opensource.eaton.com



-----------------------------

-----------------------------

________________________________________
From: Denis Serov [[email protected]]
Sent: Saturday, October 13, 2012 9:41 PM
To: Bohe, Frederic; [email protected]
Subject: RE: [Nut-upsuser] New intermediate Windows binaries release -  2.6.5-3

Hello Frederic!

I found more information about this fault. It seems that is unhandled exception 
(writing to NULL-pointer):

First-chance exception at 0x7773e41b (ntdll.dll) in upsmon.exe: 0xC0000005: 
Access violation writing location 0x00000000.

The stack calls:

>       ntdll.dll!@RtlpLowFragHeapFree@8()  + 0x89 bytes
        ntdll.dll!_RtlFreeHeap@12()  + 0x7e bytes
        AcXtrnal.dll!77da9ed9()
        [Frames below may be incorrect and/or missing, no symbols loaded for 
AcXtrnal.dll]
        msvcrt.dll!751798cd()
        libupsclient-1.dll!639c724a()
        msvcrt.dll!7517a53a()
        libupsclient-1.dll!639c3bd3()
        libupsclient-1.dll!639c369d()
        libupsclient-1.dll!639c31e5()
        msvcrt.dll!75179d45()
        AcXtrnal.dll!77da8433()
        ntdll.dll!__RtlUserThreadStart@8()  + 0x1b bytes

And now I see that this error was repeated more later releasing of 2.6.5-3 
version (I have missed this point because of my custom filter for NUT in Event 
Viewer). The fault is stable reproduced in my environment and I think it 
doesn't related to any configuration files (I have played this different cases 
with the same result).

Hope this helps...

Thanks,
Denis

-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Friday, October 12, 2012 12:13 PM
To: [email protected]; [email protected]
Subject: RE: [Nut-upsuser] New intermediate Windows binaries release - 2.6.5-3

> From: nut-upsuser-bounces+fredericbohe=eaton....@lists.alioth.debian.org 
[nut-upsuser-bounces+fredericbohe=eaton....@lists.alioth.debian.org] on behalf 
of Denis Serov [[email protected]]
> Sent: Tuesday, September 25, 2012 8:07 PM
> To: [email protected]
> Subject: Re: [Nut-upsuser] New intermediate Windows binaries release -
> 2.6.5-3
>
> Hello!

Hello Denis,

>
> 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

Can't reproduce this here. Can you send your configuration files please.


>
> 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 [[email protected]]
>    7.250892     UPS [[email protected]]: connect failed: Connection 
> failure: Unknown error
>    7.250892     do_notify: ntype 0x0008 (NOCOMM)
>    7.250892     UPS [email protected] is unavailable
>    7.250892     Current power value: 1
>    7.266492     Minimum power value: 1
>   12.277778     Trying to connect to UPS [[email protected]]
>   12.277778     Login on UPS [[email protected]] failed - got [ERR 
> ACCESS-DENIED]
>   12.277778     Current power value: 1
>   12.277778     Minimum power value: 1
>   17.285387     pollups: [email protected]
>   17.300987     get_var: [email protected] / status
>   17.300987     parse_status: [OL]
>   17.300987     do_notify: ntype 0x0004 (COMMOK)
>   17.300987     Communications with UPS [email protected] established
>   17.316587     parsing: [OL]
>   17.316587     ups_on_line: [email protected] (first time)
>   17.316587     Current power value: 1
>   17.T3i1m6e5r8 7q      uMeiunei meummp tpyo,w eerx ivtailnuge
> : 1
>   22.338275     pollups: [email protected]
>   22.353875     get_var: [email protected] / status
>   22.369475     parse_status: [OL]
>   22.369475     parsing: [OL]
>   22.369475     ups_on_line: [email protected] (no change)
>   22.400675     Current power value: 1
>
> It may be possible problem with a memory buffer.

I don't think so. I seems that upssched output is mangled with upsmon output 
(upssched output is something like "Timer queue is empty, exiting"). This may 
happen because upsmon and upssched are sharing the same console since upssched 
is ran by upsmon. It's not beautiful, but it is not a bug.

>
> I will continue testing this version...

Thanks for that.

Regards,
Fred

>
> OS: Windows 7 x64 Ultimate English
> UPS: APC Back-UPS ES-525
>
> Thanks,
> Denis



-----------------------------

-----------------------------

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On 
Behalf Of [email protected]
Sent: Wednesday, September 19, 2012 5:14 PM
To: [email protected]
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
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser


_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Reply via email to