Author Topic: Trace Logs  (Read 2036 times)

pankaj.puranik

  • Sr. Member
  • ****
  • Posts: 374
    • View Profile
Trace Logs
« on: February 19, 2016, 01:33:02 AM »
Hi

After having a few server crashes in our SIT environment, I switched on the trace logging by setting the value to the highest levet (INFO, FLOW, WARNING, ERROR, etc). The server did crash again. But on looking into the trace log (after converting it into readable format), I did not see any ERROR information. All I saw was INFO and FLOW messages.

Does anyone have any suggestions to find out what caused the server to Crash?
Note that the System Log also didn't give much information.

Thanks
Pankaj.

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2231
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: Trace Logs
« Reply #1 on: February 19, 2016, 03:56:21 AM »
What was the server doing before the crash?  Were there any specific jobs, queries, or users connected? 

You haven't given us platform/OS, software components, version numbers, or included any logs. 

If you want help with something so technical, you need to help us before we can help you!  :)

-JD.
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR

pankaj.puranik

  • Sr. Member
  • ****
  • Posts: 374
    • View Profile
Re: Trace Logs
« Reply #2 on: February 29, 2016, 05:44:44 AM »
 :) CMOD version 9.0.0.5
Operating System - Linux

There are multiple applications that access this CMOD server.
As per the trace log (looking at the time stamps), the last activity was a search query that passed in an account number and a date range.

I tried the same criteria again after bring the server up but the query did not cause a crash.
The point I am trying to make is why did the trace log didn't log any ERROR message at all in spite of the fact that the logging was set to the highest level (15).

Thanks
Pankaj.