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 0.0.0.0/0
Allowed HTTP access to only my network Public IP.
Restarted the Server and found it was working like charm.

I again allowed access to 0.0.0.0/0 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

Comments

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 https://get.docker.com/ | 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.

a file I/O error has occurred while accessing vmware converter

While converting physical Windows 7 machine to Virtual machine of infrastructure type, I got this error. The error seems it is unable to read/write source or destination datastore.

I have installed VMware-converter-en-6.2.0-8466193 on Windows 7 physical machine with option locally selected. (not at server/client option)

All of my ESXi servers are connected to the vCenter Server, so I had to use vCenter Server's IP address to send this physical machine to the virtual world.

The issue i found was with the dns resolution to the vCenter Server's hostname. Since I am not using the same dns server on the Windows 7 client machine. So I updated the host entries manually for the vCenter Server's hosname to it IP address.

After adding dns eteries to the hostfile of windows 7, I am not getting this "a file I/O error has occurred while accessing vmware converter" and the migration has started.