Display Client Logs
- Xibo for Android
- Install a White Label or a different Player version on a DSCS9
- CEC Screen Power on/off with DSDevices DSCS9
- Hardware Recommendations (website?)
- Philips Signage SoC Monitors (website?
- Managing Storage on the Android Device
- Player Settings
- Players without an Internet Connection
- Remote Administration with SS Helper
- Restart Rooted Device with a Shell Command
- Rooting a Device
- Running Xibo for Android
- Resolving Common Issues
- Error shown when I try to licence my Player?
- Player not updating from the CMS?
- I can see my Licence entry but the Player appears unlicensed?
- Error message - Player is missing dependencies
- My scheduled Layouts are not working?
- Layout won't play? Splash screen plays?
- Watchdog error message
- Troubleshooting for Administrators
- Audit Trail
- Log Information
- Player Logs
- Getting the Player Status
- Can I use the Xibo name / logo?
- Can I run a Xibo Player on Raspberry Pi?
- How can I increase the upload file size limit?
- How do Players communicate with the CMS?
- How many displays can Xibo support?
- How do I reset the Xibo_admin account password?
- Power On/Off for Players
- Why do I need a Default Layout?
- Xibo for Android FAQ's
- Autoplaying Embedded Youtube Videos
- Closing to Home screen
- Displaying Images
- Embedded TV
- External SD card not listed when running Banana-Pi
- Helper Command to change Time zone
- HTML5 Video
- Memory Notifications
- Menu not accessible
- Orientation Settings for the DSDevices DSCS9 Player
- SSL Support
- Using Portrait Displays
- Video wont play properly
On this page
Display Client Logs
Log information for Players has been kept light to improve performance and stability. Player devices tend to be tight on memory and therefore applications are granted a limited amount of memory to use. As Xibo runs 24/7, memory usage is very important to us and generating lots of logging actually uses a lot of memory.
The type of logging available depends on the Player and can be set from within the Display Settings Profile, or overridden on the Display.
For example, in Android you would Edit Profile -> Troubleshooting Tab -> Log Level, and choose Error, Audit or Off.
If you’ve asked for support on Community or the Help Desk, and been asked for more logging you will almost always be asked for the most detailed level of logging, e.g. Audit.
Please note if you change the Player logs to Audit and want to see these in the CMS, you must enable troubleshooting on the Display - see below.
This is done on either the Display Settings Profile for your Player type, or in the Display Settings Override tab on Edit Display.
Once you have made a change to the log level, the Player will switch to that level the next time it connects to the CMS for its routine collection.
The easiest way to view Player logs is to have them sent to the CMS.
There are two types of log information for Players:
- messages sent to the CMS as “Error”
- messages sent to the CMS as “Audit”
As a rule of thumb, anything Error or above on the Player is sent as “Error” and anything below that is sent as “Audit”.
When received by the CMS Error messages are always written to the log, Audit messages are only written when the Auditing until fields have been configured for the Display .
To set Auditing logs, click on Displays from the CMS menu and use the row menu for the Display you wish to set auditing for.
Click on the Advanced tab and enter a date and time the Player should collect log information until.
Please note: This should not be set for too long a period which goes beyond the troubleshooting window.
Only the most important messages are logged.
Each Player can store log information and send them once reconnected to the CMS.
This means Players can run offline for an extended period of time without losing log information. The Player must be on-line to send its messages to the CMS.
The last 5 log messages are shown on the Player status screen which are useful for “immediate” debugging. These are removed as they are sent to the CMS. The status of each communication call to the CMS is also recorded for easy debugging.