Displaying 20 results from an estimated 900 matches similar to: "Can't connect to auth server at default: Connection refused"
2016 Apr 21
2
Setting up replication?
On 4/21/2016 12:01, Timo Sirainen wrote:
> On 21 Apr 2016, at 19:51, Knute Johnson <dovecot at knutejohnson.com> wrote:
>> On 4/21/2016 04:33, Aropalo Tommi wrote:
>>>> I'm trying to set up replication between two servers and I've hit a
>>>> snag. I have two users and am using mbox files. If anybody has a
>>>> sample config file for a
2005 Nov 18
0
Two new Assert Failures
These two are from CVS version as of 2005-11-03.
There have only been these two asserts and we've had over 45000 logins.
----------------------------------------------------------------------
dovecot: Nov 16 13:35:34 Error: 18439
imap(username): Corrupted transaction log file
/mailhome/new/c/h/username/.imap/INBOX/dovecot.index.log: Append with
UID 53103, but next_uid = 53104
dovecot: Nov
2013 May 31
1
dsync assert failure in 2.2.2
Hi,
with 2.2.2 and today's hg, dsync crashes with
dsync(root): Panic: file ../../../../../src/lib-storage/index/mbox/mbox-lock.c: line 797 (mbox_lock): assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type != F_RDLCK)
when I run
USER=root 2.2-hg/bin/dsync -c etc/dovecot.conf -f -o mail_location=mbox:/tmp/imap/fwadmin.tmp:INBOX=/tmp/imap/fwadmin.tmp/INBOX mirror
2020 Oct 11
2
Preparing for replication: dsync-local(testaccount): Panic: file mbox-lock.c
I am preparing a bit for setting up replication. However when I manually
try to dsync an account, the first time I execute this[1] command it
seems to be ok. The 2nd time I am getting this error[2].
If I add -1 (one way syncing) the error disappears. Does this mean I
will have problems with setting up replication between these two
servers?
[1]
[@ ~]# doveadm sync -n inbox -u testaccount
2017 Sep 26
3
dsync: assert panic on mbox // no INBOX sync on hybrid mbox/maildir
Hi,
This (hopefully!) might be a case of user error, as I'm new to
dovecot... Alternatively it might be some confusion in an index, since
I've been mucking about trying different things in my configuration
files and had frequent crashes.
I'm trying to sync 2 (LAN) hosts, ideally to have full automatic
replication happening.
They both have hybrid mbox INBOX and maildir++ folders,
2017 Sep 16
2
dsync panic in mbox_lock
Hello
I am trying to setup replication with dovecot-2.2.29.1, and for some
users, I get a reproductible panic:
# doveadm -v -o plugin/mail_replica=remoteprefix:root at mail2.example.net
sync -d -u jdoe
dsync-local(jdoe): Panic: file mbox-lock.c: line 799 (mbox_lock):
assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type !=
F_RDLCK)
Abort
User is not overquota, and filesystem
2016 Apr 21
2
Setting up replication?
On 4/21/2016 04:33, Aropalo Tommi wrote:
>> I'm trying to set up replication between two servers and I've hit a
>> snag. I have two users and am using mbox files. If anybody has a
>> sample config file for a simple system like mine I would really be
>> grateful to see it.
>> Thanks,
>> The error I'm getting is:
>> Mar 23 14:07:31 knute2
2005 Oct 14
0
1.0a3: assert and core dump
Timo,
A rare assert and core dump out of 1.0alpha3. My setup:
Solaris 9, mbox format, using imap only. Built dovecot
with gcc 4.0.1. The syslog for this was:
Oct 14 11:57:56 emerald dovecot: [ID 107833 mail.info] imap-login: Login: user=<epmccull>, method=PLAIN, rip=137.146.210.59, lip=137.146.210.52, TLS
Oct 14 11:58:56 emerald dovecot: [ID 107833 mail.info] imap-login: Login:
2005 Apr 27
0
Assertion Failures in Current CVS version
I've attached a few assertion errors in imap. Any fixes or advice on
where to look are appreciated.
This is with the CVS version, current as of April 27.
Todd Burroughs
-------------- next part --------------
dovecot: Apr 27 00:00:45 Error: 5714 IMAP(chairman): file mail-index-transaction.c: line 808 (mail_index_update_ext): assertion failed: (seq > 0 && (seq <=
2014 Aug 26
0
Running dsync results in Panic: file mbox-lock.c: line 799 (mbox_lock)
Hello,
I'm converting our system to use dovecot. As part of the migration we
need to convert existing mbox'es to Maildir format. I'm using latest
Dovecot2 available as FreeBSD pkg - 2.2.13.
I'm trying to use dsync, which results in:
./dsync -vfu ppaczyn -o
mail_location=mbox:~/mail:INBOX=/var/mail/ppaczyn mirror
maildir:~/Maildir
dsync(ppaczyn): Panic: file mbox-lock.c: line 799
2004 Dec 01
2
1.0-test CVS HEAD index problems
Running current CVS HEAD I get:
dovecot: Dec 01 13:27:38 Info: Dovecot v1.0-test52 starting up
dovecot: Dec 01 13:33:34 Info: imap-login: Login: jtl [69.162.177.245]
dovecot: Dec 01 13:41:07 Error: IMAP(jtl): UIDVALIDITY changed
(1100294646 -> 110192643
5) in mbox file /var/spool/mail/j/t/jtl
dovecot: Dec 01 13:41:07 Error: IMAP(jtl): UIDVALIDITY changed
(1100294646 -> 110192643
5) in
2017 Sep 16
0
dsync panic in mbox_lock
> On September 16, 2017 at 5:28 AM Emmanuel Dreyfus <manu at netbsd.org> wrote:
>
>
> Hello
>
> I am trying to setup replication with dovecot-2.2.29.1, and for some
> users, I get a reproductible panic:
>
> # doveadm -v -o plugin/mail_replica=remoteprefix:root at mail2.example.net
> sync -d -u jdoe
> dsync-local(jdoe): Panic: file mbox-lock.c: line 799
2008 Aug 25
2
Dovecot 1.1.2
Hello,
I upgraded dovecot to 1.1.2 this weekend and i get those errors:
grep dovecot /var/log/net/maillog |grep Panic | cut -d " " -f 11-100|
sort | uniq -c | sort -rn
7547 file index-sync.c: line 39: assertion failed:
(seq_range_exists(&ibox->recent_flags, uid))
89 file index-mail.c: line 1091: assertion failed: (!
mail->data.destroying_stream)
18 file
2017 Sep 27
0
dsync: assert panic on mbox // no INBOX sync on hybrid mbox/maildir
Hi,
replying to my own issue:
The dsync crash seems to be triggered when there are emails to copy in
both directions, and it's fairly clear from comments in the code that
it should be releasing a read lock before trying to grab a write lock.
A work-around for the crash was doing a one-way sync manually. This
allowed the process to complete and my setup is now replicating
properly. I guess
2014 May 16
0
syncing problems Dovecot 2.2.13
Hi,
we still migrate a couple of users from mbox to maildir.
Most of them are fine without any problem.
Some crash and dont get all mails synced.
first I sync backup the mbox to a maildir-NEW, than copy mbox to a new
name, mv maildir-NEW to maildir.
Now some problematic mailusers miss some mails from the old mbox, so I
start a dsync mirror and BAM crash.
e.g.:
dsync(s108019): Panic: file
2004 Sep 28
3
Moving mail dirs
Hi all,
This is probably a silly question, but I have a problem. I've had to
move my users maildirs from:
maildir:/home/%u/.Maildir
To
maildir:/data/mail/%u
I've updated the MTA to put mail to the correct place and it's working
fine. I've also changed the dovecot.conf file and restarted dovecot and
I thought that would be all I needed to do.
However, the users are getting
2020 Oct 12
0
Preparing for replication: dsync-local(testaccount): Panic: file mbox-lock.c
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div class="default-style">
Replication is not supported with mbox format. You can only do unidirectional sync out of mbox.
</div>
<div class="default-style">
<br>
</div>
<div
2013 Nov 15
0
Dovecot panic during replication
I'm seeing the following errors on my Dovecot box when trying to replicate:
Nov 15 18:44:46 server1 dovecot: dsync-server(mark): Panic: file
mbox-lock.c: line 799 (mbox_lock): assertion failed: (lock_type == F_RDLCK
|| mbox->mbox_lock_type != F_RDLCK)
Nov 15 18:44:46 server1 dovecot: dsync-server(mark): Fatal: master:
service(doveadm): child 21571 killed with signal 6 (core not dumped -
2004 Oct 05
0
1.0-test46: Assertion failed
Hi,
I'm experiencing there assertions in the mail log (about 8 times during
the last 2 days):
Oct 5 11:20:51 web dovecot: POP3(xxxxx): file mbox-lock.c: line 493
(mbox_lock): assertion failed: (lock_type == F_RDLCK ||
ibox->mbox_lock_type != F_RDLCK)
What is it? I'm running 1.0-test46 and sendmail on FC2. This is in
dovecot.conf:
#fcntl_locks_disable = no
#mbox_read_locks = fcntl
2013 Nov 11
0
dsync-server panic/fatal errors
Would anyone like to hazard a guess what these errors mean:
Nov 11 18:57:04 server2 dovecot: dsync-server(mark): Panic: file
mbox-lock.c: line 799 (mbox_lock): assertion failed: (lock_type == F_RDLCK
|| mbox->mbox_lock_type != F_RDLCK)
Nov 11 18:57:04 server2 dovecot: dsync-server(mark): Fatal: master:
service(doveadm): child 3119 killed with signal 6 (core not dumped - set
service doveadm {