Difference between revisions of "Error reporting"
Line 9: | Line 9: | ||
The next option, '''file''', allows you to choose a file in which you will store the logs. The path you will indicate there should be relative to the system root (/). If you live it as it is (default option dolibarr.log), it will likely be opened in several directories, depending on the directory you're executing the script from. Of course, to do that, your web server must have write permissions on the directory you are using. | The next option, '''file''', allows you to choose a file in which you will store the logs. The path you will indicate there should be relative to the system root (/). If you live it as it is (default option dolibarr.log), it will likely be opened in several directories, depending on the directory you're executing the script from. Of course, to do that, your web server must have write permissions on the directory you are using. | ||
+ | |||
+ | Generally, the '''file''' facility will work more easily because it doesn't depend on your server configuration (or only for the directory that needs to be writeable). | ||
Finally, the level of reporting is how many types of errors you want to report. LOG_DEBUG(7) is the strongest option, reporting pretty much everything that calls a dolibarr_syslog() function. LOG_EMERG(0) is the opposite, letting you see only the errors that would really block your system. | Finally, the level of reporting is how many types of errors you want to report. LOG_DEBUG(7) is the strongest option, reporting pretty much everything that calls a dolibarr_syslog() function. LOG_EMERG(0) is the opposite, letting you see only the errors that would really block your system. |
Revision as of 19:35, 23 August 2007
The error reporting module is integrated in the Dolibarr administration tool and allows you to configure what level of errors you would like to be reported and where.
To get to the error reporting module configuration page, go to Home, Configuration, Modules and use the configuration icon of the last module on the screen: System logs.
Of course, this module (System logs) must be activated for the following to work.
The facility option allows you to use pre-set facilities to log your errors. Facilities are a system-level feature to tell your syslog operator where this error comes from, to judge priority and all that. You can find more about this inside the PHP documentation for the openlog() function which is used inside the dolibarr_syslog() function: http://www.php.ne/openlog Really, you should leave it to LOG_USER unless you know exactly what you're doing.
The next option, file, allows you to choose a file in which you will store the logs. The path you will indicate there should be relative to the system root (/). If you live it as it is (default option dolibarr.log), it will likely be opened in several directories, depending on the directory you're executing the script from. Of course, to do that, your web server must have write permissions on the directory you are using.
Generally, the file facility will work more easily because it doesn't depend on your server configuration (or only for the directory that needs to be writeable).
Finally, the level of reporting is how many types of errors you want to report. LOG_DEBUG(7) is the strongest option, reporting pretty much everything that calls a dolibarr_syslog() function. LOG_EMERG(0) is the opposite, letting you see only the errors that would really block your system.
On a typical Linux install, the logs will then be available somewhere in /var/log/apache[2]/[dolibarr]-error.log. You can watch it live from the terminal by using:
tail -f /var/log/apache2/dolibarr-error.log