Common Errors at the front end of a Linux server and their meanings

Article Title: common errors at the front-end of a Linux server and their meanings. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.

Common Errors on the Linux Server front-end and their meanings

General class prompts

Eth1: Too much work at interrupt, IntrStatus = 0x0001

The meaning of this prompt is. A network card has too many interrupted requests. if it appears only once, it can be ignored. however, if this prompt appears frequently or appears in a centralized manner, there are many possibilities to be addressed .. There are many possibilities, such as NIC performance, server performance, and network attacks.

General class prompts

IPVS: incoming ICMP: failed checksum from 61.172.0.X!

The server receives an ICMP packet with a checksum and an error. This type of data packet may be generated illegally. However, the server currently receives a large amount of such data, which is generally ignored.

Generally, the proxy server forwards thousands of data packets every second during work. It does not affect normal operation if several error data packets are received. This is the most common type of prompt.

General class prompts

NET: N messages suppressed.

The server ignores N Packets. Similar to the previous prompt, the packets received by the server are considered useless junk data. This type of data is mostly produced by attack programs.

This prompt can be ignored if N is relatively small. However, if such a prompt appears frequently or for a long time, it is likely that the server is under a bandwidth attack like junk data.

General class prompts

UDP: bad checksum. From 221.200.X.X: 50279 to 218.62.X.X: 1155 ulen 24
UDP: short packet: 218.2.X.X: 3072 3640/217 to 222.16x.x: 57596
218.26.131.X sent an invalid ICMP type 3, code 13 error to a broadcast: 0.1.0.4 on eth0

The server receives an incorrect data packet, Which is UDP checksum and error, too short UDP data packets, and an incorrect ICMP data packet. This type of information is generally invalid. However, if the problem is not serious, you can ignore it directly.

General class prompts

Kernel: conntrack_ftp: partial 227 2205426703 + 13
FTP_NAT: partial packet 2635716056/20 in 2635716048/2635716075

An error occurs when the server maintains an FTP connection. Such a prompt can be ignored directly. Serious network communication problems!

NETDEV WATCHDOG: eth1: transmit timed out eth1: link down eth1: link up, 10Mbps, half-duplex, lpa 0x0000 eth2: link up, 100Mbps, full-duplex, lpa 0x41E1 setting full-duplex based on MII #24 link partner capability of 45e1

These prompts appear only when serious problems occur in network communication. the fault is basically related to network disconnection. these prompts indicate that data transmission times out for a certain network adapter, the network adapter is down, the network adapter is up, and the connection rate is 10/100 Mbps. the prompts for the last three lines written here are similar. when this type of prompt appears, you must pay attention to the network connection status for handling !!!

Serious network communication problems!

NIC Link is Up 100 Mbps Full Duplex

Situation and kernel: eth1: link up ,... same. the connection rate that a network card can adapt. it is generally considered that the network adapter is down, but the adaptive speed of the network adapter is also a communication problem. This type of information can be ignored if the network cable is disconnected normally.

Serious network communication problems!

Eth0: Transmit timed out, status 0000, PHY status 786d, resetting... eth0: Reset not complete yet. Trying harder.

The first prompt indicates that the NIC fails to send data. Reset the NIC. The second prompt indicates that the NIC is not successfully reset... These prompts are all serious communication problems.

[1] [2] Next page