Skip to end of metadata
Go to start of metadata

LoxBerry's Log Manager displays all logfiles generated by the system and the plugins. Even if the web interface of a plugin fails, you may find it's logfile here.
LoxBerry keeps track of all logfiles, and automatically deletes old logfiles, as well as very big ones.

Logfiles

LoxBerry provides own functions to the plugins, to generate and manage logfiles. On this tab you find all logfiles that were generated by this functions.

Every plugin has it's own section in Log Manager. Inside of the sections, a plugin may have different groups of logfiles. The left, colored column shows the highest severity that was logged in this log. If an info symbol is displayed, you can quickly read log important messages in that logfile.

If a plugin supports this feature, you directly can change the loglevel of that plugin on the top of it's section.

More Logfiles

All other logfiles, that are not created by LoxBerry's logging functions, are listed in this tab. Every plugin has it's own section. The date/time displayed is the last modification time of the log.

Apache Log

This tab directly opens the logfile of the Apache webserver. If the webinterface of a plugin fails (Internal Server Error), take a look at this logfile to find error messages of the plugin.

Further information

  • The loglevel can be changed in Log Manager, when the plugin supports LoxBerry's loglevel feature. If the plugin offers it's own logging functionality, check the plugin page for a loglevel setting.
  • On errors in a plugin, first change the loglevel to "Debug", and then retry the use-case. Please only submit logfiles in loglevel "Debug" to the plugin developer. After your test, switch back to "Errors".
  • All logfiles are automatically truncated or deleted by LoxBerry, if 
    • the filesize is too big,
    • the logfile is too old,
    • the disk space on the log folder (tmpfs = RAM disk) is below a threshold.
  • "Logfiles" tab:
    • The list shows logging sessions (the plugin is triggered to do something), not logfiles. Multiple sessions may write to the same logfile. You may see sessions in the logview, that do not exist anymore in it's logfile, as the logfile was truncated or deleted by the logfile maintenance.
    • The first column shows the highest severity a plugin writes to the log. On warnings and errors, an i symbol is displayed in the column, listing all important events in the log. For debugging purposes, please submit the full logfile to the developer.



  • No labels