(usern...@domain.de): Panic: file
http-client-request.c: line 521 (http_client_request_send_more): assertion
failed: (req-payload_input != NULL)
It crashed because the HTTP request failed and it tried to auto-retry, which
doesn’t work with fts-solr. This should fix:
http://hg.dovecot.org
=20131203151436.962c06b...@monitoring01.domain.de: stored mail
into mailbox 'Trash'
Dec 03 16:15:06 lmtp(30601): Info: Disconnect from 10.0.0.3: Successful quit
== dovecot.log ==
Dec 03 16:15:06 indexer-worker(usern...@domain.de): Panic: file
http-client-request.c: line 521 (http_client_request_send_more
Hi,
Dovecot 2.1.12 sends panic message when it tries to authenticate some users.
Apparently because they use different authentication mechanisms on different
email clients at the same time. For example, in debug logs this user uses
CRAM-MD5, NTLM and PLAIN in account settings of his email
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
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
On 30 wrz 2013, at 07:54, Timo Sirainen t...@iki.fi wrote:
On 28.9.2013, at 18.11, Kamil Andrusz w...@mniam.net 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
On 28.9.2013, at 18.11, Kamil Andrusz w...@mniam.net 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
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
is causing this?
..
Jul 4 15:04:03 mail dovecot: POP3(user)x.x.x.x: Connection
closed top=0/0, retr=0/0, del=0/4582, size=246709805
Jul 4 15:04:03 mail dovecot: POP3(user)x.x.x.x: Panic: file
pop3-client.c: line 585 (client_default_destroy): assertion failed:
(client-cmd == NULL)
The only reason
, size=246709805
Jul 4 15:04:03 mail dovecot: POP3(user)x.x.x.x: Panic: file
pop3-client.c: line 585 (client_default_destroy): assertion failed:
(client-cmd == NULL)
The only reason I can see for this is:
http://hg.dovecot.org/dovecot-2.2/rev/debbcfe5577a
: POP3(user)x.x.x.x: Panic: file
pop3-client.c: line 585 (client_default_destroy): assertion failed:
(client-cmd == NULL)
Jul 4 15:04:03 mail dovecot: POP3(user)x.x.x.x: Error: Raw
backtrace: /usr/lib/dovecot/libdovecot.so.0() [0x31b4c6074a] -
/usr/lib/dovecot/libdovecot.so.0() [0x31b4c60796
: lmtp(2899, rigak...@otenet.gr): Panic:
pool_data_stack_realloc(): stack frame changed
Jul 4 12:29:47 pop01 dovecot: lmtp(2899, rigak...@otenet.gr): Error:
Raw backtrace: /opt/dovecot-2.2.4/lib/dovecot/libdovecot.so.0
[0x2b0066488bb0] - /opt/dovecot-2.2.4/lib/dovecot/libdovecot.so.
0 [0x2b0066488c06
Never mind I just saw there's a newer version of pigeonhole that fixes
it. Sigh...
Changelog v0.4.1:
- Fixed assertion failure due to datastack problem in message header
composition.
Dalevizo
Hi Timo
With the current dovecot hg we're getting dsync replication errors
Panic: Unknown key: send_mail_requests followed by a crash. This
seems to have been introduced somewhere around
http://hg.dovecot.org/dovecot-2.2/rev/4883a8e1db13
Log output from latest hg, 2.2.2 (e7c474011934+):
May 29
On 29.5.2013, at 10.54, Oli Schacher dove...@lists.wgwh.ch wrote:
With the current dovecot hg we're getting dsync replication errors
Panic: Unknown key: send_mail_requests followed by a crash. This
seems to have been introduced somewhere around
http://hg.dovecot.org/dovecot-2.2/rev
---
root@lapetus:/mnt/emails/indiefield.co.uk/jsmith/Mails/Virtual# doveadm -v
index -u 'john smith' 'Search/Archives'
doveadm(john smith): Info: Search/Archives: Caching mails seq=109580..127362
1800/17783doveadm(john smith): Panic: file solr
Am 29.04.2013 11:08, schrieb Andre Rodier:
Sorry,
I checked my dovecot version, and it has not been updated by Debian yet.
I will check if I can find a method to update without breaking dependancies.
André
perhaps look at
Thanks Robert,
I was not aware of this distribution.
ATB,
André
On 29/04/13 10:21, Robert Schetterer wrote:
Am 29.04.2013 11:08, schrieb Andre Rodier:
Sorry,
I checked my dovecot version, and it has not been updated by Debian yet.
I will check if I can find a method to update without
=109580..127362
1800/17783doveadm(john smith): Panic: file solr-connection.c: line 416
(solr_connection_select): assertion failed: (!conn-posting)
doveadm(john smith): Error: Raw backtrace:
/usr/lib/dovecot/libdovecot.so.0(+0x4414a) [0x7fcb7b5b014a] -
/usr/lib/dovecot/libdovecot.so.0
Hi Timo,
just another crash - using 2.2.1 (c95cea6e1389).
Regards,
Pascal
Reading symbols from /usr/local/libexec/dovecot/imap...done.
[New LWP 15198]
warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library
On 23.4.2013, at 14.47, Pascal Volk user+dove...@localhost.localdomain.org
wrote:
just another crash - using 2.2.1 (c95cea6e1389).
Fixed: http://hg.dovecot.org/dovecot-2.2/rev/2784b88a4260
(This started happening only after yesterday's zlib change.)
On Tue, 2013-04-16 at 19:28 +0200, Pascal Volk wrote:
On 04/15/2013 11:33 PM Pascal Volk wrote:
OK, applied that patch. Lets see what will happen.
Looks good. No crash in the last 20 hours.
OK. Committed the patch a little bit differently:
On 04/15/2013 11:33 PM Pascal Volk wrote:
OK, applied that patch. Lets see what will happen.
Looks good. No crash in the last 20 hours.
Regards,
Pascal
--
The trapper recommends today: cafefeed.1310...@localdomain.org
Hi Timo,
some imap processes seems to have some problems.
Regards,
Pascal
Core was generated by `dovecot/imap'.
Program terminated with signal 6, Aborted.
#0 0x7fbf87b25475 in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt full
#0 0x7fbf87b25475 in raise () from
On Mon, 2013-04-15 at 16:37 +0200, Pascal Volk wrote:
some imap processes seems to have some problems.
Can you reproduce it? What client was that with? I wonder if it was
using CATENATE extension.
On 04/15/2013 04:51 PM, Timo Sirainen wrote:
Can you reproduce it? What client was that with? I wonder if it was
using CATENATE extension.
Three users where able to crash their imap service. All three users are
using Thunderbird 17.0.5@Windows.
I'm not sure what they've done exactly. Nobody
On Mon, 2013-04-15 at 16:37 +0200, Pascal Volk wrote:
some imap processes seems to have some problems.
I still can't reproduce .. but I wonder if the attached patch makes a
difference.
Also in the gdb these would be useful to know:
p *attach.input.real_stream.parent.real_stream
p
On Mon, 2013-04-15 at 19:50 +0300, Timo Sirainen wrote:
On Mon, 2013-04-15 at 16:37 +0200, Pascal Volk wrote:
some imap processes seems to have some problems.
I still can't reproduce .. but I wonder if the attached patch makes a
difference.
Uh, wrong directory. This patch. :)
diff -r
On Mon, 2013-04-15 at 19:53 +0300, Timo Sirainen wrote:
On Mon, 2013-04-15 at 19:50 +0300, Timo Sirainen wrote:
On Mon, 2013-04-15 at 16:37 +0200, Pascal Volk wrote:
some imap processes seems to have some problems.
I still can't reproduce .. but I wonder if the attached patch makes a
On 04/15/2013 06:55 PM Timo Sirainen wrote:
On Mon, 2013-04-15 at 19:53 +0300, Timo Sirainen wrote:
Uh, wrong directory. This patch. :)
Once more, with some error checks :)
OK, applied that patch. Lets see what will happen.
Regards,
Pascal
--
The trapper recommends today:
Le 9 avr. 2013 à 22:56, Timo Sirainen t...@iki.fi a écrit :
On 8.4.2013, at 23.26, to...@starbridge.org wrote:
imap(clean-quarant...@spamguard.fr): Panic: file istream.c: line 153
(i_stream_read): assertion failed: (_stream-skip != _stream-pos)
http://hg.dovecot.org/dovecot-2.2/rev
On 8.4.2013, at 23.26, to...@starbridge.org wrote:
imap(clean-quarant...@spamguard.fr): Panic: file istream.c: line 153
(i_stream_read): assertion failed: (_stream-skip != _stream-pos)
http://hg.dovecot.org/dovecot-2.2/rev/fbef40826602 should fix this.
with thunderbird so far)
Thanks for your help
Apr 7 21:30:58 mx2 dovecot: imap(clean-quarant...@spamguard.fr): Panic:
Buffer full (8206 8192, pool none)
Thanks, this should fix it:
http://hg.dovecot.org/dovecot-2.2/rev/bb25fa35d887
Hi Timo,
It's ok for this error, but now, on a few email, I've
on a large mailbox (around 50k
messages)
imap(clean-quarant...@spamguard.fr): Panic: Buffer full (4254 4248,
pool none)
These should fix it: http://hg.dovecot.org/dovecot-2.2/rev/689dbeadf168
http://hg.dovecot.org/dovecot-2.2/rev/ee7352f46d1e
Thx Timo
It's ok now
Regards
Tonio
Hi
Apr 7 21:30:58 mx2 dovecot: imap(clean-quarant...@spamguard.fr): Panic:
Buffer full (8206 8192, pool none)
Thanks, this should fix it:
http://hg.dovecot.org/dovecot-2.2/rev/bb25fa35d887
messages)
imap(clean-quarant...@spamguard.fr): Panic: Buffer full (4254 4248,
pool none)
These should fix it: http://hg.dovecot.org/dovecot-2.2/rev/689dbeadf168
http://hg.dovecot.org/dovecot-2.2/rev/ee7352f46d1e
Thx Timo
It's ok now
Regards
Tonio
On Sat, 2013-03-16 at 13:51 +0100, to...@starbridge.org wrote:
Hi Timo,
I've got a crash with dovecot 2.2
dovecot --version
2.2.rc2 (69c26a9e3be5)
It's occured when accessing with imap on a large mailbox (around 50k
messages)
imap(clean-quarant...@spamguard.fr): Panic: Buffer full
Hi Timo,
I've got a crash with dovecot 2.2
dovecot --version
2.2.rc2 (69c26a9e3be5)
It's occured when accessing with imap on a large mailbox (around 50k
messages)
imap(clean-quarant...@spamguard.fr): Panic: Buffer full (4254 4248,
pool none)
Error: Raw backtrace: /usr/lib/dovecot
On 16.3.2013, at 13.51, to...@starbridge.org wrote:
It's occured when accessing with imap on a large mailbox (around 50k
messages)
imap(clean-quarant...@spamguard.fr): Panic: Buffer full (4254 4248,
pool none)
..
#7 0x7f9d1bcd4ba8 in quoted_printable_decode_full
this message in context:
http://dovecot.2317879.n4.nabble.com/Panic-when-indexing-virtual-folder-with-solr-tp40764p40779.html
Sent from the Dovecot mailing list archive at Nabble.com.
--
André Rodier
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
' 'Search/*' =
Panic: file solr-connection.c: line 416 (solr_connection_select): assertion
failed: (!conn-posting)
Now, if I rune the doveadm index on the real folders first, the next time I do
the index on the virtual folder, everything is fine:
doveadm -v index -u 'andre rodier' '*'
doveadm
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
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
the errors correctly.
It should return an error message.
Kind regards,
André Rodier
On 4 March 2013 10:01, André Rodier andre.rod...@gmail.com wrote:
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
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 character is '^]'.
* OK
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
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
This bug was fixed !
http://hg.dovecot.org/dovecot-2.1/rev/fa9387588430
Thanks Timo.
Quote: Hiromi Kimura hir...@tac.tsukuba.ac.jp：
Quote: Timo Sirainen t...@iki.fi：
On Mon, 2012-12-31 at 04:23 +0100, Marc Schiffbauer wrote:
IMO relevant logs line parts:
java.io.CharConversionException:
Quote: Timo Sirainen t...@iki.fi：
On Mon, 2012-12-31 at 04:23 +0100, Marc Schiffbauer wrote:
IMO relevant logs line parts:
java.io.CharConversionException: Invalid UTF-8 start byte 0xf8 (at
char #483989, byte #532382)
Fixed: http://hg.dovecot.org/dovecot-2.1/rev/7be4709aab5e
I have
always get a panic.
..
SEVERE: java.lang.RuntimeException: [was class
java.io.CharConversionException] Invalid UTF-8 start byte 0xf8 (at char
#483989, byte #532382)
Looks like the same issue I was trying to debug with the other guy also, but
I couldn't figure out how that happens. Dovecot
On Mon, 2012-12-31 at 04:23 +0100, Marc Schiffbauer wrote:
IMO relevant logs line parts:
java.io.CharConversionException: Invalid UTF-8 start byte 0xf8 (at char
#483989, byte #532382)
Fixed: http://hg.dovecot.org/dovecot-2.1/rev/7be4709aab5e
Am Freitag, 4. Januar 2013, 23:26:13 schrieb Timo Sirainen:
On Mon, 2012-12-31 at 04:23 +0100, Marc Schiffbauer wrote:
IMO relevant logs line parts:
java.io.CharConversionException: Invalid UTF-8 start byte 0xf8 (at char
#483989, byte #532382)
Fixed:
Am 02.01.2013 um 17:57 schrieb Marc Schiffbauer m...@sys4.de:
status 500. Internal server error? Do you have entries in Apache error.log?
My /var/log/tomcat-7/* does not contain any other message.
sorry, my fault. Dovecot connects directly to Tomcat, yes.
I have tried to reproduce this
On 31.12.2012, at 5.23, Marc Schiffbauer m...@sys4.de wrote:
I am having a problem indexing one of my mailboxes using the solr fts backend
in dovecot 2.1.12
For many mailboxes it works just fine, but on one mailbox I currently always
get a panic.
..
SEVERE: java.lang.RuntimeException
solr setup:
Java: icedtea 6.1.11.5
Solr: 3.6.2 running in tomcat 7.0.32
I am running solr on Tomcat 6.
complete dovecot log:
doveadm(my@user): Error: fts_solr: Invalid XML input at 85:198: mismatched
tag (near: htmlheadtitleApache Tomcat/7.0.32-gentoo - Error
report/titlestyle!--H1
Am Mittwoch, 2. Januar 2013, 15:16:45 schrieb Christian Rößner:
solr setup:
Java: icedtea 6.1.11.5
Solr: 3.6.2 running in tomcat 7.0.32
I am running solr on Tomcat 6.
complete dovecot log:
doveadm(my@user): Error: fts_solr: Invalid XML input at 85:198: mismatched
tag (near:
Hi all,
I am having a problem indexing one of my mailboxes using the solr fts backend
in dovecot 2.1.12
For many mailboxes it works just fine, but on one mailbox I currently always
get a panic.
solr setup:
Java: icedtea 6.1.11.5
Solr: 3.6.2 running in tomcat 7.0.32
Command to reproduce error
Hello!
I use dovecot 2.1.12 locally on a 32bit Linux with an ext4 filesystem and after
deleting a lot of emails from a mbox folder, I now get the following messages
in the log:
dovecot: imap(amied): Panic: file mbox-sync.c: line 1351
(mbox_sync_handle_eof_updates): assertion failed: (offset
On Tue, 2012-12-04 at 13:26 -0500, Dave Abrahams wrote:
I just found this in my logs. Any idea?
--8---cut here---start-8---
12/4/12 12:33:43.831 PM dovecot[2660]: indexer-worker(dave): Panic: file
mailbox-list-fs.c: line 156 (fs_list_get_path): assertion
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. :)
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 the
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
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
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]
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 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:
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 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 UTF-8
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:
): Panic:
file solr-connection.c: line 547 (solr_connection_post_more): assertion
failed: (maxfd = 0)
Nov 26 20:49:29 bubba dovecot: indexer-worker(dmil...@amfes.com): Error:
Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x45cea)
[0x7f0c66c33cea] - /usr/local/lib/dovecot/libdovecot.so.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
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
0xfc (at char
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 already
input at line 1: mismatched tag
doveadm(xyz): Panic: file solr-connection.c: line 545
(solr_connection_post_more): assertion failed: (maxfd = 0)
doveadm(xyz): Error: Raw backtrace:
/usr/lib/dovecot/libdovecot.so.0(+0x3c14a) [0x7f7ce2c1714a] -
/usr/lib/dovecot/libdovecot.so.0(default_fatal_handler
Robert Schetterer skrev den 2012-09-22 07:46:
you should upgrade to recent stable version 2.1.x
and this is a simple change from 1.x to 2.x :(
i have never a panic in 1.x here
/Upgrading/1.2
http://wiki2.dovecot.org/Upgrading/2.0
i have never a panic in 1.x here
yeah, but i guess active bug supported are only recent
versions, however wait till Timos answers
--
Best Regards
MfG Robert Schetterer
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
Am 21.09.2012 23:54, schrieb Michael Durket:
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
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: /usr/lib/dovecot/libdovecot.so.0(+0x448fa)
[0x7f70036db8fa] - /usr/lib/dovecot/libdovecot.so.0(+0x44946
,
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: /usr/lib/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: /usr
El 09/07/12 14:37, Robert Schetterer escribió:
guess this is latest for 12.04
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/
I have check this 3.4 kernel and it seems there is no problem with it
--
Angel L. Mateo Martínez
Sección de Telemática
Área de Tecnologías de la
Am 13.07.2012 11:37, schrieb Angel L. Mateo:
El 09/07/12 14:37, Robert Schetterer escribió:
guess this is latest for 12.04
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/
I have check this 3.4 kernel and it seems there is no problem with it
cool, thx for info
--
Best
Hello,
More problems (it seems that we won't be able to put our new servers in
production). The problem now is that when we reach 1000 dovecot
processes we have errors like:
Jul 9 12:10:22 myotis31 dovecot: imap-login: Panic: epoll_ctl(add, 6)
failed: Invalid argument
Jul 9 12:10:22
: Panic: epoll_ctl(add, 6)
failed: Invalid argument
Jul 9 12:10:22 myotis31 dovecot: imap-login: Fatal: master:
service(imap-login): child 32251 killed with signal 6 (core dumps disabled)
and server doesn't accept any new connection.
Our servers are running in ubuntu 12.04
:10:22 myotis31 dovecot: imap-login: Panic: epoll_ctl(add, 6)
failed: Invalid argument
Jul 9 12:10:22 myotis31 dovecot: imap-login: Fatal: master:
service(imap-login): child 32251 killed with signal 6 (core dumps disabled)
and server doesn't accept any new connection.
Our servers
12:10:22 myotis31 dovecot: imap-login: Panic: epoll_ctl(add, 6)
failed: Invalid argument
Jul 9 12:10:22 myotis31 dovecot: imap-login: Fatal: master:
service(imap-login): child 32251 killed with signal 6 (core dumps disabled)
and server doesn't accept any new connection.
Our
hallo,
dovecot log entries:
Jun 23 23:19:10 mx dovecot: dict: Panic: file driver-pgsql.c: line 84
(driver_pgsql_set_state): assertion failed: (state == SQL_DB_STATE_BUSY
|| db-
cur_result == NULL)
This is clearly a bug, but I don't really see why it's happening. It would
On 24.6.2012, at 13.21, ckubu wrote:
dovecot log entries:
Jun 23 23:19:10 mx dovecot: dict: Panic: file driver-pgsql.c: line 84
(driver_pgsql_set_state): assertion failed: (state == SQL_DB_STATE_BUSY || db-
cur_result == NULL)
This is clearly a bug, but I don't really see why it's happening
.
dovecot log entries:
Jun 23 23:19:10 mx dovecot: dict: Panic: file driver-pgsql.c: line 84
(driver_pgsql_set_state): assertion failed: (state == SQL_DB_STATE_BUSY ||
db-
cur_result == NULL)
Jun 23 23:19:10 mx dovecot: dict: Error: Raw backtrace:
/usr/local/dovecot-2.1.7/lib/dovecot
.
dovecot log entries:
Jun 23 23:19:10 mx dovecot: dict: Panic: file driver-pgsql.c: line 84
(driver_pgsql_set_state): assertion failed: (state == SQL_DB_STATE_BUSY || db-
cur_result == NULL)
Jun 23 23:19:10 mx dovecot: dict: Error: Raw backtrace:
/usr/local/dovecot-2.1.7/lib/dovecot/libdovecot.so.0
using latest auto build didn't help.
this happens only with a specific account.
# doveadm -o imapc_user=-@domain.com -o imapc_password= backup
-u =-@domain.com -R imapc:
dsync(@domain.com): Panic: pool_data_stack_realloc(): stack frame
changed
dsync(@domain.com): Error: Raw
On 06/15/2012 02:43 PM, Gedalya wrote:
using latest auto build didn't help.
this happens only with a specific account.
# doveadm -o imapc_user=-@domain.com -o imapc_password= backup
-u =-@domain.com -R imapc:
dsync(@domain.com): Panic: pool_data_stack_realloc(): stack frame
On 15.6.2012, at 21.50, Gedalya wrote:
#12 imapc_untagged_fetch (reply=0xb184, mbox=0x80fd2c8) at
imapc-mailbox.c:349
old_kws = {arr = {buffer = 0x8093030, element_size = 4}, v = 0x8093030,
v_modifiable = 0x8093030}
Fixed: http://hg.dovecot.org/dovecot-2.1/rev/a28c8043842d
On 06/15/2012 07:04 PM, Timo Sirainen wrote:
On 15.6.2012, at 21.50, Gedalya wrote:
#12 imapc_untagged_fetch (reply=0xb184, mbox=0x80fd2c8) at
imapc-mailbox.c:349
old_kws = {arr = {buffer = 0x8093030, element_size = 4}, v = 0x8093030,
v_modifiable = 0x8093030}
Fixed:
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
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: line
On Fri, 2012-04-27 at 16:34 +1000, Nick Urbanik wrote:
I upgraded to 2.1.5, and we have the same assertion failure, on the
same mailbox:
Apr 27 16:02:03 imap(nu-imaptest00...@example.com): Panic: file
mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed
Dear Folks,
We had this assertion failure on Dovecot 2.1.1 on a particular
mailbox.
I upgraded to 2.1.5, and we have the same assertion failure, on the
same mailbox:
Apr 27 16:02:03 imap(nu-imaptest00...@example.com): Panic: file
mailbox-list-fs.c: line 156 (fs_list_get_path): assertion
601 - 700 of 983 matches
Mail list logo
