Question

Wordpress site is down and won't come back up

Posted August 14, 2014 2.3k views

My Wordpress site has gone down and will not reboot. The error is:

Error establishing a database connection

I’ve tried restarting from the console and UI, but no luck. I have a swap as well.

This isn’t the first time this has happened either, although it happened after a long time…

Any permanent solutions to this recurring and annoying problem???

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer

Apache logs:

root@farooqyousuf:~# tail /var/log/apache2/error.log
[Thu Aug 14 01:04:53 2014] [notice] caught SIGTERM, shutting down
[Thu Aug 14 01:05:03 2014] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.11 with Suhosin-Patch configured – resuming normal operations
[Thu Aug 14 01:10:13 2014] [notice] caught SIGTERM, shutting down
[Thu Aug 14 01:10:29 2014] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.11 with Suhosin-Patch configured – resuming normal operations
[Thu Aug 14 03:26:50 2014] [notice] caught SIGTERM, shutting down
[Thu Aug 14 03:27:01 2014] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.11 with Suhosin-Patch configured – resuming normal operations
[Thu Aug 14 03:29:25 2014] [notice] caught SIGTERM, shutting down
[Thu Aug 14 03:29:33 2014] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.11 with Suhosin-Patch configured – resuming normal operations
[Thu Aug 14 03:48:11 2014] [notice] caught SIGTERM, shutting down
[Thu Aug 14 03:48:28 2014] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.11 with Suhosin-Patch configured – resuming normal operations
root@farooqyousuf:~# tail /var/log/apache2/error.log

  • I did ‘less /var/log/mysql/error.log’ and got this:

    140814 1:10:13 [Note] /usr/sbin/mysqld: Normal shutdown

    140814 1:10:13 [Note] Event Scheduler: Purging the queue. 0 events
    140814 1:10:13 InnoDB: Starting shutdown…
    140814 1:10:13 InnoDB: Shutdown completed; log sequence number 1595705
    140814 1:10:13 [Note] /usr/sbin/mysqld: Shutdown complete

    140814 1:10:30 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
    140814 1:10:30 [Note] Plugin 'FEDERATED’ is disabled.
    140814 1:10:30 InnoDB: The InnoDB memory heap is disabled
    140814 1:10:30 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    140814 1:10:30 InnoDB: Compressed tables use zlib 1.2.3.4
    140814 1:10:30 InnoDB: Initializing buffer pool, size = 128.0M
    140814 1:10:30 InnoDB: Completed initialization of buffer pool
    140814 1:10:30 InnoDB: highest supported file format is Barracuda.
    140814 1:10:30 InnoDB: Waiting for the background threads to start
    140814 1:10:31 InnoDB: 5.5.35 started; log sequence number 1595705
    140814 1:10:31 [Note] Server hostname (bind-address): '127.0.0.1’; port: 3306
    140814 1:10:31 [Note] - '127.0.0.1’ resolves to '127.0.0.1’;
    140814 1:10:31 [Note] Server socket created on IP: '127.0.0.1’.
    140814 1:10:31 [Note] Event Scheduler: Loaded 0 events
    140814 1:10:31 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '5.5.35-0ubuntu0.12.04.2’ socket: ’/var/run/mysqld/mysqld.sock’ port: 3306 (Ubuntu)

Submit an Answer