MySQL Error 1078 ER_GOT_SIGNAL is raised when the server thread receives an unexpected operating-system signal and aborts the current operation, often crashing the session or server.
MySQL Error 1078 ER_GOT_SIGNAL happens when the server gets an unexpected OS signal (for example SIGTERM, SIGSEGV) and aborts the thread. Check the MySQL error log, identify the signal source, repair any corrupted tables, and restart the server to clear the condition.
%s: Got signal %d. Aborting!
The message “Got signal X. Aborting!” means the MySQL server thread intercepted an operating-system signal while running SQL.
Signals such as SIGINT, SIGTERM, SIGSEGV or SIGABRT force the thread to stop, so the server surfaces error 1078.
The error appears during long-running queries, ALTER TABLE, bulk INSERT or online backup if the OS, an administrator or the kernel sends a fatal signal to the mysqld process or its worker thread.
Signals indicate crashes, out-of-memory kills or manual KILL commands.
Ignoring them risks data loss, table corruption and prolonged downtime, so immediate diagnosis is critical.
External KILL commands, kernel OOM reaper, faulty hardware, buggy storage engines, or misconfigured scripts can all generate fatal signals that MySQL relays as error 1078.
First inspect the MySQL error log to learn the exact signal number and timestamp. Next locate the source process in syslog or dmesg. Repair any affected tables with CHECK TABLE ...
REPAIR or mysqlcheck, then restart mysqld.
If the kernel OOM killer terminated mysqld, add RAM or set vm.overcommit parameters. If a DBA ran KILL -9, switch to graceful KILL QUERY. For SIGSEGV from a plugin, update or disable the plugin.
Monitor memory, avoid kill -9, patch storage engines promptly, and use the InnoDB crash recovery settings.
Galaxy’s query history helps roll back risky commands before they need to be killed.
Errors 2013 (Lost connection) and 1194 (Table is crashed) often accompany ER_GOT_SIGNAL. Diagnose them with the same log and repair approach.
.
A system administrator or automation script sends SIGKILL to mysqld or its thread, instantly aborting execution.
Low memory prompts the Linux kernel to terminate mysqld with SIGTERM or SIGKILL, producing error 1078.
Bad RAM, disk I/O errors or kernel bugs trigger SIGSEGV or SIGBUS, which propagate to MySQL.
A segmentation fault inside a third-party plugin sends a fatal signal that the server converts to ER_GOT_SIGNAL.
.
Check the MySQL error log. It includes the signal number and sometimes the process ID that sent it.
No. Even without a crash, the aborted thread might leave partial writes or table locks. Always investigate.
Not always. A manual kill -9 can raise the error without data damage, but you must still verify integrity.
Galaxy’s editor shows query run-time and lets you cancel long queries gracefully, avoiding OS-level kills that generate ER_GOT_SIGNAL.
.avif)
.avif){kind=logo}
