> > status=deferred (delivery temporarily suspended: conversation with 
> > 127.0.0.1[127.0.0.1] timed out while receiving the initial server
> > greeting)
> 
> Is postfix trying to open more connections to amavisd than 
> there are amavisd child processes ($max_servers) running?
> Is this a pre-queue filtering setup?
> 

Yes, I have a pre-queue filtering setup.

I have no idea if Postfix has reached the number of connections equal to
$max_servers.. :-( But I think that this is normally done..

> > Moreovere I tried to lauch amavisd-nanny but I get:
> >
> >  # /usr/local/src/amavisd-new-2.5.3/amavisd-nanny
> > process-id task-id     elapsed in    elapsed-bar (dots 
> indicate idle)
> >            or state   idle or busy
> > BDB no dbN 1: Unknown locker ID: 4a19cd No such file or 
> directory at 
> > /usr/local/src/amavisd-new-2.5.3/amavisd-nanny line 122.
> 
> The BerkeleyDB::Hash::new failed, it reported 'Unknown locker 
> ID: 4a19cd'
> as a primary error (the 'No such file or directory' might be bogus).

Infact..

> > # rpm -qa | grep db
> > dbus-1-0.60-33.2
> > db-4.3.29-15.2
> > gdb-6.4-19.10
> > dbus-1-mono-0.60-33.2
> > dbus-1-python-0.60-33.2
> > db-devel-4.3.29-15.2
> > gdbm-1.8.3-243.2
> > db-utils-4.3.29-15.2
> > dbus-1-glib-0.60-33.2
> > gdbm-devel-1.8.3-243.2
> >
> > I can't figure out what it can be the cause as I have the same 
> > software installed on a different macchine and all works fine..
> >
> > Moreover, could be the two anomalies related?
> 
> Don't know, could be related if both problems show up at the 
> same time. If a database would end up in a permanently-locked 
> state, the 'conversation with 127.0.0.1 timed out while 
> receiving the initial server greeting' could also be a 
> symptom. Amavisd log might be able to tell more. Trying db 
> 4.4.20 or later might help too.

OK. I have reloaded amavisd-new and all has continued to works
correctly. It seems a 'one-time' problem. But anyway it coulb be pretty
nice to point the cause. The main disease was that I didn't be aware
that amavisd-new didn't work at all. The postfix active queue has
reached an huge number of messages.

So, now, I have found a way to monitor the status of amavisd-new,
watching the size of Postfix queues and the latency of messages..

Thanks,

rocsca

-------------------------------------------------------------------------
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