Quoting Luis campo <lcr_2...@hotmail.com>:
The service is still active spamd just does not process the emails,
all giving a score of zero and then get the error message
ServerA spamc [7277]: connect to spamd on 172.16.0.14
> Failed, retrying (# 1 of 3): Interrupted system call
When this problem occurs restarted spamd and runs approximately 20
minutes and then switch back to the same problem.
Quoting Luis campo <lcr_2...@hotmail.com>:
The service is still active spamd just does not process the emails,
all giving a score of zero and then get the error message
ServerA spamc [7277]: connect to spamd on 172.16.0.14
> Failed, retrying (# 1 of 3): Interrupted system call
When this problem occurs restarted spamd and runs approximately 20
minutes and then switch back to the same problem.
Correct. When you restart the spamd proccess, it frees up memory that
was used. Once spamd gets running again, it starts taking up memory.
If you run out of memory, your server starts to swap. Once your server
starts to swap, things slow down dramatically. The amount of memory
each spamd process will take depends upon what rules you have loaded
and how many.
Here, our filter server (16Gb RAM) with spamd startup parameters:
--min-children=9 --max-children=36 --min-spare=9 --max-spare=18
has been running flawless with no issues for over a year. Each spamd
process on our filter server takes up aproximately 100meg.
