search for: mail_index_move_to_memory

Displaying 8 results from an estimated 8 matches for "mail_index_move_to_memory".

2007 Jan 02
1
Dovecot 1.0-rc15 on Solaris 10
...to ramp up our user count and ran into a file descriptor limit: Jan 1 19:38:54 <hostname> dovecot: IMAP(username): Newly created index file is corrupted: /home/username/.imap/foldername/dovecot.index.tmp Jan 1 19:38:54 <hostname> dovecot: IMAP(username): file mail-index.c: line 1806 (mail_index_move_to_memory): assertion failed: (index->fd == -1) Jan 1 19:38:54 <hostname> dovecot: pipe() failed: Too many open files Jan 1 19:38:54 <hostname> dovecot: Temporary failure in creating login processes, slowing down for now We got around this by calling "ulimit -n 512" and restarting...
2016 Jul 14
3
Panic: file mail-transaction-log-file.c: line 104 (mail_transaction_log_file_free): assertion failed: (!file->locked)
...nsaction_logs_clean+0x4d) [0x7feb8a3360ed] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_transaction_log_close+0x30) [0x7feb8a336230] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_transaction_log_move_to_memory+0xd5) [0x7feb8a3363e5] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_move_to_memory+0xa0) [0x7feb8a330440] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_index_write+0x183) [0x7feb8a32e9d3] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_fsck+0xc1f) [0x7feb8a3186ff] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x49b) [0x7feb8a322eab] -&...
2016 Nov 01
1
Panic: file mail-transaction-log-file.c: line 104 (mail_transaction_log_file_free): assertion failed: (!file->locked)
...logs_clean+0x4d) [0x7feb8a3360ed] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_transaction_log_close+0x30) [0x7feb8a336230] -> /usr/lib64/dovecot/libdovecot- >> storage.so.0(mail_transaction_log_move_to_memory+0xd5) [0x7feb8a3363e5] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_move_to_memory+0xa0) [0x7feb8a330440] -> /usr/lib64/dovecot/libdovecot- >> storage.so.0(mail_index_write+0x183) [0x7feb8a32e9d3] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_fsck+0xc1f) [0x7feb8a3186ff] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x49b) >> [...
2019 Mar 27
2
Panic: file mail-transaction-log-file.c: line 105 (mail_transaction_log_file_free): assertion failed: (!file->locked)
...ansaction_logs_clean+0x5c) [0x7f25fc9e6e3c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_transaction_log_close+0x34) [0x7f25fc9e6f04] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_transaction_log_move_to_memory+0xed) [0x7f25fc9e709d] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_move_to_memory+0x60) [0x7f25fc9e10b0] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_write+0x1e1) [0x7f25fc9df3a1] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_fsck+0x68a) [0x7f25fc9ca13a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x5b0) [0x7f25fc9d4090] -&gt...
2006 Feb 07
1
In-memory Index file bug
Hi, I am getting intermittent error messages in the log when my mail client tries to create/open a folder named ".imhoprefs". Some accounts seem to able to do it, but I have at least one that gives the log error: Feb 7 09:29:54 acad-cl1 dovecot: imap(tkay): close() failed with index file (in-memory index): Bad file descriptor I traced through the code, and it seems to be coming from
2016 Aug 25
0
Panic: file mail-transaction-log-file.c: line 104 (mail_transaction_log_file_free): assertion failed: (!file->locked)
...ion_logs_clean+0x4d) [0x7feb8a3360ed] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_transaction_log_close+0x30) [0x7feb8a336230] -> /usr/lib64/dovecot/libdovecot- > storage.so.0(mail_transaction_log_move_to_memory+0xd5) [0x7feb8a3363e5] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_move_to_memory+0xa0) [0x7feb8a330440] -> /usr/lib64/dovecot/libdovecot- > storage.so.0(mail_index_write+0x183) [0x7feb8a32e9d3] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_fsck+0xc1f) [0x7feb8a3186ff] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x49b) > [0x7feb8a...
2008 Jun 02
1
Problems under opensuse-10.3-x86_64
...ay 27 16:22:44 ian dovecot: IMAP(tkstest at foo-bar.de): Corrupted transaction log file /var/spool/virtuser/xxxxx/mail/INBOX./.imap/Trash/dovecot.index.log: unexpected end of file while reading header or: May 27 18:05:44 ian dovecot: IMAP(tkstest at foo-bar.de): file mail-index.c: line 1 900 (mail_index_move_to_memory): assertion failed: (index->fd == -1) May 27 18:05:44 ian dovecot: IMAP(tkstest at foo-bar.de): Raw backtrace: imap [0x4648be] -> imap [0x4645fe] -> imap [0x443834] -> imap [0x450b08] -> imap(mail_index_open+0x1df) [0x444e6f] -> imap(index_storage_mailbox_init+0x159) [0x43c119]...
2006 Oct 20
4
1.0.rc10 status report
....c: line 405 (mbox_sync_read_and_move): assertion failed: (need_space == (uoff_t)-mails[idx].space) child 30842 (imap) killed with signal 6 This looks particularly awkward. Any thoughts? 4. There were two occurences of: IMAP(...): file ../../../src/lib-index/mail-index.c: line 1801 (mail_index_move_to_memory): assertion failed: (index->fd == -1) child 20493 (imap) killed with signal 6 Again, this looks particularly awkward. Any thoughts? For these last two items, note that the indexes are currently NFS-shared alongside the INBOX area. I'm still not clear on how to regard the concept...