System Health Check

MyQ performs registered checks which can return error messages with their level of severity and they can be viewed in the system health check. The errors concern database health, disk space availability, PIN length settings, time zone configuration, etc.

Every error message is logged in the MyQ main log.

When the error message has a Critical severity, the related MyQ service is stopped and the administrator gets an email notification about it.

To access the system health check overview, log in as admin to MyQ and go to MyQ, System Health Check or click on the system health check button on the top-right side of the window.

Click Run to trigger the System health check Task schedule to perform a check.

Click Show hidden to view any hidden checks on the list.

Click Scheduled task to open the System Health Check task in Task Scheduler, where you can view and modify it.

Error codes and their severity are listed in the table below.

Code	Severity	Description
101	High	Main database health is not good; multiple messages can appear in the log
102	High	Log database health is not good; multiple messages can appear in the log
103	Medium	PIN length needs to be increased; see Generating PIN
104	High	Disk space is on warning level; see Disk space checker
105	Critical	Disk space is on critical level; see Disk space checker
106	High	Time zones misconfiguration; see Time zone
107	Medium	Queue(s) has an error
108	Medium	Obsolete terminal version
109	High	MyQ Server is not responding to HTTP requests. HTTP Server or HTTP router will be restarted (if the option is enabled in the config.ini)
110	High	MyQ Server is not responding to HTTP requests in a reasonable time
111	High	Terminal package(s) does not respond to health check request
112	High	At least one service is not running
113	High	The logon account of at least one service doesn't match the configured account
114	Medium	Database password is default
115	Medium	Administrator password is default