of common failures and their solutions

  • 2020-06-12 11:31:01
  • OfStack

The server supports the information data of the whole enterprise, which is of vital significance to the information storage, business development, normal operation and other links of the company. However, in the daily operation of the server, due to its complex hardware structure, tedious operation principle, there are often a number of large and small problems troubling you. The following carefully collate 1 server common problems summary, to help you troubleshoot.

1. System blue screen, frequent crash, restart and slow response speed

The server is very similar to our normal computer, whether it is hardware structure or running system. Therefore, just like our computer 1, 1 May be infected with a virus. It will also crash due to system vulnerabilities, software conflicts, hardware failures, blue screen, restart and other failures. It will also be sluggish due to too much junk cache information.

2. Remote desktop connections exceeded the maximum number of connections

Since the server allows two connections by default, if you forget to log out and turn off the remote desktop, the server knows whether to log in or stay on the server. The most common way this happens is to restart the server, but if it is at peak times, the cost of restarting the server is obvious. At this point, you can use the mstsc/console instruction to force the login. Open the "run" box, type in "mstsc/v: xxx. xxx. xxx. xxx IP (server)/console", can be forced on to the remote desktop.

3. How to clean the files that cannot be deleted

In this case, it may be that the file is still running, so you can restart to delete it, or run CMD, enter the name of the folder that ES24en-ES25en-ES26en-ES27en-ES28en wants to delete, and finally enter the name of the folder that del wants to delete, after running this command, you can not recover, please use with caution.

4. Hidden trouble of system port

For the server, the first guarantee of stability and security. Therefore, we only need to guarantee the most basic functions of the server, just like the sound card is disabled by default. We don't need too much functionality, and we don't need too much port support. Like 1 some unnecessary, and higher risk ports can be blocked. For some necessary and risky ports, such as 3389, 80, etc., we can modify the registry to set it to a non-special secret port, so that the security risks of the server port will no longer exist.

Common server failures and corresponding solutions

Server 1 is rarely a problem, once a problem, how to actively rescue? We can't just sit there and wait, because if the server goes down, all the websites on that server won't open. For an enterprise, the website is their lifeblood, the loss is huge. It was also devastating for SEOER, which managed to appear on the front page of the search engine only to disappear due to a server failure. The following site to Hong Kong server rental and Hong Kong server hosting experience to tell you the three main reasons for the basic server failure and how to solve?

1. In the case of server network card, please check the usage of your server first.

1. Whether the utilization rate of CPU is more than 50%.

2. Whether memory usage is too high.

3. Whether the network utilization rate is too high.

If this occurs, it indicates that your server or network cannot host your current service, please contact a technician to adjust your resources. If the above situation does not occur, it may be caused by:

1. As a result of CC attack on the server, it is necessary to contact after-sales staff to make CC protection policy.

2. The server encountered a large traffic attack, but the server was not attracted by the traffic.

3. Equipment network card fault, network cable fault, upper switch fault. Before the failure, you can test the adjacent ip of your server. If the adjacent ip also suffers packet loss, it means that the upper switching equipment fails.

4. Computer room network failure, which will be a large-scale failure.

In the case of a server card, 1 general performance:

1, the server seriously lost packet, normal server loss rate is 0%, if the loss rate is higher than 1% will appear in the case of card.

2, some users card, some users do not card, may be caused by hardware firewall, part of the link blockage.

3. In addition, the above situation may also be caused by the failure of Internet nodes.

In case of a card, please make the following judgment in order to accurately determine the fault of the technology

1. Please first check whether your local network is normal. If it is not a local network problem, it may be a server failure. Local network detection method: ping test your server, while some other sites to synchronize ping test, if your server seriously lost packets, other servers do not lose packets, then the fault is in your server.

2. Confirm whether your server has non-card users. Generally speaking, all or some customer CARDS. Specific card user is which side of the user.

2. The server is unable to connect the following possible situations:

1. Due to the large traffic attack, the server was pulled by the traffic.

2, server hardware damage, resulting in server crash or shutdown.

3. Network interruption or inability to enter the operating system due to incorrect configuration of the server.

4. The system was damaged by hackers.

5. Fault of upper switching equipment.

6. Computer room network failure. The test method is similar to a network card.

In a word, server failure is an emergency, no one can predict, as long as to prevent and monitor, pay attention to the above problems and then find the appropriate solution can eliminate the loss caused by the failure.

The site the site (note: the server can't remote can ping ip test server is online, if you have back means that the server network is normal, may be the problem of machine (if the server is not forbidden ping), 1 kind for assistance, contact room for high traffic sites suggested more machine backup, a problem or temporary replacement.


Related articles: