Skip to main content

Causes of Linux server down or server crash

Introduction

Major 4 types of Linux server down or crash issues. In this tutorial know why it's happened.



1) Common Error
The Network Problem 


The Network Problem is a major error. We are not sure where the problem, because you may appear in server-side or can be displayed on the client or may be in the any single place. Example Firewall rule issue, DNS issue. Cross check the Ethernet cable connected to your server or not broken Last you can check the network connections on your side and make sure that all network connections are okay.
Power Failure


Power Failure is a main situation observed many times. It’s happened when A server on a UPS should shut down gracefully when the UPS is going to run down. The minimal purpose of the UPS is to keep the server running long enough to do that. Check all the power cables connected to your server, because sometimes the cable may burn from overheating or short circuit.

2) Human Error
DOS Attack 
DOS means Denial of Services, In DDOS attacks, the Attacker installs software virus or trojan in damaged systems and uses them to flood the victim's network so that the victim's server can not handle.


As mentioned in this IP question is only the ip of the website or can we DDOS the URL of the victim. This will be the burden on the server that hosts the site. It leads to refuse. Eventually, the site may collapse.
High Server Workload 
High server workload is good for you. But when this turns into heavy traffic burden on the server, the server stops responding. Can not get another request from the client, ie the server goes down


Configuration Bug 
The status of the server and the application depends on the configuration, sometimes due to incorrect configuration of the application that is not accessible by the client. In this case, although the server is still alive, it seems to the client that the server is either down or crashes, because it has no access to the server.

3) Software Error
Operating system crash
Server operating system crash problems either due to a fault in the hardware component or because of conflicts in the performance of applications installed on the system. But if it is a virus problem and some critical part of the system has been destroyed by the virus then system need to be recovered or re-install the operating system.
Application Crash 
once could happen collapse the application that serves your client. There can be various causes of application failure.
As - resource depletion, computational or logical error, system overload, data corruption and more.



4) Hardware Error
Server Hardware Problem 
Like RAM, processor or hard drive that is causing the problem, but this is not the case. If it were true, every site would work perfectly well. The more you provide the memory space, it always seems low, as there is no limit to the popularity and the number of people trying to access your site. They sometimes fail causing the problem.




Thanks for being here.



Comments

  1. This comment has been removed by a blog administrator.

    ReplyDelete

Post a Comment

Popular posts from this blog

How to Speedup your WordPress site with Amazon CloudFront.

Introduction A WordPress performance is quite excellent . The number of WordPress plugins to handle performance is such evidence. But the easiest way to improve your user experience is to accelerate the entire WordPress website using CloudFront. This will help you not only improve site response time reduces the necessary infrastructure, reducing the load on the Web server, so you can reduce the total cost of the infrastructure works WordPress. CloudFront is actually a site can greatly help your site to respond to unexpected load when gained popularity. Today this post is to clarify the method of providing a reasonable standard configuration on the WordPress website or blog. How does CloudFront help? Amazon CloudFront is to improve the user's experience accessing the Web site in several ways: 1.  Anycast DNS is to ensure that customers are routed to the nearest edge location. 2.  The cached content is available to users at the edge position (i

Linux System : Free Employee Monitoring with Automatic Screenshots

Introduction :   A utomatic screen-shots  of Linux system directly import  on your web server with Linux samba server service and scrot command. 1)  Setup web panel UI on your web server :   Get web panel PHP/HTML code from Github URL: https://github.com/raj412/Employee-Monitoring-for-Linux-System It’s work in Linux server LAMP environment(no need database for this configuration ) Defult login username password is admin/1234. You can change username/passwrod from login.php file in line number #6 Login Page : Dashboard : Screenshot Page : 2)  Samba server configuration on web server : I.  Install Samba on your server where you setup Linux screenshot log system web panel. sudo apt-get update sudo apt-get install samba II.  Set a password for your user in Samba sudo smbpasswd -a <user_name> III.  Share gallery-images folder from you web panel. This is my web panel gallery-images p

How to control high traffic load on Apache servers : optimization performance of APACHE2 & PHP-FPM

Everyone handle high traffic loads  on Apache server. During down-time they forget to check server memory . Apache not used lot of memory  still server not responding. All time we restart Apache service and all things will start working good. I also faced same issue numerous time and all-time  used same solution : Restart Apache. After lots of research and reading found one solution. In this blog you see step-by-step guide to apache2 performance settings. System environment: Intel(R) Xeon(R) CPU 3.10GHz, 4 cores | 8GB RAM Ubuntu 16.04 Apache2 version using mpm_event PHP FPM (5.6,7.1) First,  Calculate process size : Download : python script file “ps_mem.py” from Github Open this and ps_mem.py file upload on you server :  https://github.com/raj412/ps_mem chmod a+x ps_mem.py sudo python ps_mem.py Output like this:  See here : 12 Apache processes, consuming a total of  35.7MiB, so each Apache process is using roughly 3MiB of RAM. The 42 php-fpm process u