Parameters to check and the remedies
|1. Check if the service was down at the given time:||
zcat /var/log/mithi/mcs/mcs_monitoring.log.19.gz | grep down -i | grep -v swm
|2. Otherwise check get the other details||
zcat /var/log/messages.19.gz | grep "Oct 20 12:" zcat /var/log/maillog.19.gz | grep "Oct 20 12:" zcat /var/log/tomcat/catalina.out.19.gz | grep "Oct-20-2010_12:"
zcat /var/log/maillog.19.gz | grep "Oct 20 12:1" > maillog zcat /var/log/maillog.19.gz | grep "Oct 20 12:2" >> maillog
Similarly collect the messages and tomcat logs
|3. Check if service were stopped/restarted at the given time through GUI/Commandline||
zcat /mithi/mcs/modules/mithi-system/report/mcs_activity_events.log.19.gz | grep <service>
|4. Check if the disk was full at that time||
The services can be stopped by the disk space monitoring agent (runs twice a day) automatically to prevent data corruption when the disk gets full. An alert is raised to the administrator (postmaster account)
Click here to correct the disk space problem.
|5. No errors found in logs||
After checking all the logs if there is no data/error available for that particular time, then this may point to the environment issue like dns/network/connectivity issue.