iptables: Index of insertion too big

This forum is only for reproducible bugs with csf and lfd (i.e. not iptables problems, lack of understanding how to use a feature, etc). Posts must be accompanied with full technical details of the problem and how it can be recreated. Any posts not adhering to this, or not considered bugs, will be moved to the General Discussion (csf) forum.
Post Reply
marcele
Junior Member
Posts: 215
Joined: 17 Sep 2007, 17:02

iptables: Index of insertion too big

Post by marcele »

On any newer servers I get this message when trying to start csf:

Starting csf:iptables: Index of insertion too big

Running Centos 5.2
uname -a
Linux 2.6.18-92.1.13.el5 #1 SMP 8 i686 i686 i386 GNU/Linux

iptables-1.3.5-4.el5
chirpy
Moderator
Posts: 3537
Joined: 09 Dec 2006, 18:13

Post by chirpy »

This indicates that iptables has been flushed. I would suspect that you are running TESTING mode, or some other cron job is flushing iptables chains, which will cause this problem while it is trying to insert a rule into a chain.
marcele
Junior Member
Posts: 215
Joined: 17 Sep 2007, 17:02

nope

Post by marcele »

Sorry this isn't the case. This is happening on our new Centos 5.2 installs .. I've verified that TESTING = "0" .. and there are no crons installed. This is happening on multiple machines. I'm a longtime csf user and never experienced this problem before.

Here is the csf.conf:
http://pastebin.com/m3037fdd4
chirpy
Moderator
Posts: 3537
Joined: 09 Dec 2006, 18:13

Post by chirpy »

I just tried your configuration on a CentOS v5.2 and didn't have any problems. If you're using a stock CentOS kernel (i.e. not a custom kernel) and can give me access to the server to investigate, please log a ticket on our helpdesk.
marcele
Junior Member
Posts: 215
Joined: 17 Sep 2007, 17:02

Very odd

Post by marcele »

Yes its very odd. I installed csf to a separate vm and don't have the problem at all. I'll open a ticket and you can login to one of the servers.
chirpy
Moderator
Posts: 3537
Joined: 09 Dec 2006, 18:13

Post by chirpy »

This was fixed in csf v4.11
Post Reply