The Software Health Check provides some simple tests to ensure your server and MediaCP configuration is valid and all services are running optimally.
There are four statuses in total:
- INFO – Provides additional information on the test above the line.
- WARN – A configuration could be improved to provide better performance and/or stability.
- PASS – Test has passed successfully and there is no problem detected
- FAIL – The Test has failed and there is a problem.
Accessing Software Health
The Software Health check is available for Administrators and can be accessed from the side menu under the Administration menu item.
Checking PHP tests
All PHP configurations are automatically deployed when installing or updating the MediaCP so these tests should always PASS given there are no modifications made by the administrator.
Time accuracy and timezone
These tests are to ensure your system time is valid. If the system time is not accurate, even by 1 or 2 seconds, then some functions may not operate correctly. In some scenarios, particularly on virtual machines, the system time can fall behind.
Most operating systems come with automatic time synchronization utilities. If these tests fail, you should contact your server provider to check and solve the problem.
In previous versions of the MediaCP (many years ago) it was required to set the PHP timezone to match your server. It is now required that the PHP configuration timezone be set to UTC. All stored dates and times in the MediaCP operate by converting from or to UTC time, so it is crucial that this passes.
Checking MySQL tests
All MySQL configurations are automatically deployed when installing or updating the MediaCP so these tests should always PASS given there are no modifications made by the administrator.
If you are encountering database issues after an upgrade, upgrading your database may fix your issues.
DNS resolution converts domain names such as mediacp.net to either IPv4 or IPv6 addresses.
Fast DNS resolution is vital to the applications performance and stability. DNS resolution is used in numerous areas of the system for different reasons.
Should these tests fail, then there is a problem with your System/Server/VPS configuration and it is a problem that your server administrator or hosting provider will need to solve. You should lodge a ticket with your provider if you are unable to solve the problem.
Permissions on the content directory and temp paths are vital for the operation of the control panel. A common reason for this test to fail is if you have moved the Media Content Directory to a new location. Should these checks fail then you should ensure that all paths are owned by “mediacp” system user, for example:
chown mediacp:mediacp -R /usr/local/mediacp/;
chown mediacp:mediacp -R /usr/local/mediacp/content/;
Checking HTTP/S access to MediaCP
This test performs and simple HTTP request to your MediaCP application. It is a simple test to check connectivity from within your own system. Should this test fail, then it indicates that the MediaCP URL is unable to be accessed from within your own server. Typically the reasons would include:
a) A DNS resolution problem; or
b) A network/firewall problem, possibly relating to poor NAT configuration
In either scenario, it is likely that you will need to contact your server administrator or service hosting provider to solve the problem.
Checking CRON bitrate/historics
A test to ensure that the regular scheduled tasks are operating for the MediaCP application. Should this fail then you should ensure your cron application is running. On some systems if the load becomes too high, then cron service may fail and not restart. Contact your server administrator or service provider to ensure the cron service is running appropriately.
Checking Redis Service Status
A test to ensure that the redis service is running. Redis is used for its high performance running user sessions and caching of information. If redis is not working, it could prevent login to the system. If you experience redis issues please contact our helpdesk for support.
Checking Queue Manager Service Status
A test to ensure that the queue manager is operating for the MediaCP application. Should this fail then you should attempt to restart the queue manager with the following command:
/usr/bin/mediacp restart queue
If this fails to restart the queue, please contact our helpdesk so we can investigate the issue.
A test to ensure that SMTP is enabled and setup appropriately. If you see failures, you will need to authenticate the test email and use the link to test your SMTP server settings.
Wowza Streaming Engine
A series of tests to confirm the connection and authentication to the Wowza Streaming Engine application. Should these tests fail, please check:
- That the ports configured in the System Config -> Plugins -> Wowza Streaming Engine match the configuration from Wowza Streaming Engine Manager
- The authentication provided in System Config -> Plugins -> Wowza Streaming Engine is valid.
- Wowza Streaming Engine and Wowza Streaming Engine Manager services are online:
systemctl status WowzaStreamingEngine;
systemctl status WowzaStreamingEngineManager;
Flussonic Media Server
A series of tests to confirm the connection and authentication to the Flussonic Media Server application. Should these tests fail, please check:
A series of tests to check the installed Liquidsoap version and if it has been installed correctly. Upgrades and installations can easily fail as Liquidsoap has a large number of dependencies that can fail if your servers’ packages are not up to date.
If your installation has failed or you are running the incorrect Liquidsoap version, you will need to update your system packages then follow this guide to reinstall Liquidsoap.
Nginx-Rtmp is now reliant on the correct version of Liquidsoap to be installed for the TV stations to be installed. If you run into a version incompatibility, follow this guide to reinstall Liquidsoap.
Should FFMPEG configuration fail, then please contact MediaCP Support.