Windows Player Watchdog
- Xibo for Android
- Install a White Label or a different Player version on DSDevices
- CEC Screen Power on/off with DSDevices
- Hardware Recommendations
- Philips Signage SoC Monitors
- 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
- 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
- Testing with Xibo
- 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
- SSL Support
- Using Portrait Displays
- Video wont play properly
On this page
Windows Player Watchdog
The Watchdog is an optional component which can be used to monitor the stability of the main application and restart it where necessary.
The Watchdog is installed into the same folder as the Windows Player during the Windows Player installation.
Configuration is managed though a configuration file located in the watchdog installation folder.
The contents of the file is as below:
<?xml version="1.0" encoding="utf-8" ?> <configuration> <configSections> <sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=22.214.171.124, Culture=neutral, PublicKeyToken=b77a5c561934e089" > <section name="XiboClientWatchdog.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=126.96.36.199, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" /> </sectionGroup> </configSections> <startup> <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" /> </startup> <applicationSettings> <XiboClientWatchdog.Properties.Settings> <setting name="ClientLibrary" serializeAs="String"> <value>C:\Users\username\Documents\Xibo Library</value> </setting> <setting name="PollingInterval" serializeAs="String"> <value>120</value> </setting> <setting name="Threshold" serializeAs="String"> <value>300</value> </setting> <setting name="ProcessPath" serializeAs="String"> <value>C:\Program Files\Xibo\XiboClient.exe</value> </setting> <setting name="LogFileName" serializeAs="String"> <value>log.xml</value> </setting> </XiboClientWatchdog.Properties.Settings> </applicationSettings> </configuration>
The important part of the above configuration file is the settings between the
The library location as configured in the Player.
How often the watchdog should check for application activity.
The threshold in seconds that the application has to be inactive before the watchdog will restart it.
The fully qualified pathname to the application EXE that should be monitored. This will be used to restart the application when it is detected as being inactive.
Log File Name
This is the name of the log file as configured in the Player that is being monitored. Downtime events and restarts will be added to the end of the usual error log.
Start with Windows
A short cut to the watchdog EXE should be created and added to the Windows start up program group in the Start Menu.