Troubleshooting: First steps when encountering errors in i-doit

When an error occurs in i-doit, the following steps help narrow down the cause and often resolve the issue independently.

Step 1: Check log files

Log files are the most important source of information when troubleshooting errors.

Log file	Path	Content
`exception_yyyy-mm-dd.log`	`<i-doit>/log/`	PHP errors and exceptions
`system.log`	`<i-doit>/log/`	General system messages
`ldap_yyyy-mm-dd.log`	`<i-doit>/log/`	LDAP sync log (logging must be enabled in the Admin Center)
`notifications_yyyy-mm-dd.log`	`<i-doit>/log/`	Notification log
`jdisc-import_yyyy-mm-dd.log`	`<i-doit>/log/`	JDisc import log (set logging to "Detailed")
`idoit_update_xx_yyyy-mm-dd.log`	`<i-doit>/log/`	Update log
`idoit_migration_xx_yyyy-mm-dd.log`	`<i-doit>/log/`	Migration log
`error.log`	`/var/log/apache2/`	Apache error messages (path varies depending on configuration)

The exception and error.log files are usually the best starting point.

Some errors only occur in the frontend and are not logged on the server side.

Before creating a support ticket, it is worth checking the Knowledge Base:

If the problem cannot be resolved independently, create a ticket at help@i-doit.com. The following information will speed up the process:

Error description: What exactly happens? What was expected? Is the error reproducible?
Screenshots of the affected areas and the error message
Log excerpts from the relevant log files (see Step 1)
System information:

Information	Where to find it
i-doit version	Administration > System overview
PHP version	Administration > System overview
MariaDB/MySQL version	Administration > System overview
Operating system	`cat /etc/os-release`
Add-on versions	Admin Center > Add-ons
Browser + version	Browser settings > About

The more complete the information, the faster support can help.

Related to