Hi!
I face in short intervals (every few minutes) such error-messages in dovecot
Feb 24 01:36:26 mail dovecot[699699]:
imap(user.name)<711331><0D3Ch9guy6UufflE>: Panic: file
mail-index-view.c: line 165 (view_lookup_full): assertion failed: (seq >
0 && seq <= mail_in
dex_view_get_messages_count
> On 15/03/2024 10:53 EET Michael Grant via dovecot wrote:
>
>
> I'm running dovecot 2.3.19.1 on debian stable. I just started seeing a
> slew of these in my log:
>
> Mar 14 10:02:38 strange.networkguild.org dovecot[865654]:
> imap(mgrant)<1939553>: Panic: file istream-header-filter.c:
>
I'm running dovecot 2.3.19.1 on debian stable. I just started seeing a slew of
these in my log:
Mar 14 10:02:38 strange.networkguild.org dovecot[865654]: imap
(mgrant)<1939553>: Panic: file istream-header-filter.c: line
663 (i_stream_header_filter_snapshot_free): assertion failed: (snapshot-
>mst
Sorry to reply to myself ;-) but I found a way around this panic.
After unsubscribe and subscribe again to my inbox folder the panics in
maillog suddenly stopped. Before I got the panic on EVERY click on my
inbox in MUA.
I was cleaning up my mailbox (moved and deleted a log of messages) when
the e
Hi list
since today I receive dovecot panics in my mail logs, whenever I want
to access on my inbox in my mailclient (evolution)
Details:
dovecot --version
2.3.17.1 (476cd46418)
Centos 7 (latest updates)
x86 architecture
mailbox stored in NFS
> Panic: file mail-index-transaction-finish.c: l
This has been fixed on later release. You are using very old version.
---Aki TuomiDovecot oy
Original message From: Eugen I Date:
08/08/2018 15:12 (GMT+02:00) To: dovecot@dovecot.org Subject: dovecot Panic:
file mail-index-sync-update.c: line 1013
An email came to several
An email came to several users but one user didn't receive it and we got
'Mail delivery failed' message.
As I see from the log below, there were broken index file.
Then dovecot repaired that index and we got the error:
Panic: file mail-index-sync-update.c: line 1013 (mail_index_sync_map):
assertio
Thanks, you were right, I had forgotten that there would be indexes for
each folder (of course). So I had done a 'find -maxdepth' type command
to find and delete them, and only hit the ones in Maildir. Now that I
have deleted all of them, there are no more errors.
On 01.03.2018 17:54, Aki Tuom
Hi!
The problem seems to occur during mail index processing. Can you try
deleting all dovecot.index* files under this user's maildir. There might
be some more under various folders.
Aki
On 03.01.2018 08:51, Owen B. Mehegan wrote:
> The EC2 instance that I run Dovecot on (personal mail server) w
The EC2 instance that I run Dovecot on (personal mail server) was
forcibly "retired" yesterday, and as a result I ended up rebuilding from
backups. In the process I switched from Ubuntu Precise to Ubuntu Xenial
(12.04 to 16.04), and this in turn caused me to upgrade Dovecot from
2.0.19 to 2.0.2
Unfortunately, I'm still getting the same errors post upgrade to 2.2.13.
I'm coming from 2.1.12, so perhaps there is some slight incompatibility
in some circumstances with the index files? I'm continuing to delete
them as this arises, and so far I've no repeat problem accounts.
Andy
---
Andy
I actually submitted the PR's. I'm waiting for the real maintainer to
approve or for the 2 week timeout.
As I said, it's doing great for me :)
On Fri, May 30, 2014 at 3:01 PM, Andy Dills wrote:
> Thanks to the suggestion by Larry off-list, I snagged an official patch
> from the FreeBSD PR an
Thanks to the suggestion by Larry off-list, I snagged an official patch
from the FreeBSD PR and now the ports are compiling cleanly.
I'll report back if I get the errors again.
Thanks,
Andy
---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
On 05/30/2014 15:34, Andy Dills wrote:
Hi t
Hi there,
We recently upgraded to 2.2.12 (the current version in FreeBSD's port
tree), and are seeing these errors in our logs (not super frequently,
but it happens):
May 30 13:20:57 mail1 kernel: pid 15752 (imap), uid 1005: exited on
signal 6
May 30 13:20:57 mail1 dovecot: imap(xxx): Fatal:
On 11.3.2014, at 22.00, Hardy Flor wrote:
> 2014 Mar 11 20:06:53 ptb-test imap(flor_hardy): Panic: file mail-index-map.c:
> line 547 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)
> 2014 Mar 11 20:06:53 ptb-test imap(flor_hardy): Fatal: master: service(imap):
> child 2760
Hi,
today I had the same problem with 2.2.12 on debian squeeze.
Here comes the log:
...
Apr 8 08:40:45 mailstoreul dovecot: imap(u...@domain.net pid:3618
session:<9cAjIG724wDD/uGI>): Panic: file mail-index-map.c: line 547
(mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)
Apr
On 2014-03-28 13:14, Alan McGinlay wrote:
On 2014-03-28 12:28, Robert Schetterer wrote:
Am 28.03.2014 12:22, schrieb Alan McGinlay:
While migrating users from Cyrus IMAP v2.3.14 to Dovecot 2.2.12
are you on latest patchlevel ?
I used this link:
http://www.dovecot.org/releases/2.2/dovecot-2.2.12
On 2014-03-28 12:28, Robert Schetterer wrote:
Am 28.03.2014 12:22, schrieb Alan McGinlay:
While migrating users from Cyrus IMAP v2.3.14 to Dovecot 2.2.12
are you on latest patchlevel ?
I used this link:
http://www.dovecot.org/releases/2.2/dovecot-2.2.12.tar.gz. Don't really
want to run absol
Am 28.03.2014 12:22, schrieb Alan McGinlay:
> While migrating users from Cyrus IMAP v2.3.14 to Dovecot 2.2.12
are you on latest patchlevel ?
see
http://hg.dovecot.org/dovecot-2.2/
there are some dsync fixes since 2.2.12
> (compiled from source) dsync aborts with a backtrace on some (maybe 15
While migrating users from Cyrus IMAP v2.3.14 to Dovecot 2.2.12
(compiled from source) dsync aborts with a backtrace on some (maybe 15
out of 800) mail accounts:
(same error happens wiht or without -f flag)
dsync -D -v -o mail_fsync=never mirror -f -R -u user@domain imapc:
dsync(u...@domain.
Zitat von Andreas Schulze :
Am 23.12.2013 17:40 schrieb Michael Cramer:
10-mail.conf:mail_attribute_dict =
file:/srv/vmail/dovecot/metadata/%d/%n/attributes
20-imap.conf:imap_metadata = yes
nothing more here but no no segfault.
I had also strange problems while using horde.
They went away aft
Version: 2.2.12
OS: Debian wheezy x86_64
2014 Mar 11 20:06:53 ptb-test imap(flor_hardy): Panic: file mail-index-map.c: line
547 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)
2014 Mar 11 20:06:53 ptb-test imap(flor_hardy): Fatal: master: service(imap):
child 2760 killed wi
On 12 Feb 2014, at 12:53 , LuKreme wrote:
> On 12 Feb 2014, at 10:16 , LuKreme wrote:
>> It doesn't appear to be affecting the user's ability to check mail (or at
>> least no complaints about that).
>
> He can check mail, he cannot RECEIVE mail.
I completely reinstalled dovecot, was still ge
On 12 Feb 2014, at 10:16 , LuKreme wrote:
> It doesn't appear to be affecting the user's ability to check mail (or at
> least no complaints about that).
He can check mail, he cannot RECEIVE mail.
--
Forget the Joneses. I can't keep up with The Simpsons.
dovecot: imap(j...@example.com): Error:
/usr/local/virtual/j...@example.com/dovecot.index: modseq_hdr.log_offset too
large
dovecot: imap(j...@example.com): Error:
/usr/local/virtual/j...@example.com/dovecot.index: modseq_hdr.log_offset too
large
dovecot: imap(j...@example.com): Panic: file mail
On 2014-01-27 2:19 AM, Kevin Holly wrote:
On 01/25/2014 01:38 PM, Charles Marcus wrote:
On 2014-01-25 5:56 AM, Kevin Holly wrote:
My client is Thunderbird, my dovecot version is 2.1.7-7 from the
official Debian repo. If you want to see my config i'll grab all the
fils together and send it to
On 01/25/2014 01:38 PM, Charles Marcus wrote:
> On 2014-01-25 5:56 AM, Kevin Holly wrote:
>> My client is Thunderbird, my dovecot version is 2.1.7-7 from the
>> official Debian repo. If you want to see my config i'll grab all the
>> fils together and send it to you.
>
> Have you asked on the debi
On 2014-01-25 5:56 AM, Kevin Holly wrote:
My client is Thunderbird, my dovecot version is 2.1.7-7 from the
official Debian repo. If you want to see my config i'll grab all the
fils together and send it to you.
Have you asked on the debian list, since you're running their
old/outdated version?
Hey guys,
i have a weird problem i'm trying to fix since 5 months now, but i
really couldn't find any explanation, why this happens and how it can be
fixed.
My client is Thunderbird, my dovecot version is 2.1.7-7 from the
official Debian repo. If you want to see my config i'll grab all the
fils t
In our previous episode (Monday, 13-Jan-2014), LuKreme said:
> Jan 13 19:09:07 mail dovecot: lda(j...@example.com): Panic: file
> mail-transaction-log-file.c: line 1148
> (mail_transaction_log_file_get_highest_modseq_at): assertion failed: (offset
> <= file->sync_offset)
> Jan 13 19:09:08 mail k
(I will not make a joke about the streets of Carlyle)
Jan 13 19:09:07 mail dovecot: lda(j...@example.com): Panic: file
mail-transaction-log-file.c: line 1148
(mail_transaction_log_file_get_highest_modseq_at): assertion failed: (offset <=
file->sync_offset)
Jan 13 19:09:08 mail kernel: pid 8435
This is log from dovecot 2.2.10:
2014-01-11T09:55:14+01:00 server/a.b.c.d dovecot: imap(user@domain):
Error: Corrupted transaction log file
/pracmail/domain/user/mail/.sent-mail/dovecot.index.log seq 16777216:
log file shrank (868 < 6144) (sync_offset=6144)
2014-01-11T09:55:14+01:00 server/a.b.c.d
Citando Robert Schetterer :
2.0.9 is old what about upgrade to recent 2.1.x, 2.2.x
the latest patchlevel of 2.0.x is 2.0.21 so minimum try upgrade to this,
your problem may allready got fixed
Upgrading to version 2.2.7 solved the problem. Thank you for the advice.
Best Regards,
--
Raúl
Am 05.01.2014 19:53, schrieb Raúl Massano Brás:
>
> Hi
>
> I am using dovecot 2.0.9 on CentOS 6.4
>
> The following error appears in the logs when users connect to the imap
> server using MACs. All
> other clients that I tested work fine.
>
> ## BEGIN ERROR ##
>
> Jan 5 18:04:25 mail
Hi
I am using dovecot 2.0.9 on CentOS 6.4
The following error appears in the logs when users connect to the imap
server using MACs. All
other clients that I tested work fine.
## BEGIN ERROR ##
Jan 5 18:04:25 mail dovecot: imap(jcf): Panic: file
mailbox-list-maildir.c: line 133:
Am 23.12.2013 17:40 schrieb Michael Cramer:
> 10-mail.conf:mail_attribute_dict =
> file:/srv/vmail/dovecot/metadata/%d/%n/attributes
> 20-imap.conf:imap_metadata = yes
nothing more here but no no segfault.
I had also strange problems while using horde.
They went away after I cleaned *all* files re
i have in my configs the following lines:
10-mail.conf:mail_attribute_dict =
file:/srv/vmail/dovecot/metadata/%d/%n/attributes
20-imap.conf:imap_metadata = yes
when i test GETMETADATA with telnet i got a pannic in my error.log
file and no attributes file in the given location is created
r
Am 12.12.2013 11:37, schrieb gio...@libero.it:
> Hi,
>
> We have a crash in dovecot 2.2.7
what about retry after upgrade to 2.2.9 ?
>
> 2013-12-11 10:38:44 imap(x...@example.com): Panic: file buffer.c: line 307
> (buffer_set_used_size): assertion failed: (used_size <= buf->alloc)
> 2013-12-1
Hi,
We have a crash in dovecot 2.2.7
2013-12-11 10:38:44 imap(x...@example.com): Panic: file buffer.c: line 307
(buffer_set_used_size): assertion failed: (used_size <= buf->alloc)
2013-12-11 10:38:44 imap(x...@example.com): Error: Raw backtrace: /opt/dovecot-
2.2.7/lib/dovecot/libdovecot.so.0(
Hello,
our dovecot mailservice was running smoothly for a long time.
Since last week we get the following error message when connecting
from the horde/imp webmailer
to the public namespace:
Panic: file acl-cache.c: line 294 (acl_cache_update): assertion
failed: (obj_cache->my_current_right
On 3.12.2013, at 23.33, Michael Kliewe wrote:
> I did a fresh installation of 2.2.9 in my test environment and enabled
> fts_autoindex=yes. I'm using a solr-server for FTS.
>
> I got this error, just once until now:
>
> _=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=
Hi,
I did a fresh installation of 2.2.9 in my test environment and enabled
fts_autoindex=yes. I'm using a solr-server for FTS.
I got this error, just once until now:
_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=
==> dovecot-lmtp-errors.log <==
Dec 03 16
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(
On 30 wrz 2013, at 07:54, Timo Sirainen wrote:
> On 28.9.2013, at 18.11, Kamil Andrusz wrote:
>
>> Sep 28 16:57:21 shwurzbung dovecot: imap(wizz): Panic: file mail-storage.c:
>> line 834 (mailbox_verify_name): assertion failed: (strncmp(vname,
>> ns->prefix, ns->prefix_len-1) == 0)
>
>> nam
On 28.9.2013, at 18.11, Kamil Andrusz wrote:
> Sep 28 16:57:21 shwurzbung dovecot: imap(wizz): Panic: file mail-storage.c:
> line 834 (mailbox_verify_name): assertion failed: (strncmp(vname, ns->prefix,
> ns->prefix_len-1) == 0)
> namespace {
> hidden = yes
> inbox = yes
> list = no
> loca
Hello List!
I've encountered an error after upgrading my system and dovecot. I guess it's
probably a result of a configuration problem, however after quite some
tinkering with configuration I am still missing the source of the problem.
Sep 28 16:57:21 shwurzbung dovecot: imap(wizz): Panic: file
Am 14.03.2013 07:54, schrieb Andre Rodier:
Hello Timo and everyone,
I am using dovecot 2.1 on debian7 with the fts-solr plugin, and everything is
working fine.
Dunno about the problem, but i recommend this repository:
deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.1 main
Greetings,
Thank you, I will try this soon !
Kind regards,
André Rodier.
On 14 March 2013 13:07, tmikaeld wrote:
> This happened to me too, i just downloaded the source for Dovecot 2.1.15 and
> used the Solr XML scheme from there instead of the one supplied with Ubuntu.
>
>
>
> --
> View this message in co
This happened to me too, i just downloaded the source for Dovecot 2.1.15 and
used the Solr XML scheme from there instead of the one supplied with Ubuntu.
--
View this message in context:
http://dovecot.2317879.n4.nabble.com/Panic-when-indexing-virtual-folder-with-solr-tp40764p40779.html
Sent fr
Hello Timo and everyone,
I am using dovecot 2.1 on debian7 with the fts-solr plugin, and everything is
working fine.
I have a Virtual folder with all emails, and when I run a doveadm index, I have
an error if I don't index real folders first. Example:
doveadm -v index -u 'andre rodier' 'Searc
Ok,
I found the issue.
The solr schema xml file was wrong, and I did not check the error logs
correctly. So, the error was in solr:
04-Mar-2013 15:15:30 org.apache.solr.common.SolrException log
SEVERE: org.apache.solr.common.SolrException: ERROR:unknown field 'uid'
at
org.apache.solr.up
This is my doveconf output. Please, note that since the panic, I have
switched to fts with squat, but it is very limited for large
mailboxes.
Any idea how to fix this?
# 2.1.7: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.0
auth_default_realm = indiefield.co.uk
auth_master_
Hello again,
Sorry for the duplicate post earlier.
My dovecot version is 2.1.7-7 (included in Debian Wheezy)
I don't think that addinf doveconf output would be useful, but I can add
it if you are interested.
Kind regards,
André Rodier
On 02/03/13 22:57, Andre Rodier wrote:
Hello All,
I ha
Hello All,
I have a panic error in dovecot when I try to use the fts search with Solr.
The version of dovecot I use is version 2.1
I have used a telnet session to search, but I don't know if this make a
difference:
telnet localhost imap
Trying 127.0.0.1...
Connected to localhost.
Escape char
Hello All,
I have a panic error in dovecot when I try to use the fts search with Solr.
The version of dovecot I use is version 2.1
I have used a telnet session to search, but I don't know if this make a
difference:
telnet localhost imap
Trying 127.0.0.1...
Connected to localhost.
Escape char
On 11/28/2012 8:49 AM, Daniel L. Miller wrote:
On 11/28/2012 12:55 AM, Timo Sirainen wrote:
On 28.11.2012, at 10.50, Daniel L. Miller wrote:
On 11/27/2012 6:45 PM, Timo Sirainen wrote:
On 28.11.2012, at 4.43, Daniel L. Miller wrote:
I did go through the code looking for that a few times alre
On 11/28/2012 12:55 AM, Timo Sirainen wrote:
On 28.11.2012, at 10.50, Daniel L. Miller wrote:
On 11/27/2012 6:45 PM, Timo Sirainen wrote:
On 28.11.2012, at 4.43, Daniel L. Miller wrote:
I did go through the code looking for that a few times already but didn't
notice anything. I went through
On 28.11.2012, at 10.50, Daniel L. Miller wrote:
> On 11/27/2012 6:45 PM, Timo Sirainen wrote:
>> On 28.11.2012, at 4.43, Daniel L. Miller wrote:
>>
I did go through the code looking for that a few times already but didn't
notice anything. I went through it once more, and finally found
On 11/27/2012 6:45 PM, Timo Sirainen wrote:
On 28.11.2012, at 4.43, Daniel L. Miller wrote:
I did go through the code looking for that a few times already but didn't
notice anything. I went through it once more, and finally found the problem. :)
http://hg.dovecot.org/dovecot-2.1/rev/6a97faf3e
On 28.11.2012, at 4.43, Daniel L. Miller wrote:
>> I did go through the code looking for that a few times already but didn't
>> notice anything. I went through it once more, and finally found the problem.
>> :) http://hg.dovecot.org/dovecot-2.1/rev/6a97faf3e500
>>
> :( Mine still breaks. Both
On 11/27/2012 1:07 PM, Timo Sirainen wrote:
On 27.11.2012, at 17.38, Daniel L. Miller wrote:
On 11/27/2012 7:28 AM, Daniel L. Miller wrote:
On 11/26/2012 10:08 PM, Timo Sirainen wrote:
On 27.11.2012, at 7.50, Timo Sirainen wrote:
Nov 26, 2012 8:49:29 PM org.apache.solr.common.SolrException
On 27.11.2012, at 17.38, Daniel L. Miller wrote:
> On 11/27/2012 7:28 AM, Daniel L. Miller wrote:
>> On 11/26/2012 10:08 PM, Timo Sirainen wrote:
>>> On 27.11.2012, at 7.50, Timo Sirainen wrote:
>>>
> Nov 26, 2012 8:49:29 PM org.apache.solr.common.SolrException log
> SEVERE: org.apache.so
On 11/27/2012 7:28 AM, Daniel L. Miller wrote:
On 11/26/2012 10:08 PM, Timo Sirainen wrote:
On 27.11.2012, at 7.50, Timo Sirainen wrote:
Nov 26, 2012 8:49:29 PM org.apache.solr.common.SolrException log
SEVERE: org.apache.solr.common.SolrException: Illegal character
((CTRL-CHAR, code 8))
at [
On 11/26/2012 10:08 PM, Timo Sirainen wrote:
On 27.11.2012, at 7.50, Timo Sirainen wrote:
Nov 26, 2012 8:49:29 PM org.apache.solr.common.SolrException log
SEVERE: org.apache.solr.common.SolrException: Illegal character ((CTRL-CHAR,
code 8))
at [row,col {unknown-source}]: [1011144,197790]
Some
On 27.11.2012, at 7.50, Timo Sirainen wrote:
>> Nov 26, 2012 8:49:29 PM org.apache.solr.common.SolrException log
>> SEVERE: org.apache.solr.common.SolrException: Illegal character ((CTRL-CHAR,
>> code 8))
>> at [row,col {unknown-source}]: [1011144,197790]
>
> Something's wrong. The Solr code was
On 27.11.2012, at 6.51, Daniel L. Miller wrote:
> On 11/26/2012 5:50 PM, Timo Sirainen wrote:
>> On 18.11.2012, at 16.54, Robert Strötgen wrote:
>>
>>> Nov 18, 2012 2:59:09 PM org.apache.solr.common.SolrException log
>>> SEVERE: org.apache.solr.common.SolrException: Invalid UTF-8 start byte
>>> 0
On 11/26/2012 5:50 PM, Timo Sirainen wrote:
On 18.11.2012, at 16.54, Robert Strötgen wrote:
Nov 18, 2012 2:59:09 PM org.apache.solr.common.SolrException log
SEVERE: org.apache.solr.common.SolrException: Invalid UTF-8 start byte
0xfc (at char #25214836, byte #26687495)
Annoying. I guess these f
On 11/26/2012 5:50 PM, Timo Sirainen wrote:
On 18.11.2012, at 16.54, Robert Strötgen wrote:
Nov 18, 2012 2:59:09 PM org.apache.solr.common.SolrException log
SEVERE: org.apache.solr.common.SolrException: Invalid UTF-8 start byte
0xfc (at char #25214836, byte #26687495)
Annoying. I guess these f
On 18.11.2012, at 16.54, Robert Strötgen wrote:
> Nov 18, 2012 2:59:09 PM org.apache.solr.common.SolrException log
> SEVERE: org.apache.solr.common.SolrException: Invalid UTF-8 start byte
> 0xfc (at char #25214836, byte #26687495)
Annoying. I guess these fix it:
http://hg.dovecot.org/dovecot-2.1
Hi!
I use dovecot 2.1.7 on Ubuntu 12.10 with fts_solr und decode2text.sh for
indexing attachments. This works great in general.
Just for one user there is a problem with an unknown bad attachment.
I run "doveadm index -A '*'". After a while I receive:
doveadm(xyz): Error: fts_solr: Invalid XML
The assert crash I think is fixed already in v2.1.9. The folder structure can
be changed with mail_shared_explicit_inbox=no
On 16.8.2012, at 14.30, Claus Rosenberger wrote:
> Could i send some more informations about this topic? I'm not sure whats
> happening here but i think it has something to
Could i send some more informations about this topic? I'm not sure whats
happening here but i think it has something to do with the shared mailboxes.
With cyrus i had following folder structure:
user1 -> inbox -> subfolders
-> user -> user1
-> user2
With dovecot
Hi,
with fetching the folder structure with the webclient Tine i can see following
error messages inside of the logfiles:
Panic: file mail-storage.c: line 791 (mailbox_check_mismatching_separators):
assertion failed: (strncmp(vname, ns->prefix, ns->prefix_len-1) == 0)
Error: Raw backtrace: /us
On Mon, May 07, 2012 at 11:45:52PM +0300, Timo Sirainen wrote:
> On 7.5.2012, at 23.40, Leon Meßner wrote:
>
> > with dovecot-1.2.17 (yes i know it's old) i'm getting the folowing error
> > after doing a system upgrade.
> >
> > May 7 22:04:26 mail dovecot: deliver(elon): Panic: file index-sync.c
On 7.5.2012, at 23.40, Leon Meßner wrote:
> with dovecot-1.2.17 (yes i know it's old) i'm getting the folowing error
> after doing a system upgrade.
>
> May 7 22:04:26 mail dovecot: deliver(elon): Panic: file index-sync.c: line
> 25 (index_mailbox_set_recent_uid):
> assertion fai
Hi,
with dovecot-1.2.17 (yes i know it's old) i'm getting the folowing error
after doing a system upgrade.
May 7 22:04:26 mail dovecot: deliver(elon): Panic: file index-sync.c: line 25
(index_mailbox_set_recent_uid):
assertion failed: (seq_range_exists(&ibox->recent_flags, uid)
We had the same problem. Reboot with an older kernel
(2.6.18-274.17.1.el5 works for us). It is known bug of RHEL, see this
bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=681578
Regards
Javier
On Thu, 29 Mar 2012 10:15:32 +0200 (CEST), FABIO FERRARI
wrote:
> Good morning,
> we h
Good morning,
we have 2 Redhat Enterprise 5.7 machines, they are a cluster with some
mail services in it (postfix and dovecot 2).
The version of dovecot is dovecot-2.0.1-1_118.el5 (installed via rpm).
>From last week we have this dovecot problem: suddenly dovecot doesn't
accept any new connection
Am 10.01.2012 16:32, schrieb Jürgen Obermann:
I have the following problem with doveadm:
# gdb --args /opt/local/bin/doveadm -v mailbox status -u
userxy/g029 'messages' "Software-alle/AK-Software-Tagung"
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered b
Hallo,
I have the following problem with doveadm:
# gdb --args /opt/local/bin/doveadm -v mailbox status -u userxy/g029
'messages' "Software-alle/AK-Software-Tagung"
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
Over the weekend I updated the OS on the machine in question to Fedora
15, which should have updated libcurl in the process, and I'm still
getting the same error message. I also moved Solr to another server
instead of trying to use it on the local box, but that didn't seem to
make a difference.
O
It happens every time. Also, I just recompiled for version 2.0.16 and it
gives me the same error (pasted below). I'll be updating the OS on this
machine soon, which will update libcurl as well.
Panic: file solr-connection.c: line 501 (solr_connection_post_more):
assertion failed: (maxfd >= 0)
Erro
On Fri, 2011-12-02 at 12:47 -0600, A Dovecot User wrote:
> [root@mymailserver ~]# doveadm -D index -u username mailbox inbox
The "mailbox" isn't necessary above.
> doveadm(username): Info: INBOX: Caching mails seq=1..466
> doveadm(username): Panic: file solr-connection.c: line 545
> (solr_connect
Dovecot version: 2.1.rc1
Expat version: expat-2.0.1-10
Libcurl version: libcurl-7.21.0-10
OS: Fedora 14 i686
Configure command: ./configure --with-solr
Solr version: 1.4.1 (also tried 3.5.0)
Java version: java-1.6.0-openjdk-1.6.0.0-55.1.9.10 (also tried Oracle
Java 6u29)
[root@mymailserver ~]# d
On Thu, Sep 29, 2011 at 04:09:02PM +0100, mailing lists wrote:
> Hello all,
>
> today I got this crash from dovecot (2.0.14)
FYI: You're not alone..
http://dovecot.org/list/dovecot/2011-September/060830.html
I seem to remember thinking this probably was caused by too short
LMTP_PROXY_DA
Hello all,
today I got this crash from dovecot (2.0.14)
Sep 29 14:09:32 imap1 dovecot: lmtp(17693): Panic: file lmtp-proxy.c: line 370
(lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof)
Sep 29 14:09:32 imap1 dovecot: lmtp(17693): Error: Raw backtrace:
/usr/lib64/dovecot/li
Many thanks, works.
Regards
Urban
Timo Sirainen wrote:
On Wed, 2011-06-22 at 10:02 +0200, Urban Loesch wrote:
# doveadm quota get -A
doveadm: Panic: file doveadm-print-table.c: line 58
(doveadm_calc_header_length): assertion failed: ((value_count % hdr_count) == 0)
Fixed: http://hg.doveco
On Wed, 2011-06-22 at 10:02 +0200, Urban Loesch wrote:
> # doveadm quota get -A
> doveadm: Panic: file doveadm-print-table.c: line 58
> (doveadm_calc_header_length): assertion failed: ((value_count % hdr_count) ==
> 0)
Fixed: http://hg.dovecot.org/dovecot-2.0/rev/02d97fb66047
Hello Timo,
Today I've moved one message from INBOX to a virtual folder which made
imap processes crash as soon as INBOX was selected.
Jun 24 17:24:50 server dovecot: imap(u...@example.com): Panic: file
mail-index-view.c: line 149 (view_lookup_full): assertion failed: (seq >
0 && seq <= mail
Hi,
I'm new to the list and I'm using dovecot since 2 months. Still in progress to
migrating from Stalker (Communigate Pro) to Dovecot.
Today I upgraded from Dovecot 2.0.13-0~auto+27 (used form the Mirror
xi.rename-it.nl - stable-auto) to 2:2.0.13-0~auto+48.
List of installed packages:
ii do
On Mon, 2011-01-17 at 00:23 +0100, Holger Mauermann wrote:
> I converted personal mailboxes from maildir to sdbox. Public mailboxes
> are still in maildir format, because I need per-user seen flags.
> However, if the user is subscribed to public mailboxes and the client
> sends 'LIST (SUBSCRIBED) "
Hi,
Crash gone on my side. Thanks Timo, it fixed it.
On 21 Jan 2011, at 23:33, Mike Abbott wrote:
>> I can't think of why any client would send IDLE+DONE in the same TCP packet.
>
> Maybe not in the same packet, but network congestion or server overloading
> could cause the IDLE and DONE to q
> I can't think of why any client would send IDLE+DONE in the same TCP packet.
Maybe not in the same packet, but network congestion or server overloading
could cause the IDLE and DONE to queue up together.
> Oh, that's nice.
Glad to help.
> Fixed now: http://hg.dovecot.org/dovecot-2.0/rev/4741
On Fri, 2011-01-21 at 12:56 -0600, Mike Abbott wrote:
> >> Jan 17 12:06:20 server dovecot: imap(@YYY): Panic: file
> imap-client.c: line 570 (client_continue_pending_input): assertion
> failed: (!client->handling_input)
>
> I can reproduce this every time by sending any data in the same pa
>> Jan 17 12:06:20 server dovecot: imap(@YYY): Panic: file
>> imap-client.c: line 570 (client_continue_pending_input): assertion failed:
>> (!client->handling_input)
I can reproduce this every time by sending any data in the same packet after
the "tag IDLE". For instance using nc:
$ nc
> Jan 17 12:06:20 server dovecot: imap(@YYY): Panic: file
> imap-client.c: line 570 (client_continue_pending_input): assertion failed:
> (!client->handling_input)
I just saw this with 2.0.8 too. Backtrace is:
0 __kill + 10
1abort + 177
20x10d928000 + 143594
30x10d928000 +
Hi,
Yesterday I upgraded one of our system from 2.0.7 to 2.0.9, I've got about 5
panic since then. It is using the exact same config (see attached) and was
compiled the same way. Any clue on the reason? And how can I fix that?
Jan 17 12:06:20 server dovecot: imap(@YYY): Panic: file imap
I converted personal mailboxes from maildir to sdbox. Public mailboxes
are still in maildir format, because I need per-user seen flags.
However, if the user is subscribed to public mailboxes and the client
sends 'LIST (SUBSCRIBED) "" *', dovecot crashes with:
imap(hol...@mauermann.org): Panic: fil
Hello!
Got a panic&assertion failed with LMTP proxy. Target Dovecot LMTP
server hanged and Dovecot LMTP proxy server started logging
panics/assertions. Core dumps were disabled unfortunately, so I don't
know if this is helpful at all:
Dec 29 15:41:58 lmtp(8853): Panic: file lmtp-proxy.c:
W dniu 2010-09-10 13:28, Len7hir wrote:
> I have version 2.0.0 and upgraded to 2.0.2 and after - this is happend:
>
> Raw backtrace:
> /opt/dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e3425e] ->
> /opt/dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e342b5] ->
> /opt/dovecot2/lib/dovecot/libdovecot.so.0 [
1 - 100 of 256 matches
Mail list logo
