Seems it is indeed a bug, users on the mailing list could verify it. See this thread: http://lists.amavis.org/pipermail/amavis-users/2011-March/000069.html
It seems to be directly related to the number of maximum instances. netstat doesn't seem to give helpful information:
== floeff@myserver:~$ sudo netstat -a | grep 10024 [sudo] password for floeff: tcp 0 0 localhost:10024 *:* LISTEN floeff@myserver:~$ sudo /etc/init.d/amavis force-reload Stopping amavisd: amavisd-new. Starting amavisd: amavisd-new. floeff@myserver:~$ sudo netstat -a | grep 10024 tcp 0 0 localhost:10024 *:* LISTEN ==
Would love to use apport-collect, but I have only a console, and lynx does not seem to work - I've always get thrown back to the same page with a "Continue" button :(
Seems it is indeed a bug, users on the mailing list could verify it. See this thread: http:// lists.amavis. org/pipermail/ amavis- users/2011- March/000069. html
It seems to be directly related to the number of maximum instances. netstat doesn't seem to give helpful information:
==
floeff@myserver:~$ sudo netstat -a | grep 10024
[sudo] password for floeff:
tcp 0 0 localhost:10024 *:* LISTEN
floeff@myserver:~$ sudo /etc/init.d/amavis force-reload
Stopping amavisd: amavisd-new.
Starting amavisd: amavisd-new.
floeff@myserver:~$ sudo netstat -a | grep 10024
tcp 0 0 localhost:10024 *:* LISTEN
==
Would love to use apport-collect, but I have only a console, and lynx does not seem to work - I've always get thrown back to the same page with a "Continue" button :(