Web servers like Apache, Nginx and others use files to record errors encountered during the execution of a dynamic language or the server processes. Depending on the configuration of the server, these files may be accessible from the web opening a hole in your site to allow an attacker to gather sensitive information of your project, so it is highly recommended to delete them.
If you are a developer, you may want to check the latest errors encountered by the server before delete the log file, that way you can see where the application is failing and fix the errors. Note that a log file may have thousand of lines, so to prevent an overflow in the memory of the PHP interpreter the plugin limits the process to the latest %%SUCURI.ErrorLog.LogsLimit%% lines inserted in the log file.
The analysis of error logs is disabled, go to the Scanner Settings panel in the Settings page to enable it.
Note that if the log file is not empty but the table is, it means that the format of the logs used by the web server is not supported by the scanner, you can try to increase the number of lines processed though from here in case that other lines have a different format which is very common on servers with mixed configurations.
| Error Logs (%%SUCURI.ErrorLog.FileSize%%) | ||||
|---|---|---|---|---|
| Date Time | Type | Error Message | File | Line |
| No valid logs in the last %%SUCURI.ErrorLog.LogsLimit%% lines of the error log file. | ||||
| No logs so far. | ||||