Changes

{{TemplateDocDevEn}}

{{TemplateDocDevEn}}

= Functions =

= Functions =

Following function allows to log informations in Dolibarr log file

Following function allows to log informations in Dolibarr log file

dol_syslog($message, LOG_DEBUG|LOG_INFO|LOG_WARNING|LOG_ERR);

<syntaxHighlight lang="php">dol_syslog($message, LOG_DEBUG|LOG_INFO|LOG_WARNING|LOG_ERR);</syntaxHighlight>

The log level is related to setup defined in module Syslog (see lower).

The log level is related to setup defined in module Syslog (see lower).

Following function can be used to add error information on screen. Usage must be reserved in never reached code.

Following function can be used to add error information on screen. Usage must be reserved in never reached code.

dol_print_error($db,texte);

<syntaxHighlight lang="php">dol_print_error($db,texte);</syntaxHighlight>

= Module Syslog =  

= Module Log Debug (also called Syslog) =  

The error reporting module is integrated with other Dolibarr modules. It allows you to configure what level of errors you would like to be reported and where.

The error reporting module is integrated with other Dolibarr modules. It allows you to configure what level of errors you would like to be reported and where.

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 DOL_DOCUMENT_ROOT/dolibarr.log), it will likely be opened in document directory. 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 DOL_DOCUMENT_ROOT/dolibarr.log), it will likely be opened in document directory. 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).

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 writable).

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 dol_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 dol_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

 

Note that you can have also find some technical PHP/Apache errors in apache log file (whatever is status/setup of this module). But this occurs only if there is a technical problem in your installation: On a typical Linux install, such logs will be available somewhere in '''/var/log/apache[2]/[dolibarr]-error.log'''. You can watch it ''live'' from the terminal by using:

<syntaxHighlight lang="bash">tail -f /var/log/apache2/dolibarr-error.log</syntaxHighlight>