headers
Marc Muehlfeld | 1 Sep 2011 08:57
Picon
Favicon

Re: Since updating to 2.4.10: Mailbox has an invalid format

 > imap[11591]: IOERROR: refreshing index for user.muehlfeld.IMGM_Extern.GbR: 
Success
 > imap[11591]: IOERROR: locking index user.muehlfeld.IMGM_Extern.GbR: Mailbox 
has an invalid format

After an horrible day of many many broken mailboxes (after upgrading from 
2.3.16 to 2.4.10) and as same many repairs, I found the solution: I moved 
/var/spool/imap from XFS to Ext4. I've done this 36h ago and since that moment 
no mailbox got broken again.

If someone else is having the same problem - this are the steps I have done:
- Create a new volume with Ext4 and mount it
- Shutdown Cyrus
- Run "reconstruct -O -r user.*" as user cyrus to repair all broken mailboxes. 
(I run it twice, just to be sure, that everything is fine. :-))
- Copy the content from /var/spool/imap to the new Ext4 volume.
- Mount the Ext4 volume to /var/spool/imap (don't forget to change your 
/etc/fstab entry!)
- Because I'm paranoid, I run the above reconstruct again - now on the Ext4 
volume.
- Started Cyrus.

My server is running Scientific Linux 6.1 (x86_64). All software was installed 
from the repository (just cyrus is selfcompiled). All kernel settings are also 
left on their default.

Regards,
Marc
----
Cyrus Home Page: http://www.cyrusimap.org/
(Continue reading)

Permalink | Reply | 0 comments |
headers
Vittorio Manfredini | 1 Sep 2011 13:41

Problem with shared folder after migrating from 2.3,16 to 2.4.10

I have some problem with shared folder after migrating from 2.3,16 to 2.4.10.

The shared folder are present I can see it with different client, but  
when I try to access nothing happen,
and with horde4 I see in the log the following message :

Sep  1 12:48:10 www HORDE: [imp] PHP ERROR: Trying to get property of  
non-object [pid 19909 on line 353 of  
"/srv/www/htdocs/horde4/imp/lib/Imap.php"]
Sep  1 12:48:10 www HORDE: [imp] IMAP error: Mailbox does not exist  
[pid 19909 on line 340 of "/srv/www/htdocs/horde4/imp/lib/Imap.php"]

the same happen with evolution and thunderbird I can see the folders,  
but I cannot access it and I cannot subscribe to it.

With thunderbird I receive the message that the mailbox did not exists.

I test the namespace using the telnet command this is the result :

 NAMESPACE
* NAMESPACE (("" "/")) (("user/" "/")) (("shared/" "/"))
 OK Completed

The created shared folder was :

shared/folder <at> example.com

and the result of lam command is :

localhost> lam shared/folder <at> example.com
(Continue reading)

Permalink | Reply | 2 comments |
headers
Craig White | 1 Sep 2011 15:44

Re: cpu and cyrus

On Wed, 2011-08-31 at 16:34 -0400, John Madden wrote:
> >> So annoying that the stable release of debian isn't supported
> >> anymore. It seems like if you wait so long to release the stable
> >> version that it isn't supported anymore, it sort of defeats the
> >> purpose.
> >
> > Debian have been staying at 2.2 rather than moving up to 2.3 through
> > two stable releases now.  There is a limit to how long you can hold
> > on to the past.  Cyrus 2.3.0 was released in December 2005.
> 
> There's a lesson here that I learned from the OpenLDAP folks that is 
> re-enforced with Cyrus (and many other packages): You can't rely on your 
> OS distributor beyond a certain scale.  RHEL's OpenLDAP packages are 
> fine a thousand objects, no good at all for a million.  Some of the 
> problems are too complex: imagine Debian delivering a functioning Murder 
> out of the box or Red Hat combining the right version of BerkeleyDB with 
> the right version of OpenLDAP.  No thanks.
> 
> It's well worth your time to maintain your own compiles and even 
> packages of Cyrus because the package maintainers can't keep up.
----
indeed though interestingly enough, OpenLDAP on Ubuntu is current.

Once I saw that ubuntu was still featuring cyrus 2.2.13, I didn't even
bother.

For Ubuntu LTS, grab source for cyrus and compile - worked great. Only
had to get a reasonably suitable sysv script to start/stop.

Those using CentOS/Scientific Linux/RHEL should probably just rebuild
(Continue reading)

