On Mon, 2 Jul 2007 at 15:49 -0300, [EMAIL PROTECTED] confabulated:
2007/7/2, Duane Hill <[EMAIL PROTECTED]>:
On Mon, 2 Jul 2007 at 15:22 -0300, [EMAIL PROTECTED] confabulated:
> Good afternoon,
> In my server of email it is appears the following error in maillog:
>
> Jul 2 15:16: 56 to mailserver spamc [19271]: connect you spamd on
> 127.0.0.1failed, retrying (#1 of 3): Connection refused
> Jul 2 15:16: 56 to mailserver spamd [15754]: prefork: child states: II
> Jul 2 15:16: 57 to mailserver spamc [19271]: connect you spamd on
> 127.0.0.1failed, retrying (#2 of 3): Connection refused
> Jul 2 15:16: 58 to mailserver spamc [19271]: connect you spamd on
> 127.0.0.1failed, retrying (#3 of 3): Connection refused
> Jul 2 15:16: 59 to mailserver spamc [19271]: connection attempt you
spamd
> aborted to after 3 retries
>
> when I try for the service of spamassassin appears the following
message:
>
> [to [EMAIL PROTECTED] ~] # /usr/local/etc/rc.d/sa-spamd stop
> spamd not running? (check /var/run/spamd/spamd.pid).
>
> However the service is twirling and marking punctuation in e-mails. What
it
> can be happening of wrong?
This can happen if you attempt to start spamd using incorrect parameters
with the startup switches. I know this from experience.
To kill spamd, you have to find its parent process and kill it. Here, I
run on FreeBSD. So, I use:
ps auxwj | grep spamd
One of the things the <j> switch tells 'ps' is to list the ppid (parent
process ID). Thus, I can now do:
kill <ppid_returned_from_ps>
Start spamd using parameters:
spamd_enable="YES"
spamd_flags="-u qscand -D -P -x -q -c -d -r /var/run/spamd.pid
--socketpath=/var/run/spamd.socket \
--socketowner=qscand --socketgroup=qscand"
anything wrong ?
You are using the -u option. Here's what the -r option says in the man
page:
-r pidfile, --pidfile=pidfile
Write the process ID of the spamd parent to the file specified by
pidfile. The file will be unlinked when the parent exits. Note that
when running with the -u option, the file must be writable by that
user.
Is the pid file writable by the user you are running spamd under?
You also shouldn't have to specify the -d or -r options. The startup
script automatically does this for you. Here's from my
/usr/local/etc/rc.d/sa-spamd.sh
pidfile=${spamd_pidfile:-"/var/run/spamd/spamd.pid"}
...
command_args="-d -r ${pidfile}"
Here's what I have for startup options:
spamd_flags="--username=spamd --groupname=spamd --min-children=10
--max-children=40 --min-spare=20 --max-spare=22 --max-conn-per-child=160 --timeout-tcp=40
--timeout-child=320 --sql-config --nouser-config"
My install is local to the server so I just use the default TCP localhost
connection.