MediaCP Manual
    1. Getting Started
    2. Sales Questions
    3. Frequently Asked Questions
    4. Transcoder System Benchmarks
    5. Start an audio streaming business
    1. Change account currency
    2. Product Licensing
    1. Introduction
    2. Installation & Upgrade
      1. System Requirements
      2. Versions & Releases
      3. Installation
      4. Upgrading
      5. Streaming Servers
        1. Nginx-Rtmp Video Server
        2. Flussonic Media Server
        3. Wowza Streaming Engine
      6. SSL Certificates
    3. Billing Integration
      1. WHMCS Integration Guide
    4. Migrate from other software
      1. Migrate from Centovacast
    5. Backup & Restoration
      1. Backup MediaCP
      2. Restore MediaCP
      3. Transfer to another server
    6. Administration
      1. Custom Web Service Configurations
      2. Reset Admin Password
      3. Port 80 / 443 Proxy
      4. MediaCP System Commands
      5. Change MediaCP domain name
      6. Move media to another hard disk
      7. Secure your server
    7. Scaling
      1. Scale with Wowza and CloudFront CDN
      2. Nginx-Rtmp with CloudFront CDN
    8. Troubleshooting
      1. Grant access to support team
      2. Troubleshooting Wowza Streaming Engine
      3. FTP Troubleshooting
      4. MySQL Database Troubleshooting
      5. Reporting Troubleshooting
      6. Troubleshooting Liquidsoap AutoDJ
    1. Introduction
    2. Administrators Dashboard
    3. System Configuration
      1. General
      2. Services
      3. Video Players
      4. Albums
      5. Email
      6. Plugins
      7. Statistics
      8. Backups
      9. Custom HTML
      10. Misc
    4. Customer Accounts
      1. Managing existing Customers
      2. Create a new Customer
      3. Deleting a Customer
      4. Login as another Customer
      5. Send email to Customer
      6. Reset Customer Password
    5. Reseller Accounts
      1. Reseller Plans
      2. Create a Reseller Account
    6. Media Services
      1. Creating a Media Service
      2. Deleting a Media Service
    7. Announcements
      1. Managing Announcements
      2. Creating Announcement
      3. Deleting Announcement
    8. Statistics
    9. Software Health
    10. Software Updates
    11. Email Templates
    12. API
    1. API Documentation
    2. Custom Domain Names
    3. Shoutcast 2 Admin Guide
    4. Wowza and Flussonic on same system
    5. Submit a feature request
    6. Wowza Custom Properties
    1. Shoutcast 2 Live Broadcasting
    2. DJ Priorities
    3. HTML5 Audio Player
    4. Broadcasting with AutoDJ
    5. Shoutcast 2 Premium
    6. Mount Points
    1. Ondemand Video Streaming
    2. Getting started with video streaming
    3. Relay & IP Camera
MySQL Database Troubleshooting

Last updated 3 days ago

Mysql Server Unreachable Error

This error refers to the database server being unavailable on the system. It is most likely that the process has stopped and is not running.

Generally this occurs when your system has run out of memory and the System Out Of Memory Management (OOM) process has stopped MySQL to save memory.

You can determine if the system OOM process has interfered by running the following on your system:

cat /var/log/messages* | grep 'Out of memory'


  1. Restart MediaCP database service using the following command as root in SSH:
    mediacp restart mysql
  2. Ensure that MediaCP is the only application running on the system.
    Other applications such as cPanel/WHM, Plesk will also consume CPU, Disk and Memory. We recommend that MediaCP is the only application on the system to ensure it runs fast and stable.

  3. Increase the amount of memory available to your system.
    You should consult the System Requirements documentation to ensure your system meets the Minimum Requirements, however you should also aim to meet the Recommended Hardware requirements.

Mysql Server will not start

If the MySQL Server is failing to start after issuing mediacp restart mysql, then you can attempt to start the process manually in your shell to expose any error messages:

/usr/local/mediacp/mysql/bin/mysqld --defaults-file=/usr/local/mediacp/mysql/my.cnf --user=mediacp --basedir=/usr/local/mediacp/mysql --datadir=/usr/local/mediacp/mysql/data --socket=/usr/local/mediacp/mysql/data/mysql.sock --log-error --skip-networking

Attempt repair of crashed tables

How do i know the tables have crashed

Common errors that you might see include:

  • General Error: 126 Incorrect key file for table ‘tablename‘; try to repair it
  • Table ‘tablename‘ is marked as crashed and should be repaired 

Why do database tables crash?

The major cause of the database corruption is the lack of free disk space on the server. Other possible causes of MySQL table crashes include operating system problems, power failures, hardware issues, unexpected MySQL server termination, data corruption due to external programs, etc.

How do i repair database tables?

You can attempt to repair the database tables by running the command below, however in some cases this might not resolve the problem (See section below What if i cannot repair the database?). Pay attention to the output in case there are errors:

/usr/local/mediacp/mysql/bin/mysqlcheck --protocol=SOCKET --socket=/usr/local/mediacp/mysql/data/mysql.sock --user=root --password= -A --auto-repair --all-databases

It might be required to restart MySQL, pay attention to the output in case there are errors:

mediacp restart mysql

Can MediaCP repair it for me?

Please contact us and our level 2 staff can complete this for you for a 1 hour service fee. Please note that the service fee will be charged regardless if the repair is successful, however we will help you restore or reinstall your MediaCP if a repair cannot be successful.

What if i cannot repair the database?

Unfortunately if the database has crashed and is not repairable then you will need to either:

Table of Contents