similar to: Corrupted transaction log file, dotlocks..?

Displaying 20 results from an estimated 2000 matches similar to: "Corrupted transaction log file, dotlocks..?"

2005 May 28
0
Transaction log file issue on dovecot-stable
Situation: dovecot-stable-20050528 on x86, Linux 2.4.30, ext3, maildir I'm trying to use the imapsync utility (http://www.linux-france.org/prj/imapsync/) to copy 1500 messages from a UW-imap server to dovecot. After about 100 messages are successfully appended, I'm seeing this in the server log, following which all APPENDs fail. May 28 09:01:06 [dovecot] IMAP(allen):
2006 Dec 03
0
Marking all messages in folder as read doesn't work
> > My only guess is that the imap process doesn't have permissions to > rename the files. >This seems plausible. I'll have another look at the permissions. Timo, On this specific point I cannot see anything wrong on my system. The maildir folders all have permissions 0700 and the messages in all folders 0600. Owner and group are the same throughout all my folders. John
2015 Oct 10
0
Syncronizing two IMAP servers
On 10/10/2015 13:22, Timothy Murphy wrote: > I spend time in two places, in different countries. > I have a local network in each place, > with IMAP servers on each network. > I collect email by fetchmail from various servers, > and read email on my laptop with KMail. > > I tried using just one IMAP server, but this proved impractical. > So I have two collections of the
2012 Sep 21
3
Dovecot 1.2.11 panic in mail-transaction-log-view?
I'm seeing this periodically in my logs for a specific user (followed by a backtrace which I've deleted from this post): Panic: file dovecot-1.2.11/src/lib-index/mail-transaction-log-view.c: line 290 (mail_transaction_log_view_set): assertion failed: (min_file_seq != max_file_seq || max_file_seq != view->head->hdr.file_seq || max_file_offset != (uoff_t)-1 || min_file_offset <=
2005 Mar 06
4
mail-cache-transaction.c error
Hello all. I've just recently (this last weekend) migrated to Dovecot on my FreeBSD 4.x box. So far, so good, I like it a lot, and plan on moving mboxes to Maildirs sometime this next weekend. BUT....I've currently run into a problem. I'm seeing an error when one user account tries to access the INBOX from Squirrelmail: Mar 6 16:50:59 cerebus dovecot: IMAP(problemuser): file
2004 Jun 18
3
1.0-test17
http://dovecot.org/test/ Just mbox fixes since 1.0-test16. The logic is simpler and more correct now. Can anyone break it anymore? I actually tested it a while with Evolution and several mailboxes and it didn't break at least immediately. :) Now maybe a few more days and I dare trying this thing myself with my real mboxes (yes, I'm still using them). Dovecot mailing list archives could
2006 Feb 25
1
dovecot-1.0-beta3 in production
Hello there! I've migrated our courier-imap production imap/pop server to dovecot 1.0-beta few days ago. In general dovecot performs excellent, but i've encountered several "bugs" in dovecot log: --- snip --- dovecot.log.1.gz:Feb 24 16:05:21 elfstone dovecot: imap(user3 at domain.tld): Maildir /export/mail/domain.tld/user3 sync: UID inserted in the middle of mailbox (47681
2011 Feb 08
1
How to recover a mail box from an assertion failure
I'm running Dovecot version 1.2.11 and getting this assertion error on a user's mail: Panic: file /home/durket/dovecot-1.2.11/src/lib-index/mail-transaction-log-view.c: line 290 (mail_transaction_log_view_set): assertion failed: (min_file_seq != max_file_seq || max_file_seq != view->head->hdr.file_seq || max_file_offset != (uoff_t)-1 || min_file_offset <=
2008 Aug 05
1
Corrupted transaction logs
Hi, I'm getting a lot of the following messages in my mail.err log. Jul 12 11:25:51 mink dovecot: IMAP(user1 at domain1.net): Corrupted transaction log file /virtual/store1/mail/u/user1_domain1.net/Maildir/.Sent/dovecot.index.log: Append with UID 925, but next_uid = 926 Jul 12 12:44:56 mink dovecot: IMAP(user2 at domain1.net): Corrupted transaction log file
2008 Jul 10
2
file mail-transaction-log-view.c: assertion failed (v1.0.12)
Hi all. Looking at previous weeks logs I discovered strange errors: "file mail-transaction-log-view.c: assertion failed" dovecot v 1.0.12 Server is hosting more than 500 virtual users. It is compleate dovecot error log; only my own mailbox is affected ...and imap folder affected is "dovecots mailing list" :) While "Corrupted transaction log file" as far as I know
2015 Nov 03
0
dovecot-lda can't create /var/mail dotlocks on debian
what is the full permissions of /var/mail? ls -lda /var/mail On Tue, Nov 3, 2015 at 1:49 PM, John Clements <johnbclements at gmail.com> wrote: > I've been using dovecot+postfix happily for many years, and I'm now > configuring it for a new machine. However, I'm running into an old problem > again, and thinking that there must be a better solution. > > The
2015 Nov 03
0
dovecot-lda can't create /var/mail dotlocks on debian
Hrm. if you turn up the debug on lda, do you get any more of a clue? Those permissions look fine to me. On Tue, Nov 3, 2015 at 2:10 PM, John Clements <johnbclements at gmail.com> wrote: > clements at desmond:/var/log$ ls -lda /var/mail > drwxrwsr-x 2 root mail 4096 Nov 2 22:07 /var/mail > > > Best, > > John Clements > > On Tue, Nov 3, 2015 at 11:52 AM, Larry
2010 Jan 28
0
assertion mail-transaction-log-view.c
I'm not sure how useful this is with optimization turned back on, but here it is anyway. This was just a one off that happened last night: Jan 27 20:49:05 gehenna17.rutgers.edu dovecot: IMAP(user): fscking index file /rci/nqu/rci/u2/user/dovecot/.INBOX/dovecot.index Jan 27 20:49:05 gehenna17.rutgers.edu dovecot: IMAP(user): Panic: file mail-transaction-log-view.c: line 108
2015 Nov 03
0
dovecot-lda can't create /var/mail dotlocks on debian
Well, first, here are the logs I generated: Nov 3 12:23:05 desmond dovecot: lda(granitemon): Debug: Effective uid=1003, gid=1003, home=/home/granitemon Nov 3 12:23:05 desmond dovecot: lda(granitemon): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mbox:~/mail:INBOX=/var/mail/granitemon Nov 3 12:23:05 desmond dovecot:
2013 Jan 25
1
assert in mail-transaction-log-file.c
I setup new server with dovecot 2.1.12 and mboxes from backup (moboxes was used with dovecot 1.1.6). OS: FreeBSD 8.3-STABLE, amd64. All index files from dovecot 1.1.6 has been deleted. Some times dovecot processes aborted. E. g. Jan 25 03:01:52 ost dovecot: lda(user at example.ru): Panic: file mail-transaction-log-file.c: line 1694 (mail_transaction_log_file_map): assertion failed:
2007 Mar 16
1
corrupted transaction log error resulting in multiple deliveries
I'm finally picking my dovecot project back up now, and after upgrading rc19 to rc27, I sent a test message to an existing account which resulted in log entries like these: Mar 16 08:45:37 node7 deliver(user at example.com): Corrupted transaction log file /var/indexes/example/com/u/us/user/.INBOX/dovecot.index.log: Append with UID 3, but next_uid = 15368 Mar 16 08:45:37 node7
2006 Sep 20
0
Corrupted Transaction Log caused by deliver
Hi All, I've just upgraded to Dovecot 1.0.rc7-1 with Postfix 2.3 on Debian Etch and it's trashing my email. I get lots of the errors below as well as other strange ones in my logs. I don't use NFS. Mail comes in via Postfix, gets passed through MailScanner, gets passed back to Postfix and then Postfix passes it to Dovecot's LDA via: mailbox_command = /usr/lib/dovecot/deliver
2010 Oct 26
1
Corrupted transaction log file
Hello I run dovecot 2.0.6 on a two-machine cluster using OCFS2 as the file system. I have some error messages like these in my log: Oct 25 01:07:50 box5 dovecot: lmtp(8886, suporte=100br.com at lmtp1.prv.f1.k8.com.br): Error: Corrupted transaction log file /var/lib/imap/user/a3/suporte=100br.com/stor age/dovecot.map.index.log seq 29: Transaction log corrupted unexpectedly at 21536: Invalid size
2015 Nov 03
2
dovecot-lda can't create /var/mail dotlocks on debian
I've been using dovecot+postfix happily for many years, and I'm now configuring it for a new machine. However, I'm running into an old problem again, and thinking that there must be a better solution. The problem is that dovecot-lda is unable to create dotlock files in the /var/mail directory. Dovecot version: 1:2.2.13-12~deb8u1 (I'm guessing this is upstream version 2.2.13) OS:
2015 Nov 03
2
dovecot-lda can't create /var/mail dotlocks on debian
clements at desmond:/var/log$ ls -lda /var/mail drwxrwsr-x 2 root mail 4096 Nov 2 22:07 /var/mail Best, John Clements On Tue, Nov 3, 2015 at 11:52 AM, Larry Rosenman <larryrtx at gmail.com> wrote: > what is the full permissions of /var/mail? > > > ls -lda /var/mail > > On Tue, Nov 3, 2015 at 1:49 PM, John Clements <johnbclements at gmail.com> > wrote: >