>>> On Friday, June 06, 2008 at 9:08 AM, in message
<[EMAIL PROTECTED]>, Andrew Ho <[EMAIL PROTECTED]>
wrote: 
> It is probably the clamd.sock is not located in the same directory. 
>  
> Check these two files again, and you may be find out the errors, and
the  
> init files in /etc/init.d. 

The clamd.conf file says that the pid and clamd-socket files are
supposed to be in /var/lib/clamav.  The databases definitely are there,
but I see no pid - that said, just as quickly as it broke, it seems to
have fixed itself using port 3310 (invisible pid notwithstanding).  But
that didn't fix the amavis processes just wanting to nap.  By the time
it was done I ended up with more than 1000 messages in my mail queue to
be processed, and somehow they started processing again just to spite me
more than anything I think!

My biggest issue with these "lazy amavis processes" as I've come to
call them, is that I can never seem to find a common solution that will
fix it each time, and also because it's generally so far between
incidents (I've had it happen about 5 times in the 3 or so years I've
used this setup) that when it happens I start pulling my hair out.  And
then it almost seems like as suddenly as the problem occurs, it goes
away.  I really have no idea if the clamav issue had anything at all to
do with the bigger problem, but it did eventually all get sorted out.

Thanks.

Danita


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to