Command "visulox log" - Analyzing log files
OverviewLog files can grow, log files are in different places, log files contain previous errors. Therefore VISULOX log entries are provided via systemd / journalctl. The "visulox log" command allows to get all VISULOX related information in one place. |
Usage
./visulox log <options>The default behaviour is analyzing from last VISULOX service restart.
| Option | Description |
|---|---|
| -S | --since | Start date / time for logging If -S is used without the -U parameter: |
| -U | --until | End date / time for logging |
| -l | --loglevel | Loglevel: error, notice, info, debug (Default: info). |
| -f | --follow | Tailing log information on stdout |
| -t | --identifier | Show entries with the specified syslog identifier, e.g. transitzone, webservice, ... As root, use "journalctl SYSLOG_IDENTIFIER=" & press "TAB" to display a list o f all identifiers. |
For example
The default setting of the system logger is error. To display debug information within the visulox log command, the logger has to be set to debug.
Setting the logger to debug
visulox config -name logger.level
-------------------------------------------
| changed | key | value |
-------------------------------------------
| | logger.level | error |
-------------------------------------------
visulox config -name logger.level=debug
Show log entries on stdout
visulox log -loglevel debug -follow If log level of the system has not been set to debug, the visulox log command can not display debug information regardless of -loglevel setting.
Show error log entries for a given timeframe
visuloxlog-S "-10 minutes" -loglevel errorvisulox log -S "-2 days" -loglevel error visulox log -since "08:00" -until "12:00" -loglevel debug visulox log -S "Tue Jul 12 10:00:15 CEST 2022" -until "Fri Jul 15 10:42:15 CEST 2022" -loglevel errorFormat of log entries (examples)
| Date / Time | Node | Loglevel | Process | Log entry information |
|---|---|---|---|---|
2022-07-27 10:21:06.951562 | vT2OL7U2 | debug | stats.tcl(12146) | ::dataChanged tables=<global_vlxconfig> |
2022-07-27 10:23:33.878061 | vT2OL7U2 | debug | stats.tcl(12146) | <::coroutine::util::C772>::LicenseCount::create e=<No DataDict from dict> |
2022-07-27 10:27:56.987730 | vT2OL7U2 | info | objects2Portal.tcl(14374) | <::coroutine::util::C27>::AdminsToDatastore::runSingle e=<no datasources found,terminating secure Global Desktop> |
... |
If more detailed logs are needed, this can be done with journal.ctl commands directly.
In this case, please contact the VISULOX Support Team for more information.
Related information
Command "visulox support" - Creating a VISULOX Support Report