[Eisfair] [e1] spamd restart Problem

[Stefan Klepsch]

Hallo,

das Problem besteht nach wie vor...

Am 20.11.2013 18:45, schrieb Stefan Klepsch:
> Hallo Jürgen,
>
> ich habe jetzt mal den alten Prozess gekillt, und
> einen neuen gestartet, ohne die Option '-quiet':
>
> root at eis - ~ # kill 8324
> root at eis - ~ # /etc/init.d/antispam start
>
> Im antispam-log erscheint dann:
> Nov 20 18:28:39 eis spamd[8324]: spamd: server killed by SIGTERM,
> shutting down
> Nov 20 18:28:39 eis spamd[8324]: spamd: cannot unlink
> /var/run/spamd.pid: No such file or directory
> Nov 20 18:31:09 eis spamd[18694]: logger: removing stderr method
> Nov 20 18:31:13 eis spamd[18696]: rules: meta test FROM_41_FREEMAIL has
> dependency 'NSL_RCVD_FROM_41' with a zero score
> Nov 20 18:31:13 eis spamd[18696]: spamd: server started on port 783/tcp
> (running version 3.3.2)
> Nov 20 18:31:13 eis spamd[18696]: spamd: server pid: 18696
> Nov 20 18:31:13 eis spamd[18696]: spamd: server successfully spawned
> child process, pid 18925
> Nov 20 18:31:14 eis spamd[18696]: spamd: server successfully spawned
> child process, pid 18926
> Nov 20 18:31:14 eis spamd[18696]: spamd: server successfully spawned
> child process, pid 18927
> Nov 20 18:31:14 eis spamd[18696]: spamd: server successfully spawned
> child process, pid 18929
> Nov 20 18:31:14 eis spamd[18696]: spamd: server successfully spawned
> child process, pid 18930
>
> Aber dann gleich wieder das alte Spiel:
>
> Nov 20 18:31:31 eis spamd[19211]: server socket setup failed, retry 1:
> spamd: could not create INET socket on 127.0.0.1:783: Address already in
> use
> Nov 20 18:31:32 eis spamd[19211]: server socket setup failed, retry 2:
> spamd: could not create INET socket on 127.0.0.1:783: Address already in
> use
> Nov 20 18:31:33 eis spamd[19211]: server socket setup failed, retry 3:
> spamd: could not create INET socket on 127.0.0.1:783: Address already in
> use
> Nov 20 18:31:34 eis spamd[19211]: server socket setup failed, retry 4:
> spamd: could not create INET socket on 127.0.0.1:783: Address already in
> use
> Nov 20 18:31:35 eis spamd[19211]: server socket setup failed, retry 5:
> spamd: could not create INET socket on 127.0.0.1:783: Address already in
> use
> Nov 20 18:31:36 eis spamd[19211]: server socket setup failed, retry 6:
> spamd: could not create INET socket on 127.0.0.1:783: Address already in
> use
> Nov 20 18:31:37 eis spamd[19211]: server socket setup failed, retry 7:
> spamd: could not create INET socket on 127.0.0.1:783: Address already in
> use
> Nov 20 18:31:38 eis spamd[19211]: server socket setup failed, retry 8:
> spamd: could not create INET socket on 127.0.0.1:783: Address already in
> use
> Nov 20 18:31:39 eis spamd[19211]: server socket setup failed, retry 9:
> spamd: could not create INET socket on 127.0.0.1:783: Address already in
> use
> Nov 20 18:31:40 eis spamd[19211]: spamd: could not create INET socket on
> 127.0.0.1:783: Address already in use
> Nov 20 18:31:40 eis antispam: process control has restarted spamd!

Ich habe die von Jürgen vorgeschlagenen Werte testweise
sogar auf sleep 20 erhöht. Ohne Erfolg :-(

Hier nochmal ein aktueller Blick in die Proßessliste:
base     : 2.2.5
eiskernel: 2.4.1 (2.6.32-eisfair-1-SMP)

root at eis - ~ # ps ax | grep spam
14757 ?        SNs    0:02 /usr/bin/spamd -d -u spam -r 
/var/run/spamd.pid --round-robin -s local7 -x -A 127.0.0.1,10.50.1.0/24
14984 ?        SN     0:00 spamd child
14985 ?        SN     0:03 spamd child
14987 ?        SN     0:02 spamd child
14988 ?        SN     0:00 spamd child
14989 ?        SN     0:00 spamd child
15465 ?        SN     0:02 /bin/sh /var/install/bin/antispam-control
28794 ?        SN     0:00 /bin/sh /etc/init.d/antispam startspamd
28816 ?        SN     0:00 /usr/bin/perl -T -w /usr/bin/spamd -d -u spam 
-r /var/run/spamd.pid --round-robin -s local7 -x -A 127.0.0.1,10.50.1.0/24
29047 pts/0    SN+    0:00 grep spam
root at eis - ~ #

Wieso wird beim Start von spamd das PID-File nicht erzeugt?

Gruß,
  Stefan