Wednesday, July 14, 2010


The cogserver.log can be found in the logs directory in the Cognos installation folder. One of the most common logs requested by support, it provides an entry point for the diagnosis. Though you can use the Log Console for dissecting the log, I am more comfortable viewing it using Wordpad or VIM. They are much more lightweight. Of course, they do not provide a quarter of the functionality provided by the Log Console (we will discuss Log Console in a later post).

Along with the cogserver.log, it is very important to pass the exact time that the error was seen. Also, if there are multiple installations and they are all logging to local files, it is important to pass all the cogserver.log files after renaming them properly. An architecture diagram or description can be attached for a better understanding of the problem.

Depending on the settings, you may find a cogserver.log.1 and a cogserver.log.2 and then a cogserver.log. Please send all of these files rather than just sending the cogserver.log. To avoid this confusion, analysts will usually ask you to send the zip of the logs folder. It would be a better idea to send the log folder after appropriately renaming it so that it is known which part of the architecture it came from.

For example:

If you increase the logging level, the cogserver.log will grow faster than usual. Also if you start IPF tracing for any component, it is usually directed to the cogserver.log. CAF related errors are usually posted to the cogserver.log file. If you get a CAF error, it will give you a code which you can search for in the cogserver.log.

The best way to get familiarized with the cogserver.log is to open it and go through it. A typical entry in the cogserver.log looks like this: 3672 2010-06-16 17:11:51.741 +5:30 BootstrapConfigurePublish na 0 Thread-16 DISP 6009 1 StartService dispatcherBootstrap Info DPR-DPR-1002 Successfully registered the dispatcher http://01hw265803:9300/p2pd in Content Manager.

Timestamp: 2010-06-16 17:11:51.741 +5:30
Logging Level: Info

Now try dissecting this entry: 3072 2010-06-21 11:50:15.806 +5:30 rsProcessStarter na 0 warpmta-ProcessManager-ProcessMgrThread DISP 6009 1 Start com.cognos.pogo.reportservice Info Start the BIBusTKServerMain with pid 4624.

The entries will look more or less the same. If you get any error code in Cognos Connection you can simply search for that error code around that timestamp when the error occured. Looking around that part you may find useful information which you can point out to support. I am sure they would not mind !

No comments:

Post a Comment