Permalink | Reply | 1 comment |
headers
Vittorio Manfredini | 1 Sep 2011 16:20

Re: Problem with shared folder after migrating from 2.3,16 to 2.4.10

Sorry ....

I found a permission problem.

Now it's working

-- 
Vittorio Manfredini
email: vittorio <at> vitsoft.bz

----- Messaggio da Vittorio Manfredini <vittorio <at> vitsoft.bz> ---------
    Data: Thu, 01 Sep 2011 13:41:40 +0200
      Da: Vittorio Manfredini <vittorio <at> vitsoft.bz>
Oggetto: Problem with shared folder after migrating from 2.3,16 to 2.4.10
       A: info-cyrus <at> lists.andrew.cmu.edu

> I have some problem with shared folder after migrating from 2.3,16 to 2.4.10.
>
> The shared folder are present I can see it with different client, but
> when I try to access nothing happen,
> and with horde4 I see in the log the following message :
>
> Sep  1 12:48:10 www HORDE: [imp] PHP ERROR: Trying to get property of
> non-object [pid 19909 on line 353 of
> "/srv/www/htdocs/horde4/imp/lib/Imap.php"]
> Sep  1 12:48:10 www HORDE: [imp] IMAP error: Mailbox does not exist
> [pid 19909 on line 340 of "/srv/www/htdocs/horde4/imp/lib/Imap.php"]
>
> the same happen with evolution and thunderbird I can see the folders,
> but I cannot access it and I cannot subscribe to it.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Bron Gondwana | 1 Sep 2011 16:49
Gravatar

Re: Problem with shared folder after migrating from 2.3,16 to 2.4.10

On Thu, Sep 01, 2011 at 04:20:16PM +0200, Vittorio Manfredini wrote:
> Sorry ....
> 
> I found a permission problem.
> 
> Now it's working

Excllent :)
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Permalink | Reply | 0 comments |
headers
Marc Patermann | 1 Sep 2011 17:53
Picon

Re: cpu and cyrus

Hi,

Craig White schrieb am 01.09.2011 15:44 Uhr:
> On Wed, 2011-08-31 at 16:34 -0400, John Madden wrote:
>>>> So annoying that the stable release of debian isn't supported
>>>> anymore. It seems like if you wait so long to release the stable
>>>> version that it isn't supported anymore, it sort of defeats the
>>>> purpose.
>>> Debian have been staying at 2.2 rather than moving up to 2.3 through
>>> two stable releases now.  There is a limit to how long you can hold
>>> on to the past.  Cyrus 2.3.0 was released in December 2005.
>> There's a lesson here that I learned from the OpenLDAP folks that is 
>> re-enforced with Cyrus (and many other packages): You can't rely on your 
>> OS distributor beyond a certain scale.  RHEL's OpenLDAP packages are 
>> fine a thousand objects, no good at all for a million.  Some of the 
>> problems are too complex: imagine Debian delivering a functioning Murder 
>> out of the box or Red Hat combining the right version of BerkeleyDB with 
>> the right version of OpenLDAP.  No thanks.
>>
>> It's well worth your time to maintain your own compiles and even 
>> packages of Cyrus because the package maintainers can't keep up.
> ----
> indeed though interestingly enough, OpenLDAP on Ubuntu is current.
> 
> Once I saw that ubuntu was still featuring cyrus 2.2.13, I didn't even
> bother.
> 
> For Ubuntu LTS, grab source for cyrus and compile - worked great. Only
> had to get a reasonably suitable sysv script to start/stop.
Wouldn't it be great, if someone could offer a PPA for Cyrus IMAPd for
(Continue reading)

Permalink | Reply | 0 comments |
headers
Maria McKinley | 1 Sep 2011 18:38

Re: cpu and cyrus

On 8/31/11 1:09 PM, Bron Gondwana wrote:

>
> Ok - next time it goes crazy can you pick one up with gdb and get
> a backtrace?
>
> gdb $cyrusbinpath/imapd $pid
>
> and then when you get the prompt:
>
> bt
>
> and maybe also:
>
> p imapd_in
>
> which will give us the command that's running.
>
> There are various bugs back in the 2.2 series which could cause
> an infinite loop - and the most interesting bit is working out
> which corrupt file is causing the problem.
>
> Bron.

