[ERLEDIGT] Incoming Traffic wird nicht gemessen

[DaSilva]

Ich habe gerade entdeckt, dass ispCP bei mir keinen eingehenden Traffic mehr misst (ausgehend schon). Dieses Phänomen tritt auf, seitdem in der /var/log/ispcp/ispcp_network.log "iptables: Resource temporarily unavailable" steht.
Die /var/log/ispcp/ispcp-srv-traff.log ist 0 Byte groß.

iptables -L -n -v --line-number :

Quote:iptables -L -n -v --line-number
Chain INPUT (policy ACCEPT 413M packets, 29G bytes)
num pkts bytes target prot opt in out source destination
1 9458 811K fail2ban-ssh tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:22
2 106K 8275K fail2ban-sasl tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:25
3 635K 63M fail2ban-apache tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:80
4 732 54443 fail2ban-courierimap tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:143
5 2721 143K fail2ban-courierpop3 tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:110
6 6520 323K fail2ban-proftpd tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:21

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
num pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 362M packets, 93G bytes)
num pkts bytes target prot opt in out source destination
1 362M 93G ISPCP_OUTPUT 0 -- * * 0.0.0.0/0 0.0.0.0/0

Chain ISPCP_INPUT (0 references)
num pkts bytes target prot opt in out source destination
1 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:993
2 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:995
3 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:587
4 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:25
5 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:143
6 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:110
7 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:443
8 0 0 RETURN 0 -- * * 0.0.0.0/0 0.0.0.0/0

Chain ISPCP_OUTPUT (1 references)
num pkts bytes target prot opt in out source destination
1 1 40 tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp spt:993
2 1 40 tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp spt:995
3 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp spt:587
4 3008 285K tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp spt:25
5 3 385 tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp spt:143
6 3 182 tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp spt:110
7 248 208K tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp spt:443
8 8501 9600K tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp spt:80
9 79384 19M RETURN 0 -- * * 0.0.0.0/0 0.0.0.0/0

Chain fail2ban-apache (1 references)
num pkts bytes target prot opt in out source destination
1 635K 63M RETURN 0 -- * * 0.0.0.0/0 0.0.0.0/0

Chain fail2ban-courierimap (1 references)
num pkts bytes target prot opt in out source destination
1 732 54443 RETURN 0 -- * * 0.0.0.0/0 0.0.0.0/0

Chain fail2ban-courierpop3 (1 references)
num pkts bytes target prot opt in out source destination
1 2721 143K RETURN 0 -- * * 0.0.0.0/0 0.0.0.0/0

Chain fail2ban-proftpd (1 references)
num pkts bytes target prot opt in out source destination
1 6520 323K RETURN 0 -- * * 0.0.0.0/0 0.0.0.0/0

Chain fail2ban-sasl (1 references)
num pkts bytes target prot opt in out source destination
1 106K 8274K RETURN 0 -- * * 0.0.0.0/0 0.0.0.0/0

Chain fail2ban-ssh (1 references)
num pkts bytes target prot opt in out source destination
1 9412 808K RETURN 0 -- * * 0.0.0.0/0 0.0.0.0/0

Dies tritt auf, nachdem der Server neu gestartet wurde.

Außerdem gibt es über 400 leere ispcp_daemon-stdout.log und ispcp_daemon-stderr.log Dateien.

Was kann ich tun um das zu beheben?
Danke.