Tripleplay MySQL error 2002

Identify and locate the Tripleplay server or player hardware

The MySQL instance runs on the Tripleplay server (or on the player itself if it's a self-contained unit). You need physical or remote access to it.

• Locate the Tripleplay server/PC/appliance serving the 1st floor — typically in an AV rack, comms room, or IT cupboard on or near the 1st floor.
• Confirm the device is powered on and has not frozen — check for fan noise, drive activity lights, or a display output.
• If the device has a screen and keyboard, proceed locally. If it's headless, connect via Remote Desktop (RDP) or SSH using administrator credentials.

Check whether the device shut down cleanly or is in a fault state

An unclean shutdown during a power outage can leave MySQL in a locked or corrupt state.

• Check the Windows Event Viewer (if Windows): Start → Event Viewer → Windows Logs → Application/System. Look for critical errors around the time of the outage.
• On Linux: runsudo journalctl -xeor check/var/log/syslogfor MySQL crash entries.
• Note any disk errors or filesystem warnings — these must be addressed before starting MySQL.

Restart MySQL via Windows Services (Windows OS)

If the Tripleplay server runs on Windows, use the Services panel to restart MySQL.

• PressWin + R, typeservices.mscand press Enter.
• Scroll to findMySQLorMySQL80(or similar version). Check its status — it will likely showStopped.
• Right-click the MySQL service and selectStart. Wait for the status to change toRunning.
• Once running, return to the Tripleplay display and check if the error has cleared.

Restart MySQL via command line (Windows or Linux)

Alternatively, or if the Services panel is unavailable, restart MySQL from an elevated command prompt or terminal.

• Windows— open Command Prompt as Administrator:

• Linux (systemd)— open a terminal with sudo access:

• Confirm the status showsactive (running)before testing Tripleplay.

Check MySQL error logs for the specific failure reason

MySQL logs tell you exactly why the service won't start — essential before attempting any repair.

• Windows:CheckC:\ProgramData\MySQL\MySQL Server X.X\Data\[hostname].err
• Linux:Check/var/log/mysql/error.logor runsudo journalctl -u mysql -n 50
• Look for phrases like"InnoDB: Database was not shut down normally"or"crashed table"— these confirm an unclean shutdown from the power loss.

Attempt InnoDB crash recovery (if log indicates unclean shutdown)

MySQL can often self-recover from an unclean shutdown using its built-in InnoDB recovery mode.

• Open the MySQL configuration file:my.ini(Windows) or/etc/mysql/my.cnf(Linux).
• Under the[mysqld]section, add the following line:

• Save the file and attempt to start MySQL again (step 3 or 4).
• If MySQL starts successfully,immediately take a full database backup, then remove theinnodb_force_recoveryline and restart MySQL normally.
• If recovery level 1 fails, increase to 2, then 3 — but do not go above 3 without guidance from Tripleplay support, as higher values risk data loss.

Set MySQL to start automatically on boot

Even once resolved, prevent recurrence by ensuring MySQL is configured to auto-start on system boot.

• Windows:Inservices.msc, right-click MySQL → Properties → set Startup type toAutomatic.
• Linux:

• Confirm by checking the service startup type is now set to Automatic before closing.