[BlueOnyx:09761] Re: openwebmail error

[Matthew Komar]

I also started getting this after today's massive yum update ... related?

First thing I did was to check the quota for the user in question, but 
that looked fine for both the user and site.

I'm also getting reports from other folks as well. No quota issues to be 
found.

On 3/8/2012 10:10 AM, Chris Gebhardt - VIRTBIZ Internet wrote:
> Adam Lepp wrote:
>
>> His error was:  Couldn't get read lock on db
>> /home/.sites/XX/siteYY/.users/ZZ/[loginname]/.openwebmail/db/[loginname]
>>
>> This occurred after logging in with the correct credentials.  I
>> duplicated his problem on my PC.
>>
>>
>>
>> I tried openwebmail for my own account, and got a similar  error:
>>
>> Couldn't update index db db
>> /home/.sites/XX/siteYY/.users/ZZ/[loginname]/.openwebmail/db/[loginname]
> 2 things:
> 1. Check your user's quota and make sure he's not 100% consumed.
> 2. Make sure that he isn't trying to log in with another POP/IMAP client
> (or mobile device) that would lock the session.
>
> If neither of those first 2 very simple checks are helpful, then check this:
> http://openwebmail.lagmonster.org/doc/faq.txt
>
> Q: I got 'Couldn't get read lock on ....' error?
>            'Couldn't get write lock on ....' error?
> A: If the error message appears immediately after you submit the CGI
> request, then it may be due to the user doesn't has enough privilege to
> lock the file or the directory for the file even doesn't exist.
>
> If the error message appears after the cgi request submission for more
> than 30 seconds, then the folder openwebmail want to access may be
> locked by other process.
>
> Most of the time, it is due to the concurrent accesses to the folder by
> other mail client through the pop3/imap daemons. This is okay, just back
> to previous page and try again later.
>
> To know where the error happened exactly, you may try to set option
> error_with_debuginfo to yes in openwebmail.conf. This would give you
> more detailed information in case openwebmailerror() happens.
>
> If you are running openwebmail in persistent mode, there could be
> openwebmail processes locking the folder file for indexing.
>
> To release the lock, you may kill the openwebmail speedy_backend process.
>
> Since openwebmail 20041129, you may use 'openwebmail-tool.pl -u
> username' to find the processes holding the filelocks, and kill the
> processes after confirmation.
>
> If the locks couldn't be released after killing the related processes,
> you may solve the problem in a quick and dirty way... rename the file,
> copy it to original name, then remove the renamed one. This would have
> the file a new inode and thus release all old locks.
>
> ps: The 'openwebmail-tool.pl -u requires the lsof package.
>       it is available at http://freshmeat.net/projects/lsof/
>
> ps: Killing the openwebmail process may leave an incomplete index db
>       on disk. It is okay, the folder index db will be fixed or rebuild
>       in the next access.
>