Re: [Dovecot] 1.2.7: recs[i]-uid rec- uid

2009-11-25 Thread Brandon Davidson
Timo,

 -Original Message-
  I'm not really sure why these are happening. I anyway changed them from
  being assert-crashes to just logged errors. I'm interested to find out
  what it logs now and if there are any user-visible errors.
  http://hg.dovecot.org/dovecot-1.2/rev/e47eb506eebd
 
 FWIW, I'm seeing this on 1.2.8 as well - just for one user so far. I'll try
 applying this patch, and report if I see anything else logged.

The user who encountered an assert crash prior to this patch now seems to be 
working properly. I am not aware of any errors presented to the client, but the 
logs show the following on the first login after application of the patch:

Nov 25 07:51:28 oh-popmap1p dovecot: imap: user=youm, rip=x.x.x.x, pid=13702: 
/home6/youm/Maildir/.Deleted Messages/dovecot-uidlist: uid=24464 exists in 
index, but not in uidlist 
Nov 25 07:51:28 oh-popmap1p dovecot: imap: user=youm, rip=x.x.x.x, pid=13702: 
/home6/youm/Maildir/.Deleted Messages/dovecot-uidlist: uid=24520 exists in 
index, but not in uidlist 
Nov 25 07:51:28 oh-popmap1p dovecot: imap: user=youm, rip=x.x.x.x, pid=13702: 
/home6/youm/Maildir/.Deleted Messages/dovecot-uidlist: uid=24532 exists in 
index, but not in uidlist

I have not seen it repeated since.

-Brad


Re: [Dovecot] 1.2.7: recs[i]-uid rec- uid

2009-11-24 Thread Brandon Davidson
 -Original Message-
 On Sun, 2009-11-22 at 23:54 +0100, Edgar Fuß wrote:
  I'm getting this Panic with some users on dovecot-1.2.7:
 
  Panic: file maildir-uidlist.c: line 1242
  (maildir_uidlist_records_drop_expunges): assertion failed: (recs[i]-
   uid  rec-
  uid)
 
 I'm not really sure why these are happening. I anyway changed them from
 being assert-crashes to just logged errors. I'm interested to find out
 what it logs now and if there are any user-visible errors.
 http://hg.dovecot.org/dovecot-1.2/rev/e47eb506eebd

FWIW, I'm seeing this on 1.2.8 as well - just for one user so far. I'll try 
applying this patch, and report if I see anything else logged.

For the record, the old epoll_ctl issue was resolved by the patch that 
reordered the fd closes. We ran 1.2.6 with that patch for quite a while and it 
didn't reoccur once.

-Brad


Re: [Dovecot] 1.2.7: recs[i]-uid rec- uid

2009-11-24 Thread Marco Nenciarini

Brandon Davidson ha scritto:


For the record, the old epoll_ctl issue was resolved by the patch that 
reordered the fd closes. We ran 1.2.6 with that patch for quite a while and it 
didn't reoccur once.



I can confirm that the epoll_ctl bug was resolved.

Kind Regards,
Marco

--
-
|Marco Nenciarini| Debian/GNU Linux Developer - Plug Member |
| mnen...@prato.linux.it | http://www.prato.linux.it/~mnencia   |
-
Key fingerprint = FED9 69C7 9E67 21F5 7D95  5270 6864 730D F095 E5E4



Re: [Dovecot] 1.2.7: recs[i]-uid rec- uid

2009-11-23 Thread Timo Sirainen
On Sun, 2009-11-22 at 23:54 +0100, Edgar Fuß wrote:
 I'm getting this Panic with some users on dovecot-1.2.7:
 
 Panic: file maildir-uidlist.c: line 1242  
 (maildir_uidlist_records_drop_expunges): assertion failed: (recs[i]- 
  uid  rec-
 uid)

I'm not really sure why these are happening. I anyway changed them from
being assert-crashes to just logged errors. I'm interested to find out
what it logs now and if there are any user-visible errors.
http://hg.dovecot.org/dovecot-1.2/rev/e47eb506eebd



signature.asc
Description: This is a digitally signed message part


Re: [Dovecot] 1.2.7: recs[i]-uid rec- uid

2009-11-23 Thread Edgar Fuß
 I'm interested to find out what it logs now
Nothing.

 and if there are any user-visible errors.
No.

It simply seems to work?!

I've still disabled the 1.2.7 server and am only testing with my own account 
(which triggered the error). I can re-enable the server for public use if that 
helps.



Re: [Dovecot] 1.2.7: recs[i]-uid rec- uid

2009-11-23 Thread Timo Sirainen
On Mon, 2009-11-23 at 20:08 +0100, Edgar Fuß wrote:
  I'm interested to find out what it logs now
 Nothing.
 
  and if there are any user-visible errors.
 No.
 
 It simply seems to work?!

It simply replaced assert-crash with non-crashing logging. If anything
appears to be fixed, it's nothing bug luck. (Unless I accidentally
changed the logic, but I don't think I did..)



signature.asc
Description: This is a digitally signed message part