Ticket #202 (closed defect: fixed)

Opened 4 years ago

Last modified 3 years ago

3.3.20 Crash on Windows 2003

Reported by: anonymous Owned by: anonymous
Priority: 3 Milestone: 0.4.0
Component: CheckSystem Version: 0.3.3
Severity: Bugs Keywords:
Cc:

Description

Event Type: Information Event Source: Application Error Event Category: (100) Event ID: 1004 Date: 7/11/2008 Time: 8:21:55 AM User: N/A Computer: EXCHANGE Description: Reporting queued error: faulting application nsclient++.exe, version 0.0.0.0, faulting module CheckSystem.dll, version 0.0.0.0, fault address 0x00025aa0.

Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 6e 73 63 ure nsc 0018: 6c 69 65 6e 74 2b 2b 2e lient++. 0020: 65 78 65 20 30 2e 30 2e exe 0.0. 0028: 30 2e 30 20 69 6e 20 43 0.0 in C 0030: 68 65 63 6b 53 79 73 74 heckSyst 0038: 65 6d 2e 64 6c 6c 20 30 em.dll 0 0040: 2e 30 2e 30 2e 30 20 61 .0.0.0 a 0048: 74 20 6f 66 66 73 65 74 t offset 0050: 20 30 30 30 32 35 61 61 00025aa 0058: 30 0

Event Type: Error Event Source: Application Error Event Category: None Event ID: 1001 Date: 7/11/2008 Time: 8:22:02 AM User: N/A Computer: EXCHANGE Description: Fault bucket 833531520.

Data: 0000: 42 75 63 6b 65 74 3a 20 Bucket: 0008: 38 33 33 35 33 31 35 32 83353152 0010: 30 0d 0a 0..

Change History

comment:1 Changed 4 years ago by anonymous

  • Owner changed from mickem to anonymous
  • Status changed from new to assigned

could you try which check causes the problem? (ie, remove and run one check at a time) and also paste log and relevant log config.

MickeM

comment:2 Changed 4 years ago by Olrait

I have the same problem i paste de logs

2008-07-18 17:01:31: message:.\FileLogger.cpp:58: Starting to log for: NSClient++ - 0.3.3.20 2008-07-02 2008-07-22 09:03:16: message:.\FileLogger.cpp:58: Starting to log for: NSClient++ - 0.3.3.20 2008-07-02 2008-07-22 09:09:58: message:.\FileLogger.cpp:58: Starting to log for: NSClient++ - 0.3.3.20 2008-07-02 2008-07-22 09:09:58: debug:.\NSClient++.cpp:426: Loading plugin: LUAScript... 2008-07-22 09:09:58: debug:.\NSClient++.cpp:426: Loading plugin: NSClient server... 2008-07-22 09:09:58: debug:.\PDHCollector.cpp:66: Autodetected w2k or later, using w2k PDH counters. 2008-07-22 09:09:58: debug:.\PDHCollector.cpp:103: Using index to retrive counternames 2008-07-22 09:09:58: debug:d:\documents\Visual Studio 2005\Projects\NSCP\branches\stable\include\Socket.h:630: Bound to: 0.0.0.0:12489 2008-07-22 09:09:58: debug:.\PDHCollector.cpp:123: Found countername: CPU: \Procesador(_total)\% de tiempo de procesador 2008-07-22 09:09:58: debug:.\PDHCollector.cpp:124: Found countername: UPTIME: \Sistema\Tiempo de actividad del sistema 2008-07-22 09:09:58: debug:.\PDHCollector.cpp:125: Found countername: MCL: \Memoria\Límite comprometido 2008-07-22 09:09:58: debug:.\PDHCollector.cpp:126: Found countername: MCB: \Memoria\Bytes comprometidos ...

...

