Database connection errors

  • Mark Cutting

    (@mcutting)


    9 years, 11 months ago

    Hi. I’ve started to get database connection errors – see below

    [19-Jun-2016 02:11:03] WARNING: mysqli_query(): MySQL server has gone away
    [19-Jun-2016 02:11:03] WARNING: mysqli_query(): Error reading result set’s header
    [19-Jun-2016 02:11:04] ERROR: System: (2) No such file or directory
    [19-Jun-2016 02:30:56] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [19-Jun-2016 02:31:21] 2. Trying to create backup archive …
    [19-Jun-2016 02:40:03] WARNING: mysqli_query(): MySQL server has gone away
    [19-Jun-2016 02:40:03] WARNING: mysqli_query(): Error reading result set’s header
    [19-Jun-2016 02:40:05] ERROR: System: (2) No such file or directory
    [19-Jun-2016 02:45:43] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [19-Jun-2016 02:45:57] 3. Trying to create backup archive …
    [19-Jun-2016 02:54:32] WARNING: mysqli_query(): MySQL server has gone away
    [19-Jun-2016 02:54:32] WARNING: mysqli_query(): Error reading result set’s header
    [19-Jun-2016 02:54:32] ERROR: System: (2) No such file or directory
    [19-Jun-2016 03:00:39] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [19-Jun-2016 03:00:40] ERROR: Step aborted: too many attempts!

    I’ve recently moved wp-config.php up one level for security reasons. Any ideas ? If I run the backup manually, it works fine, but not from wp-cron.

    Thanks

    https://ww.wp.xz.cn/plugins/backwpup/

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Contributor Daniel Hüsken

    (@danielhuesken)

    9 years, 11 months ago

    With WordPress Version did you use?

    Thread Starter Mark Cutting

    (@mcutting)

    9 years, 11 months ago

    Latest. With wp-config outside of web root – one level up

    Plugin Contributor Daniel Hüsken

    (@danielhuesken)

    9 years, 11 months ago

    WordPress Version ?

    Thread Starter Mark Cutting

    (@mcutting)

    9 years, 11 months ago

    Latest – 4.5.2

    Thread Starter Mark Cutting

    (@mcutting)

    9 years, 11 months ago

    Interestingly, if I run the backup from the admin console, it works fine – it seems to be an issue when running from the CRON. I have disabled wp-cron, and am using CRONTAB instead as below

    /usr/bin/php-5.6-cli -q /var/sites/c/domain_name/public_html/wp-cron.php

    Plugin Contributor Daniel Hüsken

    (@danielhuesken)

    9 years, 11 months ago

    Can you send me a deteiled log. I think we must go setp by step to see what goes wrong. Use http://docs.backwpup.com/article/48-sending-in-log-files-for-the-support for this.

    Frank9652

    (@frank9652)

    9 years, 11 months ago

    I also have the same Problem.

    Since 21th june I have the same problems like oldmankit with backups from two different Homepages from two differen Hosters.

    I don’t use Wordfence I’m using iThemes Security, after deactivating iThemes Security the problem still exist.

    Homepage 1
    5 Backups with 5 different Errormessages (PID)

    [21-Jun-2016 23:43:41] WARNUNG: Error while sending QUERY packet. PID=2598
    [22-Jun-2016 00:03:34] WARNUNG: Error while sending QUERY packet. PID=28768
    [22-Jun-2016 01:34:53] WARNUNG: Error while sending QUERY packet. PID=26925
    [22-Jun-2016 01:58:19] WARNUNG: Error while sending QUERY packet. PID=23441
    [22-Jun-2016 02:17:07] WARNUNG: Error while sending QUERY packet. PID=11798

    Homepage 2
    2 Backups with the same Errormessage

    [22-Jun-2016 00:20:07] WARNUNG: mysqli_query(): MySQL server has gone away
    [22-Jun-2016 00:20:07] WARNUNG: mysqli_query(): Error reading result set’s header

    [22-Jun-2016 02:19:07] WARNUNG: mysqli_query(): MySQL server has gone away
    [22-Jun-2016 02:19:07] WARNUNG: mysqli_query(): Error reading result set’s header

    I will also sendin the errorlogs.

    Frank

    kapelari.studio

    (@bkapelari)

    9 years, 5 months ago

    I have the same Problem on a few websites.
    I use a cron job to make a automated backup and save the zip file on a external FTP-Server.

    SYSTEM INFO
    BackWPup 3.3.4
    WordPress 4.7
    MySQL 5.5
    PHP 5.6

    Here the exact log:

    [03-Jan-2017 15:04:27] 1. Versuche, Backup zu erstellen …
[03-Jan-2017 15:04:27] Komprimiere Dateien als ZipArchive. Bitte habe einen Moment Geduld.
[03-Jan-2017 17:20:47] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 17:20:47] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 17:26:09] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 17:27:57] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 17:27:57] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 17:29:54] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 17:31:41] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 17:31:41] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 17:33:41] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 17:35:24] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 17:35:24] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 17:37:27] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 17:39:15] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 17:39:15] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 17:41:17] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 17:43:02] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 17:43:02] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 17:44:59] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 17:46:43] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 17:46:43] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 17:48:39] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 17:50:25] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 17:50:26] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 17:52:26] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 17:54:14] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 17:54:14] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 17:56:16] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 17:58:19] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 17:58:19] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 18:00:32] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 18:02:35] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 18:02:35] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 18:04:55] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 18:07:13] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 18:07:13] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 18:09:35] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 18:11:47] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 18:11:47] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 18:14:08] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 18:16:18] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 18:16:18] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 18:18:48] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 18:21:00] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 18:21:00] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 18:23:27] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 18:25:33] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 18:25:33] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 18:28:04] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 18:30:22] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 18:30:22] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 18:32:49] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 18:35:04] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 18:35:04] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 18:37:41] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 18:40:11] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 18:40:11] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 18:42:47] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 18:45:10] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 18:45:10] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 18:47:36] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 18:50:03] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 18:50:03] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 18:52:45] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 18:55:27] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 18:55:27] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 18:58:10] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 19:00:42] WARNUNG: mysqli_query(): MySQL server has gone away
[03-Jan-2017 19:00:42] WARNUNG: mysqli_query(): Error reading result set's header
[03-Jan-2017 19:03:38] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 19:22:51] WARNUNG: Auftrag durch Inaktivität von mehr als 5 Minuten neu gestartet
[03-Jan-2017 19:22:53] 2. Versuche, Backup zu erstellen …
[03-Jan-2017 19:25:46] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 19:30:52] WARNUNG: Auftrag durch Inaktivität von mehr als 5 Minuten neu gestartet
[03-Jan-2017 19:30:56] 3. Versuche, Backup zu erstellen …
[03-Jan-2017 19:33:43] WARNUNG: mysqli_ping(): MySQL server has gone away
[03-Jan-2017 19:54:56] WARNUNG: Auftrag durch Inaktivität von mehr als 5 Minuten neu gestartet
[03-Jan-2017 19:54:56] FEHLER: Schritt abgebrochen: zu viele Versuche!
[03-Jan-2017 19:54:56] FEHLER: Job mit Fehlern beendet in 17549 Sekunden. Um eine korrekte Ausführung zu gewährleisten, musst du die Fehler beheben.
    Anandaraj Balu

    (@anand000)

    9 years, 4 months ago

    I’m also have the same issue

    Warning: mysqli_query(): MySQL server has gone away in 

Warning: mysqli_query(): Error reading result set's header in 

Warning: mysqli_query(): MySQL server has gone away in 

Warning: mysqli_query(): Error reading result set's header in
Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Database connection errors’ is closed to new replies.