At some point, SA stopped filtering spam. I looked into it, I found spamd not running: coal ~ # ps -eaf | grep spam root 5702 472 0 07:14 pts/7 00:00:00 grep spam so I tried to start it: coal ~ # /etc/init.d/spamd start * Starting spamd ... Could not create INET socket on 127.0.0.1:783: Address already in use (IO::Socket::INET: Address already in use) * Failed to start spamd strange. So I looked to see what was using port 783: coal ~ # fuser -n tcp 783 783/tcp: 6967 coal ~ # ps -eaf| grep 6967 jake 6967 1 0 Aug02 ? 00:00:27 /usr/sbin/famd -T 0 -c /etc/fam.conf I looked around, and I found absolutely no mention of this anywhere, which is somewhat strange. I think the answer is to change the port SA is using, which is no big deal. Reproducible: Always Steps to Reproduce:
This is a local config problem, not a package problem. I have both running quite nicely without reconfiguring either, futzing with anything, etc. By default fam is listening on 642. ps -ef | grep am|grep -v grep: root 9794 1 0 04:02 ? 00:00:00 /usr/sbin/famd -T 0 -c /etc/fam.conf root 26748 1 0 09:58 ? 00:00:00 /usr/sbin/spamd -d -r /var/run/spamd.pid -m 5 -c -H root 26750 26748 0 09:58 ? 00:00:00 spamd child root 26751 26748 0 09:58 ? 00:00:00 spamd child root 26752 26748 0 09:58 ? 00:00:00 spamd child root 26753 26748 0 09:58 ? 00:00:00 spamd child root 26754 26748 0 09:58 ? 00:00:00 spamd child fuser -n tcp 642 here: 642 642/tcp: 9794 root # ps -ef | grep 9794 root 9794 1 0 04:02 ? 00:00:00 /usr/sbin/famd -T 0 -c /etc/fam.conf root # fuser -n tcp 783 here: 783 783/tcp: 26748 26750 26751 26752 26753 26754 root # ps -ef |grep 26748 root 26748 1 0 09:58 ? 00:00:00 /usr/sbin/spamd -d -r /var/run/spamd.pid -m 5 -c -H root 26750 26748 0 09:58 ? 00:00:00 spamd child root 26751 26748 0 09:58 ? 00:00:00 spamd child root 26752 26748 0 09:58 ? 00:00:00 spamd child root 26753 26748 0 09:58 ? 00:00:00 spamd child root 26754 26748 0 09:58 ? 00:00:00 spamd child
hardly a "local configuration" issue. I have not edited nor did I initially choose the ports. http://www.google.com/search?q=spamassassin+port+783 http://www.google.com/search?q=famd+port+783
(In reply to comment #1) > This is a local config problem, not a package problem. I have both running > quite nicely without reconfiguring either, futzing with anything, etc. By > default fam is listening on 642. I'm having the same problem, and I've found that if you start spamassassin first, then famd uses another port (752 on my system). But how do you configure famd to make it use a fixed port? There seem to be no configuration option...
(In reply to comment #3) > I'm having the same problem, and I've found that if you start spamassassin > first, then famd uses another port (752 on my system). But how do you > configure famd to make it use a fixed port? There seem to be no configuration > option... It seems that famd is grabbing a different port each time it's started...
