The last update updated amavid-new to 2.11.1-r3. After restarting my server to let a kernel update kick in, amavisd reports that it start normally, but a status shows it as crashed. ps aux shows that amavisd is not running. No log is written in messages or elsewhere. This is what happens: serverdef ~ # /etc/init.d/amavisd start * Starting amavisd ... [ ok ] serverdef ~ # /etc/init.d/amavisd status * status: crashed serverdef ~ # /etc/init.d/amavisd stop * Stopping amavisd ... * start-stop-daemon: no matching processes found Netstat shows there is nothing listening on 10024. Everything is configured correctly as far as I know. The most recent previous version of amavisd-new was running perfectly with no changes in configuration.
Amavisd is sometimes really unhelpful when it crashes. There's probably something in your config that is causing it to commit suicide -- the trick will be to find out what, exactly, it doesn't like. What happens if you run amavis in the foreground manually? That is, /usr/sbin/amavisd foreground as root. Ideally it will complain about something, and that's what you've got to fix. If it remains silent (and still crashes), then you can try increasing your $log_level in /etc/amavisd.conf, or another option would be to run the command above under "strace" to see what is happening right before it crashes.
I owe you guys an apology. Thanks to Michael's suggestion, I was able to successfully start amavis by setting the $myhostname var. Either something changed to make this a more strict requirement (uname no longer being sufficient) or the update overwrote my previous config and I wasn't thinking to check it.
No big deal, glad I could help!
