Peter, the message says it: "Please set ttdebug_log/tt to a filename in ttmain.mk/tt for enabling exception logging."
After setting the variable you have to issue 'cmk -O' or 'cmk -R' for the setting to be applied. At the end watch the output in the debug log for the error regarding logwatch. When found deactivate the debug_log setting again and issue 'cmk -O/-R' - the log can get really big. Log should point you (or us) to the right direction. HTH, Marcel 2013/7/31 David Peter <[email protected]>: > Hi there, > > i could get rid of the old warnings. The log says > > [1375276456] SERVICE ALERT: mail2(...).de;-;UNKNOWN;HARD;1;UNKNOWN - invalid > output from agent, invalid check parameters or error in implementation of > check local. Please set <tt>debug_log</tt> to a filename in <tt>main.mk</tt> > for enabling exception logging. > [1375276456] SERVICE NOTIFICATION: > david;mail2(...).de;-;UNKNOWN;check-mk-notify;UNKNOWN - invalid output from > agent, invalid check parameters or error in implementation of check local. > Please set ttdebug_log/tt to a filename in ttmain.mk/tt for enabling > exception logging. > > Did I forgot something? > > -- > Peter David > Information Services > > Vocatus AG * Oppelner Straße 5 * 82194 Gröbenzell/München > Telefon +49 8142 5069 117 * Fax +49 8142 5069 299 > www.vocatus.de > > Vorstandsmitglieder: Dr. Florian Bauer, Hardy C. Koth, Alexander S. Weigmann, > Dr. Gaby Wiegran, Aufsichtsratsvorsitzender: Dr. Rolf W. Habbel, > Sitz der Gesellschaft: Gröbenzell, Registergericht München HRB 128851 > > -----Original Message----- > From: Marcel Schulte [mailto:[email protected]] > Sent: Mittwoch, 31. Juli 2013 15:06 > To: David Peter > Cc: [email protected] > Subject: Re: [omd-users] check_mk.ini logwatch restriction > > You can get rid of such warnings - but not of the warnings alarmed/received > before the agent's reconfiguration and restart. These warnings stay until > purged. > > What does the debug log say for the UNKNOWN status? > > Marcel > > 2013/7/31 David Peter <[email protected]>: >> Hi Marcel, >> >> yes i restarted the windows service after changing the config. I know >> that I can change the level of the message, but I thought that with >> >>>> [logwatch] >>>> # Nur critical senden >>>> logfile application = crit >>>> logfile internet explorer = crit >>>> logfile system = crit >>>> logfile security = crit >>>> logfile * = off >> >> I can get rid of warning-messages. I also re-inventorized the server where I >> have the issue, now I have something strange: >> >> State "UNKN" Service "- "Status detail "invalid output from agent, invalid >> check parameters or error in implementation of check local. Please set >> debug_log to a filename in main.mk for enabling exception logging." >> >> This is strange. >> >> -- >> Peter David >> Information Services >> >> Vocatus AG * Oppelner Straße 5 * 82194 Gröbenzell/München Telefon +49 >> 8142 5069 117 * Fax +49 8142 5069 299 www.vocatus.de >> >> Vorstandsmitglieder: Dr. Florian Bauer, Hardy C. Koth, Alexander S. >> Weigmann, Dr. Gaby Wiegran, Aufsichtsratsvorsitzender: Dr. Rolf W. >> Habbel, Sitz der Gesellschaft: Gröbenzell, Registergericht München HRB >> 128851 >> >> -----Original Message----- >> From: Marcel Schulte [mailto:[email protected]] >> Sent: Mittwoch, 31. Juli 2013 14:23 >> To: David Peter >> Cc: [email protected] >> Subject: Re: [omd-users] check_mk.ini logwatch restriction >> >> Hi Peter, >> >> sorry, forgot something: >> >> 1. existing services in WARN and CRIT status at OMD site are not cleared by >> agent config changes. >> 2. if you had LOG services from logs other than the ones shown in the config >> you'll have to reinventorize the appropriate hosts to get rid of these >> services. >> >> HTH, >> Marcel >> >> 2013/7/31 Marcel Schulte <[email protected]>: >>> Hi Peter, >>> >>> did you restart every agent (the windows service) after changing its >>> config? Changes are only applied at agent startup... >>> >>> Possible but I think you've checked this: CRIT messages could be set >>> to WARN by rules at OMD server... >>> >>> HTH, >>> Marcel >>> >>> 2013/7/31 Peter David <[email protected]>: >>>> Hello List! >>>> >>>> I have omd 1.00 installed on SLES 11 SP2 with multiple servers monitored. >>>> Everything is working fine, i really like OMD!! >>>> There are a few Windows (2k3 and 2k8R2) machines as well where i >>>> want to restrict the logwatch-notification to critical only. I'm not >>>> sure if it is working, because i've added >>>> >>>> [logwatch] >>>> # Nur critical senden >>>> logfile application = crit >>>> logfile internet explorer = crit >>>> logfile system = crit >>>> logfile security = crit >>>> logfile * = off >>>> >>>> (http://mathias-kettner.de/checkmk_windows.html) >>>> >>>> to the check_mk.ini on multiple servers but from some of them i >>>> still get warning-messages based on the logwatch. Where is the error? >>>> >>>> Greetings! >>>> >>>> _______________________________________________ >>>> omd-users mailing list >>>> [email protected] >>>> http://lists.mathias-kettner.de/mailman/listinfo/omd-users _______________________________________________ omd-users mailing list [email protected] http://lists.mathias-kettner.de/mailman/listinfo/omd-users
