Changes between Version 5 and Version 6 of doc/usage/nscp/crash

Timestamp:

12/26/10 17:46:01 (2 years ago)

Author:

mickem

Comment:

--

doc/usage/nscp/crash

@@ -31 +31 @@
 To get you started I have divided this guide into three sections but nothing keeps you (and I advocate when possible) from using all three of these methods.
 
-== Archiving files ==
+=== Archiving files ===
 
 The simplest way to protect your self is to make yourself aware of the fact that NSClient++ has crashed. This is done using both the archive feature and the [check_nscp] command in addition to this archiving crash dump files makes it possible to submit them by hand afterwards if you have an issue you want me to help you resolve. Submitting the crash dumps are fairly simple and you can either use the reporter tool or just send them via email to me.
@@ -68 +68 @@
 }}}
 
-The module serves two purposes the first being to collect all error messages reported inside NSClient++ and the second being to check the crash dump folder for crash dumps.
+The module serves two purposes the first being to collect all error messages reported inside NSClient++ and the second being to check the crash dump folder for crash dumps. After enabling the CheckNSCP module start NSClient++ in "test" mode by running the following command:
+{{{
+nsclient++ /test
+}}}
 
+Now go to your nagios box and run the check_nscp command from using the check_nrpe command.
+{{{
+check_nrpe ... -c check_nscp
+OK: 0 crash(es), 0 error(s)
+}}}
+Hopefully you now see the "OK: ..." response above with means everything is fine if not you already have a problem with you need to resolve. To simulate a problem we can force the client to crash when it is in "test" mode using the assert command. So go back to your "nsclient++ /test" command window and type the following:
+{{{
+...
+assert
 
+}}}
+The result should be that NSClient++ crashes and produces a dump file. Notice if you have enabled "restart" (default) here you need to first stop nsclient++ before we can continue. So first stop nsclient++ then start it again in "test" mode.
+{{{
+nsclient++ -stop
+nsclient++ -test
+...
+}}}
 
+Now go back to the nagios machine and run the check_nscp command again. This time we should see an error indicating that NSClient++ has crashed.
+{{{
+check_nrpe ... -c check_nscp
+ERROR: 1 crash(es), last crash: fb472415-34e8-434d-9b48-f3929a834a87.dmp.txt
+}}}
 
+The next step is to remove the crash dump and then start the service normally.
+The crash dumps are stored under %LOCALAPPDATA%\NSClient++\crash dumps. So open that folder and see if you can find the dump mentioned above. If you remove the file and again run the check_nscp command the result should revert back to good again.
 
+It is important to understand that crash dumps are per-user which means if you run in "test" mode you will not see the same dumps as if you run the agent as a service.
 
+=== Submit crash reports ===
 
 '''TODO'''
+
+=== Restart service ===
+
+'''TODO'''
+