2008-07-22 12:53:41: debug:.\NSClientListener.cpp:143: Data: None&6&ShowAll&PLANIFICADOR RECIBIR EMAILS.exe 2008-07-22 12:53:41: debug:.\NSClientListener.cpp:168: Data: ShowAll&PLANIFICADOR RECIBIR EMAILS.exe 2008-07-22 12:53:41: debug:.\NSClient++.cpp:541: Injecting: checkProcState: ShowAll, PLANIFICADOR RECIBIR EMAILS.exe, nsclient 2008-07-22 12:53:41: debug:.\NSClient++.cpp:561: Injected Result: OK 'PLANIFICADOR RECIBIR EMAILS.exe: Running' 2008-07-22 12:53:41: debug:.\NSClient++.cpp:562: Injected Performance Result: 2008-07-22 12:54:25: debug:.\NSClientListener.cpp:143: Data: None&5&ShowAll&PAVAGENTE 2008-07-22 12:54:25: debug:.\NSClientListener.cpp:168: Data: ShowAll&PAVAGENTE 2008-07-22 12:54:25: debug:.\NSClient++.cpp:541: Injecting: checkServiceState: ShowAll, PAVAGENTE, nsclient 2008-07-22 12:54:25: debug:.\NSClient++.cpp:561: Injected Result: OK 'PAVAGENTE: Started' 2008-07-22 12:54:25: debug:.\NSClient++.cpp:562: Injected Performance Result: 2008-07-22 12:54:30: debug:.\NSClientListener.cpp:143: Data: None&6&ShowAll&PLANIFICADOR EMAILS VALENCIAPORTPCS.exe 2008-07-22 12:54:30: debug:.\NSClientListener.cpp:168: Data: ShowAll&PLANIFICADOR EMAILS VALENCIAPORTPCS.exe 2008-07-22 12:54:30: debug:.\NSClient++.cpp:541: Injecting: checkProcState: ShowAll, PLANIFICADOR EMAILS VALENCIAPORTPCS.exe, nsclient 2008-07-22 12:54:30: debug:.\NSClient++.cpp:561: Injected Result: OK 'PLANIFICADOR EMAILS VALENCIAPORTPCS.exe: Running' 2008-07-22 12:54:30: debug:.\NSClient++.cpp:562: Injected Performance Result: 2008-07-22 12:55:04: debug:.\NSClientListener.cpp:143: Data: None&5&ShowAll&PavSrv? 2008-07-22 12:55:04: debug:.\NSClientListener.cpp:168: Data: ShowAll&PavSrv? 2008-07-22 12:55:04: debug:.\NSClient++.cpp:541: Injecting: checkServiceState: ShowAll, PavSrv?, nsclient 2008-07-22 12:55:04: debug:.\NSClient++.cpp:561: Injected Result: OK 'PavSrv?: Started' 2008-07-22 12:55:04: debug:.\NSClient++.cpp:562: Injected Performance Result: 2008-07-22 12:55:09: debug:.\NSClientListener.cpp:143: Data: None&5&ShowAll&PadFSvr 2008-07-22 12:55:09: debug:.\NSClientListener.cpp:168: Data: ShowAll&PadFSvr 2008-07-22 12:55:09: debug:.\NSClient++.cpp:541: Injecting: checkServiceState: ShowAll, PadFSvr, nsclient 2008-07-22 12:55:09: debug:.\NSClient++.cpp:561: Injected Result: OK 'PadFSvr: Started' 2008-07-22 12:55:09: debug:.\NSClient++.cpp:562: Injected Performance Result: 2008-07-22 12:55:49: debug:.\NSClientListener.cpp:143: Data: None&4&c 2008-07-22 12:55:49: debug:.\NSClientListener.cpp:168: Data: c 2008-07-22 12:55:49: debug:.\NSClient++.cpp:541: Injecting: CheckDriveSize: c, nsclient 2008-07-22 12:55:49: debug:.\NSClient++.cpp:561: Injected Result: OK '1163756544&4194827776' 2008-07-22 12:55:49: debug:.\NSClient++.cpp:562: Injected Performance Result: 2008-07-22 12:56:35: debug:.\NSClientListener.cpp:143: Data: None&6&ShowAll&ServiceController?.exe 2008-07-22 12:56:35: debug:.\NSClientListener.cpp:168: Data: ShowAll&ServiceController?.exe 2008-07-22 12:56:35: debug:.\NSClient++.cpp:541: Injecting: checkProcState: ShowAll, ServiceController?.exe, nsclient

comment:3 Changed 4 years ago by Olrait

Plis Help!! The nslient debug doesn´t give extra information. The isn´t any error in the debug log.

Windows Events log this error

Aplicación con errores: nsclient++.exe, versión: 0.0.0.0, módulo con error: CheckSystem.dll, versión 0.0.0.0, dirección de error 0x00025aa0.

comment:4 Changed 4 years ago by Olrait

[modules] FileLogger.dll CheckSystem.dll CheckDisk.dll NSClientListener.dll

[Settings] allowed_hosts=192.168.66.67 use_file=1

[log] debug=1 date_mask=%Y-%m-%d %H:%M:%S

[NSClient] port=12489

[NRPE]

[Check System]

[External Script]

[External Scripts]

[External Alias]

; [includes]

[NSCA Agent]

[NSCA Commands]

[NRPE Handlers]

[NRPE Client Handlers]

comment:5 Changed 4 years ago by mickem

If that is all the info in the log (I usualy prefer output of the nsclient++ /test as there is a chance the logfile is not synced before it crashes it is acually quite usefull:

the last lien:

debug:.\NSClient++.cpp:541: Injecting: checkProcState: ShowAll, ServiceController?.exe, nsclient 

says the last check (which did not finnish) was a process check so the problem is with the checkProcState command, so now I have something to go on.

Mickem

comment:6 Changed 4 years ago by mickem

try the last nightly and see if it resolves the issue (doubtfull) all I did was add some more error handling but could be worth a try.

It would be interesting to know if the last line is the one tat cases the crash or not.

Mickem

comment:7 Changed 4 years ago by anonymous

No more problems since the update to the new nightly build with Windows 2k3 R2..!

comment:8 Changed 4 years ago by mickem

oki, thanx... I shall package it up and release yet-another-bug-fix then :/

If anyone has further problems let me know...

MickeM

comment:9 Changed 3 years ago by olrait

Dear Michael

I have the same problem. I find this problem olny in the windows server that i check process.

Example :

define service{

use generic-service host_name NTESPF02 service_description LisvaFORMS_Server check_command check_nt!PROCSTATE!-d SHOWALL -l LisvaFORMS_Server.exe }

If i comment this service then the nsclient++ never crash.

Could this help you to find out a solution.

To me is very important this funtionality.

Thank & Best Regards

Olrait (martin)

comment:10 Changed 3 years ago by Olrait

I will try with this new version (new nightly build)

Thanks for your help

comment:11 Changed 3 years ago by Olrait

Only one thing . Information for development. I try to automatically tick in the NSClient++ service the option "Allow service to interact with desktop" adding a reg file to the windows registry

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet?\Services\NSClientpp] "Type"=dword:00000110

This tick this option but doesn´t really take effect even i restart the service.

If you find this you can include it in the instaler y think is a good facility.

Thanks again

comment:12 Changed 3 years ago by mickem

nsclient++ -noboot SysTray install

is IIRC the "proper" way to enable that option, in future version there will be a few more steps to get the systray working...

MickeM

comment:13 Changed 3 years ago by Olrait

48 hours without crashing. I think is solved. I will continue testing.

Thanks

comment:14 Changed 3 years ago by mickem

  • Status changed from assigned to closed
  • Resolution set to fixed

oki good stuff! I don't like my program crashing, I usually believe myself to write better code so it is a big blow to my ego ;) But this "assert" issue have been nagging me a while now since I know it is a "stupid way" and I stopped using it years ago but I havent gone over the code and removed them all until now...

Anyways, I will hopefully have a new version ("official 0.3.4 or so") out in a week or so with this fixed as well as a beta version of a new system tray so check back in a bit and of course report back if there are any crashes...

MickeM

comment:15 Changed 3 years ago by anonymous

so the fix is:

nsclient++ -noboot SysTray install

?

comment:16 Changed 3 years ago by anonymous

no the solution is to use a "newer version" unfortunetly there are some issues with the last nightly which I shall attempt to fix ASAP.

The simplest way to fix this is to use the CheckSystem.dll from the last nightly in the old (0.3.3) version...

MickeM

Note: See TracTickets for help on using tickets.