Combined with the case to introduce the solution to the Linux server failure

Server problems are common, but if there is a problem with the server under the Linux system, I don't know if you will solve it. In fact, the servers are similar. The following tutorial will give you a case. Analyze how to solve the server failure problem in the case.

The server suddenly has a public network failure. Fortunately, there are two IPs, one public network, one internal network, and the internal network can be connected to the server through the internal network. Check the log, dmesg, found that there is such a:

Sep 9 14:34:36 slave kernel: NETDEV WATCHDOG: eth0: transmit timed out

/etc/init.d/network restart Network The service is restarted and it returns to normal.

Go to google to find information, and found that there is the same problem,

is a problem of intractable diseases, initially thought that the driver version is too low, but think about such a network card for Linux What is the standard, I can't think of it, add these two parameters, and solve the problem.

Method:

/boot/grub/menu.lst file, add

acpi=off noapic

at the end of the kernel kernel that is started. 1) acpi=off prohibits some advanced power management functions and has no effect on your application.

2) noapic changes the interrupt mode, and has no effect on the application.

If this problem occurs again, consider adding this parameter.

The possible solution is similar to other systems. I don't know if you have found this. However, this solution is still somewhat professional. If ordinary users don't understand it, it can be understood. Look at it a few times and try to understand it.