similar to: 604995471 7500 routers / upgrade issue

Displaying 20 results from an estimated 120 matches similar to: "604995471 7500 routers / upgrade issue"

2007 Jan 25
1
X-UID gaps cause Dovecot/IMAP to hang
Hi, When the Dovecot 1.0.rc19 IMAP server encounters X-UID headers with gaps in them, it hangs indefinitely. I've attached a sample mailbox (in mbox format) which repeatably exhibits this behavior. The mbox contains only three messages with the following X-UIDs in order: 774, 785, 787. If I remove the X-UID headers from each message, Dovecot handles the mailbox without any problems. UW-IMAP
2005 Oct 21
1
1.0alpha4: mbox-lock asserts and cores
Timo, I upgraded from alpha3 to alpha4 yesterday, and I am seeing a few of the following asserts: imap(user): file mbox-lock.c: line 379 (mbox_lock_fcntl): assertion failed: (lock_type == F_UNLCK) Gdb info on a couple of the cores is attached. It looks like the arg lock_type for mbox_lock_fcntl() is not getting passed in correctly, like the enum "enum mbox_lock_type type" in
2009 Feb 04
4
pop3_lock_session question
Hello, I'm preparing to convert from qpopper + UW-IMAP to dovecot. So far testing has gone very well. One problem we haven't figured out is that long-running POP sessions keep the mailbox locked, so that the MDA times out while trying to deliver. We're using "maildrop" as our MDA if that matters. We don't see this issue for dovecot IMAP sessions. During long-running
2008 Oct 04
2
Dovecot 1.1.3 crash & backtrace
Backtrace:/usr/local/libexec/dovecot/imap GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB
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 - >>>
2018 Dec 04
3
[2.3.4] Segmentation faults
Thanks for mySql For Squat vs Solr, Solr does not reach Squat by very far in terms of results : If I setup Solr, and search (via the search in Roundbube or Evolution) for a keyword or part of the keyword, the results are complete non sense. The diference between "search in full body" and "search in fields" does not even work. Solr with Dovecot seems very early beta
2018 Nov 29
3
[2.3.4] Segmentation faults
finally managed to locate the dump here the output: # gdb /usr/libexec/dovecot/auth /var/lib/systemd/coredump/core.auth.0.3a33f56105e043de802a7dfcee265a07.28130.1543516118000000 GNU gdb (GDB) 8.2 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it.
2018 Dec 04
2
[2.3.4] Segmentation faults
Hi How to solve this ? So many similar segfaults Thank you On 2018-11-30 06:11, Joan Moreau wrote: > ANother (very very long) example : > > # gdb /usr/libexec/dovecot/indexer-worker core.indexer-worker.0.3a33f56105e043de802a7dfcee265a07.21017.1543533424000000 > GNU gdb (GDB) 8.2 > Copyright (C) 2018 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or
2004 Jul 20
3
Bug? 1.0.0-test28 NFS locking problems
Hi Slight problem - linux 2.4 running dovecot, Solaris 2.8 home directory server. Full lockd support etc. I had to make the following code patches (at end of mail for clarity) to get dovecot to read the users mbox files at all. 1) fcntl with F_SETLKW will not work against a Solaris 2.8 server as proved with a small test program. Other forms of fcntl (ie F_SETLK) are OK. I noticed there are
2004 Mar 10
9
Lock contention issue with ocfs
I am still having this weird problem with nodes hanging while I'm running OCFS. I'm using OCFS 1.0.9-12 and RHAS 2.1 I've been working on tracking it down and here's what I've got so far: 1. I create a file from node 0. This succeeds; I can /bin/cat the file, append, edit, or whatever. 2. From node 1, I do an operation that accesses the DirNode (e.g. /bin/ls) 3. Node 0
2004 Mar 10
9
Lock contention issue with ocfs
I am still having this weird problem with nodes hanging while I'm running OCFS. I'm using OCFS 1.0.9-12 and RHAS 2.1 I've been working on tracking it down and here's what I've got so far: 1. I create a file from node 0. This succeeds; I can /bin/cat the file, append, edit, or whatever. 2. From node 1, I do an operation that accesses the DirNode (e.g. /bin/ls) 3. Node 0
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
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 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
2018 Dec 04
2
[2.3.4] Segmentation faults
> On December 4, 2018 at 8:18 AM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > We don't consider it as "very early beta". We consider it production ready. It is bit more work to set up though. FWIW, Squat has been deprecated since 2.0, so none of this should come as a surprise. https://wiki.dovecot.org/Plugins/FTS > Aki > > > On 04 December
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
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,
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
2008 Sep 03
3
1.1.3 panics
Hi, Installed Dovecot 1.1.3 today and started receiving panic errors on a few of our users: dovecot: [ID 107833 mail.crit] Panic: IMAP(xx): file mail-index-transaction-view.c: line 204: unreached When I upgraded, I deleted all of our users index files so it started with a clean slate. We are running mbox format over NFS with fsquota plugin on Solaris 8. Here is output of dovecot -n: