In short, this message is received because the nf_conntrack kernel maximum number assigned value gets reached.
The common reason for that is a heavy traffic passing by the server or very often a DoS or DDoS (Distributed Denial of Service) attack.
ATHK said: The common reason for that is a heavy traffic passing by the server or very often a DoS or DDoS
Aye, this. If your conntrack table is maxed the second your networking starts up, you're not going to get far after that. I would boot in single user mode and examine some logs. It's port 80 so check your web access logs for odd activity.
Comments
http://www.pc-freak.net/blog/resolving-nf_conntrack-table-full-dropping-packet-flood-message-in-dmesg-linux-kernel-log/
https://major.io/2014/01/07/nf-conntrack-table-full-dropping-packet/
If you can't access the server via SSH or the serial console, shut it down until whatever it is passes...
Aye, this. If your conntrack table is maxed the second your networking starts up, you're not going to get far after that. I would boot in single user mode and examine some logs. It's port 80 so check your web access logs for odd activity.
Well, that's quick.
Ninja.