[SOLVED] Re: LMTPD process stuck at 100% - blocking mail deliveries - 3.8.1

"Joost Roeleveld via Info" <[email protected]>
Newsgroups gmane.mail.imap.cyrus
Message-ID <20240213062314.EGroupware.p-yAPhwsbMuSUWkzi0ZhktW@_>
Hi All,

I managed to resolve this.

----------------------- Original message -----------------------
From: Joost Roeleveld via Info <[email protected]>
To: Info <[email protected]>
Date: Wed, 07 Feb 2024 10:17:36 +0100
----------------------------------------------------------------

>>> Hi All,
>>>
>>> I tried upgrading from 3.4.5 to 3.8.1.
>>> All the steps went fine and I could access my emails.
>>>
>>> However, when I restarted postfix to have emails delivered, I  
>>> noticed the "lmtpd" process to be stuck at 100%.
>>> No emails were being delivered and all was stuck.
>>
>> I face this from time to time on my 3.2.6 murder cluster.
>> strace shows that the process qets stuck in conversations index.
>>
>> kill process, ctl_conversationsdb -z user and then  
>> ctl_conversationsdb -b user makes lmtp working again.
>> Sometimes I had to rm user.conversations but that was maybe when I  
>> didn't wait for -z to finish.
> 
> Thank you for your reply.
> Unfortunately, I don't think this was the cause.
> 
> I checked which files it had open (using lsof), and it only showed
> "deliver.db"
> This file is on a tmpfs and is rebuild every time the server restarts.
> This was recommended in the documentation when I upgraded to 3.4.x
> in the past and I haven't had any issues with that since.
> 
> And I did try this, but every time postfix would start trying to
> deliver emails, the lmtpd would instantly lock up.
> And I did do "reconstruct" and "ctl_conversationsdb" commands in
> between tries.
> 
> Kind regards,
> 
> Joost
> 




------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/Te9b6c39d0ac2a7d4-Me5ff3ea561e8ccba040e1671
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.