Understanding Your Logs
From OpenIndivo Documentation Wiki
Contents |
Indivo Server
indivo.log
catalina.out
localhost.log
Indivo PHP UI
php_errors.log
Description
This log captures most errors encountered when executing PHP code. As the PHP codebase grows more stable, this log should stay pretty empty.
Configuration
This log is configured in your php.ini file. By default, we expect your configuration to contain values like these:
error_reporting = E_ALL & ~E_NOTICE log_errors = On error_log = "c:\php\log\php_errors.log"
Naturally, that last one should reflect your particular deployment of PHP. On our Linux systems, we typically generate the PHP error log in a directory below our web root, /var/www/log/, or just in /var/log/.
Sample Output
The contents of this file will look like:
[29-Sep-2006 13:14:33] Log_mail: Failure executing mail() [29-Sep-2006 13:14:33] PHP Fatal error: Uncaught [o(Exception):"java.lang.Exception: Invoke failed: [o(TalkClientImpl)]->readDocumentHeaders((String)null, (String)o(String), (String)o(String), (boolean)o(Boolean)). Cause: org.indivo.client.ActionNotPerformedException"]
php-java-bridge.log
Description
All Java code run through the PHP-Java Bridge has its System.out and System.err streams redirected to this log.
Configuration
This log is also configured in your php.ini file. By default, we expect the [java] section of your configuration to contain values like these:
[java] ... java.log_file = "C:\php\log\php-java-bridge.log" java.log_level = 2
On our Linux systems, we like to set our log_file value with the same directory as php_errors.log for convenience.
Sample Output
The contents of this file will look like:
log4j:WARN No appenders could be found for logger (org.indivo.client.TalkClientImpl). log4j:WARN Please initialize the log4j system properly. ObjectCache instantiated Cleaned ObjectCache of 0 old items.
UI Logging Database
Description
The Indivo UI logs all its operations to the 'log' table in your MySQL database. This is where the overwhelming bulk of your UI logs will appear (at least while it's running at the PEAR_LOG_DEBUG level), and should be the first place to look if you're having problems.
Configuration
The 'log' table is created as part of UI Installation, and your Indivo PHP API must be configured properly to use it.
