Skip to main content

Error Establishing A Database Connection WordPress CentOS

Being novice to WordPress, but maintaining a Apache web server on CentOS 6.5 and maintaining a WordPress website.
Surprisingly it was not a database issue, but a DDoS attack!!!
After googling a lot related to MySQL database, i started monitoring my web server and found its CPU usage was becoming 100% by lot of Apache processes and after some time my server became unresponsive!!!

What I did…
Blocked HTTP access from
Allowed HTTP access to only my network Public IP.
Restarted the Server and found it was working like charm.

I again allowed access to and it again became unresponsive and the CPU utilization was 100% or sometimes with “Error Establishing A Database Connection”

My next step was obviously to look at which public IP is bombarding http requests to my Server.

To check http access logs, use the following command
cat /var/log/httpd/access_log

My CentOS server is hosted on Amazon Web Services, so there is no provision to block any single IP address with AWS security group, I had to block this culprit IP on the CentOS itself.

Here are the commands to block the IP on the CentOS linux with it native firewall
sudo iptables -I INPUT -s x.x.x.x/32 -j DROP

After adding your rules you’ll need to save them, and ensure the iptables service starts at boot.
sudo iptables-save > /etc/sysconfig/iptables-config


Popular posts from this blog

What is Cisco Supervisor Engine?

Supervisor Engine is a module that is installed in the Cisco Chassis-based Catalyst Switches or Routers. Supervisor engine contains nearly all the same components of a fixed Cisco Switches or Routers. These Supervisor engines come in a variety of different types with different functionalities and are installed in the Switches/Router Chassis as per requirements of the network types.

Benefits of Supervisor Engines
By installing Latest Supervisor Engines in your existing investments (Switches and Routers) you can scale system performance and integrate next-generation services into your Networks.
Within a single multilayer switch chassis, two supervisor modules with integrated route processors can be used to provide hardware redundancy. If an entire supervisor module fails, the other module can pick up the pieces and continue operating the switch.
The supervisor engine contains the following integrated daughter cards that perform forwarding and routing and provide the protocols supported …

GNS3 Docker Error while creating node: Docker has returned an error: Cannot connect to host docker:80

Error while creating node: Docker has returned an error: Cannot connect to host docker:80 ssl:False [No such file or directory]

After adding docker template for Alpine Linux in gns3, you get above mentioned message when you want to use alpine linux in GNS3.

To get rid of this message you have to install Docker by following below link
curl -fsSL | sh

If you do not have curl installed then instal curl first with below command.apt-get install curl
After installing Docker you need to add your user name in the docker group with the following command. $ sudo usermod -aG docker your_username

Verify if the docker service is started with following command$ service docker status
If docker is not started then start with following command $ sudo service docker start
Logout from GNS3 Virtual Machines and log back. Start gns3 and use alpine linux.

Telnet Client is Disabled Enable it to use it from this application

This is a Cisco Network Assistant (CNA) error when you want to telnet any Cisco Devices from within CNA.
Solution to remove this error is related to Windows 7 or Windows Vista. First of all you need to Add TELNET program from Control Panel, which by Default is not added in fresh installation of Windows 7.For adding and using Telnet Program in Windows 7, Click Start > Control Panel > Uninstall a Program > Turn Windows Features On and OFF > Scroll to TELNET and Select it > Press OK After Adding Telnet Program into the Windows 7 you need to Copy Telent.exe from C:\Windows\System32 folder and paste it to C:\Windows\SysWOW64\ Now you should not get the same error.