Why does it not see the directory /usr/lib/cyrus/bin? that seems weird. 
Am I doing something wrong here? Tried it with a couple of different 
cyrus processes.

~maria
(Continue reading)

Permalink | Reply | 6 comments |
headers
Maria McKinley | 1 Sep 2011 19:14

Re: cpu and cyrus

On 9/1/11 9:38 AM, Maria McKinley wrote:
> On 8/31/11 1:09 PM, Bron Gondwana wrote:
>
>>
>> Ok - next time it goes crazy can you pick one up with gdb and get
>> a backtrace?
>>
>> gdb $cyrusbinpath/imapd $pid
>>
>> and then when you get the prompt:
>>
>> bt
>>
>> and maybe also:
>>
>> p imapd_in
>>
>> which will give us the command that's running.
>>
>> There are various bugs back in the 2.2 series which could cause
>> an infinite loop - and the most interesting bit is working out
>> which corrupt file is causing the problem.
>>
>> Bron.
>
> Why does it not see the directory /usr/lib/cyrus/bin? that seems weird.
> Am I doing something wrong here? Tried it with a couple of different
> cyrus processes.
>
> ~maria
(Continue reading)

Permalink | Reply | 5 comments |
headers
Maria McKinley | 1 Sep 2011 20:15

Re: cpu and cyrus

On 8/31/11 1:40 PM, Bron Gondwana wrote:
> On Wed, Aug 31, 2011 at 11:51:03AM -0700, Maria McKinley wrote:
>> On 8/31/11 11:44 AM, Wesley Craig wrote:
>>> On 31 Aug 2011, at 14:36, Maria McKinley wrote:
>>>> Anyway, here is an example of some processes that are getting big:
>>>>
>>>>     PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
>>>>
>>>> 24328 cyrus     20   0  147m 6236 5004 R 27.4  0.2  22:07.21 imapd
>>>>
>>>> 27549 cyrus     20   0  147m 6512 5116 R 27.4  0.2 155:41.26 imapd
>>>>
>>>> 30097 cyrus     20   0  147m 6280 5052 R 27.1  0.2  93:44.08 imapd
>>>>
>>>>
>>>> Unfortunately I can't tell you anymore about these processes, since they
>>>> are just cut and pasted from a terminal where I checked top before
>>>> restarting cyrus, and cyrus has not regrown yet.
>>>
>>> It would be handy if you'd gather some metrics from a loaded but not pathological machine, and then
additional metrics once it was in a bad state.  Also, getting strace output from a run-away (if it is
run-away) process would be handy.
>>>
>>> :wes
>>
>>
>> Not sure how helpful this is, but you can see where the that I have
>> restarted cyrus twice in the last 24 hours, and three times in the last
>> week, and how this has affected the load, etc. of this machine.
>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dan White | 1 Sep 2011 20:49
Gravatar

Re: cpu and cyrus

On 01/09/11 10:14 -0700, Maria McKinley wrote:
>> On 8/31/11 1:09 PM, Bron Gondwana wrote:
>>> Ok - next time it goes crazy can you pick one up with gdb and get
>>> a backtrace?
>>>
>>> gdb $cyrusbinpath/imapd $pid
>>>
>>> and then when you get the prompt:
>>>
>>> bt
>>>
>>> and maybe also:
>>>
>>> p imapd_in
>>>
>>> which will give us the command that's running.
>>>
>
>ella:~# gdb /usr/lib/cyrus/bin/imapd 4416

>(gdb) bt
>#0  0x00007f2c049e90d8 in poll () from /lib/libc.so.6
>#1  0x00007f2bfe6fd31d in ?? () from /usr/lib/libldap_r-2.4.so.2
>#2  0x00007f2bfe6fe4fd in ldap_result () from /usr/lib/libldap_r-2.4.so.2
>#3  0x00007f2bfe93a505 in ?? () from /lib/libnss_ldap.so.2
>#4  0x00007f2bfe93a7a7 in ?? () from /lib/libnss_ldap.so.2
>#5  0x00007f2bfe93cff5 in _nss_ldap_endgrent () from /lib/libnss_ldap.so.2
>#6  0x00007f2c04a04d89 in ?? () from /lib/libc.so.6
>#7  0x00007f2c049c315a in endgrent () from /lib/libc.so.6
>#8  0x0000000000451d1d in ?? ()
(Continue reading)

Permalink | Reply | 4 comments |

Gmane