Debugging

When troubleshooting or collecting diagnostic information, it’s often necessary to enable the most verbose logging available. For OnixS-based applications, the most reliable way to do this is by setting the logging environment variables at launch time.

This approach forces the logging subsystem to run at the requested verbosity, and it overrides any logging configuration defined inside the application.

To enable full logging and direct syslog output to standard error, run the application like this:

Linux:

ONIXS_SYSLOG_LEVEL=5 ONIXS_SYSLOG_LOG_TO_STD_ERR=ON ONIXS_LOG_LEVEL=5 ./onixs_based_app

Windows:

$env:ONIXS_SYSLOG_LEVEL="5"; $env:ONIXS_SYSLOG_LOG_TO_STD_ERR="ON"; $env:ONIXS_LOG_LEVEL="5"; .\onixs_based_app.exe

Note: Any sensitive user data (for example, passwords) is scrambled in the logs.

Note: The application logs location is defined by OnixS::ICE::BOE::SessionSettings::storageDirectory.

OnixS-based applications can write diagnostic messages to the host logging system. Use the steps below to collect logs for troubleshooting:

Linux:

journalctl -t OnixS > ./onixs_events.log

Windows:

Get-WinEvent -FilterHashtable @{ LogName='Application'; ProviderName='OnixS' } | Select-Object TimeCreated, Id, LevelDisplayName, Message | Export-Csv -NoTypeInformation -Encoding utf8 .\onixs_events.csv