[ERLEDIGT] fail2ban und iptables

[vbbaby]

OK das Problem scheint hier wohl doch auch etwas anderes zu sein

Habe nun im Maillog folgendes gefunden:

Quote:Feb 7 14: tpd[9349]: disconnect from unknown[83.4.193.36]
Feb 7 14: tpd[9349]: connect from localhost[127.0.0.1]
Feb 7 14: tpd[9349]: lost connection after CONNECT from localhost[127.0.0.1]
Feb 7 14: tpd[9349]: disconnect from localhost[127.0.0.1]
Feb 7 14: tpd[9349]: connect from localhost[127.0.0.1]
Feb 7 14: tpd[9349]: lost connection after CONNECT from localhost[127.0.0.1]
Feb 7 14: tpd[9349]: disconnect from localhost[127.0.0.1]
Feb 7 14: tpd[9349]: connect from fmmailgate01.web.de[217.72.192.221]
Feb 7 14:ster[5820]: warning: master_spawn: fork: Cannot allocate memory -- throttling
Feb 7 14: ge repeated 3 times
Feb 7 14:gr[5822]: warning: connect to transport amavis: No such file or directory
Feb 7 14:ster[5820]: warning: master_spawn: fork: Cannot allocate memory -- throttling
Feb 7 14:ge repeated 4 times
Feb 7 14:gr[5822]: warning: connect to transport amavis: No such file or directory
Feb 7 14:ster[5820]: warning: master_spawn: fork: Cannot allocate memory -- throttling
Feb 7 14:37:34 h1307630 postfix/master[5820]: warning: master_spawn: fork: Cannot allocate memory -- throttling
Feb 7 14:37:38 h1307630 courierpop3login: fork: Cannot allocate memory
Feb 7 14:37:42 h1307630 postfix/master[5820]: warning: master_spawn: fork: Cannot allocate memory -- throttling
Feb 7 14:37:56 h1307630 last message repeated 2 times
Feb 7 14:38:02 h1307630 postfix/qmgr[5822]: warning: connect to transport amavis: No such file or directory
Feb 7 14:38:17 h1307630 postfix/master[5820]: warning: master_spawn: fork: Cannot allocate memory -- throttling
Feb 7 14:38:56 h1307630 last message repeated 4 times
Feb 7 14:39:02 h1307630 postfix/qmgr[5822]: warning: connect to transport amavis: No such file or directory
Feb 7 14:39:17 h1307630 postfix/master[5820]: warning: master_spawn: fork: Cannot allocate memory -- throttling
Feb 7 14:39:56 h1307630 last message repeated 4 times
Feb 7 14:40:02 h1307630 postfix/qmgr[5822]: warning: connect to transport amavis: No such file or directory
Feb 7 14:40:15 h1307630 postfix/anvil[6115]: statistics: max connection rate 3/60s for (smtp:83.31.5.77) at Feb 7 14:30:29
Feb 7 14:40:15 h1307630 postfix/anvil[6115]: statistics: max connection count 1 for (smtp:83.31.5.77) at Feb 7 14:30:23
Feb 7 14:40:15 h1307630 postfix/anvil[6115]: statistics: max cache size 3 at Feb 7 14:30:32
Feb 7 14:40:17 h1307630 postfix/master[5820]: warning: master_spawn: fork: Cannot allocate memory -- throttling
Feb 7 14:40:56 h1307630 last message repeated 4 times
Feb 7 14:41:02 h1307630 postfix/qmgr[5822]: warning: connect to transport amavis: No such file or directory
Feb 7 14:41:17 h1307630 postfix/master[5820]: warning: master_spawn: fork: Cannot allocate memory -- throttling
Feb 7 14:41:56 h1307630 last message repeated 4 times
Feb 7 14:42:02 h1307630 postfix/qmgr[5822]: warning: connect to transport amavis: No such file or directory
Feb 7 14:42:17 h1307630 postfix/master[5820]: warning: master_spawn: fork: Cannot allocate memory -- throttling
Feb 7 14:42:42 h1307630 last message repeated 3 times
Feb 7 14:42:44 h1307630 courierpop3login: fork: Cannot allocate memory
Feb 7 14:42:56 h1307630 postfix/master[5820]: warning: master_spawn: fork: Cannot allocate memory -- throttling
Feb 7 14:43:02 h1307630 postfix/qmgr[5822]: warning: connect to transport amavis: No such file or directory
Feb 7 14:43:17 h1307630 postfix/master[5820]: warning: master_spawn: fork: Cannot allocate memory -- throttling
Feb 7 14:43:56 h1307630 last message repeated 4 times
Feb 7 14:44:02 h1307630 postfix/qmgr[5822]: warning: connect to transport amavis: No such file or directory
Feb 7 14:44:17 h1307630 postfix/master[5820]: warning: master_spawn: fork: Cannot allocate memory -- throttling

Wie kann ich nun feststellen, warum hier kein Speicher mehr vorhanden ist ?
Diese Abstürze habe ich öfter und ich konnte bisher nicht feststellen, welche Anwendung hier den Speicher vollmacht....