I've been using amavisd-new with postfix for several years with no
problems until this new installation I just setup. There are now two
problems, that are probably inter-related.
Problem 1: after an 'amavisd reload' or 'amavisd stop' command, not
all child processes die. The main server thread exits and some children
may exit, but often one or more children hang around. Example:
[EMAIL PROTECTED] ~]# ps ax |grep amavisd
30170 ? Ss 0:13 amavisd (master)
31249 ? R 876:43 amavisd (ch4-31249-04)
817 ? S 0:06 amavisd (ch6-avail)
916 ? S 0:03 amavisd (ch4-avail)
930 ? S 0:01 amavisd (ch4-avail)
934 ? S 0:01 amavisd (ch4-avail)
936 ? S 0:01 amavisd (ch3-avail)
937 ? S 0:00 amavisd (ch2-avail)
943 ? S 0:01 amavisd (ch2-avail)
[EMAIL PROTECTED] ~]# amavisd reload
Daemon [30170] terminated by SIGTERM, waiting for dust to settle...
becoming a new daemon...
[EMAIL PROTECTED] ~]# ps ax |grep amavisd
31249 ? R 877:28 amavisd (ch4-31249-04)
989 ? Ss 0:03 amavisd (master)
991 ? R 0:00 amavisd (ch1-00991-01)
992 ? S 0:00 amavisd (virgin child)
993 ? S 0:00 amavisd (virgin child)
994 ? S 0:00 amavisd (virgin child)
995 ? S 0:00 amavisd (virgin child)
996 ? S 0:00 amavisd (virgin child)
997 ? S 0:00 amavisd (virgin child)
998 ? S 0:00 amavisd (virgin child)
Note that 31249 is still hanging around. A manual 'kill -TERM' will not
make it go away. I have to use 'kill -9' to zap it.
Problem 2: Sometimes, but not always, after an 'amavisd reload', the
communications between amavisd and postfix get hosed. The amavisd
process list will show the master and all virgin children and the
mail logs will show postfix unable to connect to the content filter
on 127.0.0.1:10025. I can manually telnet to 127.0.0.1:10025 and get
a prompt from amavisd. A 'postfix stop; postfix start' clears up
this problem.
The content filter in postfix is configured for smtp-filter on
127.0.0.1:10025 with the other end smtpd on 127.0.0.1:10026.
Software versions are:
amavisd-new-2.4.3 (also happened with 2.4.2)
postfix-2.3.3
perl-5.8.8
spamassassin-3.1.7
clamav-0.88.5
I looked in the mailing list archives and the FAQs, etc., and didn't
find anything that described this particular problem. Has anyone seen
anything similar? If you think it might be a postfix problem, let me
know and I can repost the message on that list.
-Bill Randle
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
