similar to: mail-search backtrace

Displaying 20 results from an estimated 200 matches similar to: "mail-search backtrace"

2016 May 21
3
mail-search backtrace
On 13/04/16 06:41, Timo Sirainen wrote: > On 09 Apr 2016, at 21:48, Hugh Bragg <hughbragg at dodo.com.au> wrote: >> I'm repeatedly getting this error: >> >> Apr 07 04:37:27 imap(mymail at address): Panic: file mail-search.c: line 84 (mail_search_arg_init): assertion failed: (arg->initialized.keywords == NULL) >> Apr 07 04:37:27 imap(mymail at address):
2007 Sep 10
2
Assertion failure in mail-index-view-sync.c
I have been getting these assertion failures every couple days, killing the IMAP process. After it happens, I can login immediately and everything is fine until it happens again. Here is the log entry: Sep 10 10:03:41 mailbox-4 dovecot: nh: IMAP(username): file mail-index-view-sync.c: line 666 (mail_index_view_sync_end): assertion failed: (view->log_file_offset >=
2012 Jun 08
3
error in mlogit
??????????????????????????????????????????... ????: ???? URL: <https://stat.ethz.ch/pipermail/r-help/attachments/20120608/37c40cb5/attachment.pl>
2019 Jul 18
0
Panic alert
Hi, I am getting a panic alert when sending an email in my box.? Below is the backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x9f3de) [0x7fa90b5543de] -> /usr/lib64/dovecot/libdovecot.so.0(+0x9f4be) [0x7fa90b5544be] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fa90b4e577c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_search_args_unref+0xa2) [0x7fa90b827c82] ->
2016 Dec 05
2
2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)
Hi, Dec 5 20:24:31 dovecot: imap(xx at yy.zz,7ckWZu1CuZFVTILa): Fatal: master: service(imap): child 7292 killed with signal 6 (core dumped) Dec 5 20:24:32 dovecot: imap(xx at yy.zz,LnAlZu1COBVVTILa): Panic: file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) Dec 5 20:24:32 dovecot: imap(xx at yy.zz,LnAlZu1COBVVTILa): Error: Raw backtrace:
2019 Jul 30
0
dovecot/imap crashes on Centos 7
Hi All, I have my dovecot/imap crashing on my Centos7 server. Below is the stacktrace I got: #0? 0x00007f32d9b84e58 in array_count_i (array=0x55b332a1f8f8) at array.h:155? ? ? ? ? ? ? ? ? ? ? ? ? ?No locals.? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??#1? array_get_i (count_r=<synthetic pointer>, array=0x55b332a1f8f8) at array.h:209? ? ? ? ? ?
2017 Jan 24
1
Quota count does not work with lock_method=dotlock
On 24.01.2017 11:31, Tom Sommer wrote: > On 2017-01-24 10:25, Aki Tuomi wrote: >> On 24.01.2017 11:13, Tom Sommer wrote: >>> On 2017-01-18 15:27, mkliewe at gmx.de wrote: >>> >>>> dovecot crashes when I switch the quota tracking from dict to count. >>> >>> I have the same problem, but I use 'dict:file' as quota backend - >>>
2019 Oct 10
0
Dovecot core debug
Hi all, I have a Dovecot core that I am trying to track down, in an attempt to replicate so I can log a bug report, and am hoping others might be able to help me as I?m reaching my limit. My working theory is that two user sessions are active at the same time, one of the sessions is ?mid-search? (or perhaps in idle state) on a virtual folder where the number of results is zero (due to a null
2017 Aug 16
1
dotlock causing crashes
OS: CentOS 7 x86_64 Dovecot version: 2.2.31 (65cde28) (GhettoForge RPM) Filesystem: GlusterFS, but working on changing that. Only one server is receiving activity. Was getting messages about corrupt dovecot.map.index files. Changed to dotlock from fcntl to try to fix that. Reading symbols from /usr/libexec/dovecot/imap...(no debugging symbols found)...done. [New LWP 74012] Core was generated by
2007 Sep 06
2
Error: corrupted index file
Hi all, I see the next error at dovecot.log: dovecot: Sep 06 17:57:27 Error: IMAP(jordi.espasa at opengea.org): Corrupted index file /var/vmail/opengea.org/jordi.espasa/.Dov ecot/dovecot.index: Duplicate header extension keywords ?Why this error is producted? -- Thanks, Jordi Espasa Clofent
2012 Nov 22
1
Plugin help, number of messages in mailbox
Hi, We use Dovecot for IMAP and POP (but not LDA), we want to do something when a user has an INBOX that becomes empty, or becomes not empty (set a flag in memcached, but that's not really important). I'm writing a plugin (for Dovecot 2.1.7). On mailbox_open() I can use mailbox_get_status() to get a count of messages in the mailbox, and then decrement this in expunge() or increment it
2017 Dec 19
0
Panic: file-lock.c
Today we had an unclean shutdown of our NFS filler and have had lots of issues with mailboxes being re-synced, mostly all the issues are now resolved but we are seeing the following appear for one user on our system. Dec 19 16:15:29 imap(xxx.xxx at xxx.com)(xxx.xxx at xxx.com): Panic: file file-lock.c: line 287: unreached Dec 19 16:15:29 imap(xxx.xxx at xxx.com)(xxx.xxx at xxx.com): Error: Raw
2007 Jan 22
2
Large & busy site, NFS with deliver only servers
Timo / Others, I have been working on a new installation for a fairly busy site, and after many weeks of tribulation have come to an architecture Im happy with: 2x Debian (2.6.18) - MXing machines running Postfix / MailScanner / Dovecot-LDA (A slightly patched RC17 for prettier Quota bounces) 2x Debian (2.6.18) - Mail retrieval machines running Dovecot IMAP/POP3 (Currently RC17) 3x Node Isilon
2008 Dec 03
1
assertion failed
Hi all, I have seen this in log: dovecot: Dec 03 06:12:57 Error: IMAP(maurirrr): file mail-index-view-sync.c: line 666 (mail_index_view_sync_end): asser tion failed: (view->log_file_offset >= view->map->hdr.log_file_int_offset) dovecot: Dec 03 06:12:57 Error: IMAP(maurirrr): Raw backtrace: /usr/libexec/dovecot/imap [0x461d5e] -> /usr/libexec/dov ecot/imap [0x461acc] ->
2013 Apr 23
2
mailbox_list_index_parse_header crash
Hi, I got all excited about IMAP NOTIFY support and tried enabling mailbox_list_index on my server. Unfortunately, I rather quickly ran into trouble of the segfault variety. This prevented me from doing basic things like seeing the contents of some of my folders. Disabling mailbox_list_index got me back up and running, but... darnit, that's annoying. The only message I got in my log file
2008 Mar 10
2
dovecot 1.1.rc3 assertion failed at index_mailbox_set_recent_uid while deleting message with thunderbird.
To some users happens this assertion failure while deleting a message. dovecot: Mar 10 08:40:44 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists (&ibox->recent_flags, uid)) dovecot: Mar 10 08:40:44 Error: IMAP(user): Raw backtrace: [see bleow] dovecot: Mar 10 08:40:44 Error: child 17683 (imap) killed with signal 6 And the
2006 Jan 16
7
1.0 beta1 released
As promised, here it is finally. v1.0 is getting nearer and I want people to start looking at Dovecot's sources. Getting some more help with development would be nice, but I'd also like to hear if there are any hidden bugs in the code. So, one week from now I'll start offering 1000 EUR for the first person to point out a remotely exploitable security hole in Dovecot. See
2018 Aug 17
2
imapsieve: Change message flags on COPY
On Friday 17 August 2018 01:41:39 CEST Stephan Bosch wrote: > dovecot -n Hi, here it is (I don't know why I get the SSLv2 warning because it is disabled in ssl_protocols, any ideas about that too?). BTW, even when storing the message in a different folder with fileinto, the original message is still saved in the original mailbox. I also tried using `discard;` and makes no difference, I
2016 Dec 06
0
2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)
Hi, On 05-Dec-16 20:28, Toni Mattila wrote: > Panicing stopped when all index files where deleted. It happens again in same user account, so rebuilding indexes didn't fix it. Here's bt full instead of just bt: #0 0x001d4402 in __kernel_vsyscall () No symbol table info available. #1 0x00949d70 in raise () from /lib/i686/nosegneg/libc.so.6 No symbol table info available. #2
2018 Aug 16
2
imapsieve: Change message flags on COPY
Hello, I'm trying to do a simple thing using imapsieve, I want messages to be marked as read when moved to certain folders (Trash, Archive, Spam). All the set up to run the imapsieve script works perfectly, but I'm having trouble to make changes effective. As the RFC says, IMAP messages are immutable, but it's not clear to me reading the specs if this applies to IMAP flags too, as one