On Wed, Sep 21, 2005 at 05:58:58PM -0500, Gary Mills wrote:
> We are running cyrus-imapd-2.1.14, using db-3.1.17 for the
> deliver.db and tls_sessions.db. Lately, we've been getting
> deadlocks that stall mail delivery. When they happen, all of
> the lmtpd processes are blocked waiting to acquire
On Thu, Sep 22, 2005 at 11:24:19AM +0300, Konstantinos Koukopoulos wrote:
> On Thu 22 Sep 2005 01:58, Gary Mills wrote:
> > We are running cyrus-imapd-2.1.14, using db-3.1.17 for the
> > deliver.db and tls_sessions.db. Lately, we've been getting
> > deadlocks that stall mail delivery. When they h
On Thu, Sep 22, 2005 at 11:24:19AM +0300, Konstantinos Koukopoulos wrote:
> On Thu 22 Sep 2005 01:58, Gary Mills wrote:
> > We are running cyrus-imapd-2.1.14, using db-3.1.17 for the
> > deliver.db and tls_sessions.db. Lately, we've been getting
> > deadlocks that stall mail delivery. When they h
Hi,
--On 21. September 2005 17:58:58 -0500 Gary Mills <[EMAIL PROTECTED]>
wrote:
We are running cyrus-imapd-2.1.14, using db-3.1.17 for the
deliver.db and tls_sessions.db. Lately, we've been getting
deadlocks that stall mail delivery. When they happen, all of
the lmtpd processes are blocked
We are running cyrus-imapd-2.1.14, using db-3.1.17 for the
deliver.db and tls_sessions.db. Lately, we've been getting
deadlocks that stall mail delivery. When they happen, all of
the lmtpd processes are blocked waiting to acquire a lock.
If I try to run the db_stat utility, it also blocks. These
