Displaying 20 results from an estimated 400 matches similar to: "indexer-worker Panic"
2012 Apr 27
1
2.1.5: Panic: file mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name))
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-imaptest00258 at example.com): Panic: file mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name))
Apr 27 16:02:03 imap(nu-imaptest00258 at
2012 Jan 25
4
Crash on mail folder delete
Attempting to delete a folder from within the trash folder using
Thunderbird. I see the following in the log:
Jan 25 15:36:22 bubba dovecot: imap(dmiller at amfes.com): Panic: file
mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed:
(mailbox_list_is_valid_pattern(_list, name))
Jan 25 15:36:22 bubba dovecot: imap(dmiller at amfes.com): Error: Raw
backtrace:
2010 Feb 28
2
Dovecot 2.0.beta3: mdbox mailbox crashes upon login
Hi,
converted my personal mailbox from 'maildir' to 'mdbox' for testing today:
# dsync convert -u user at domain mdbox:~/mdbox
Set mail location to mdbox in 'mail.conf' and restarted server:
mail_location = mdbox:~/mdbox
Dovecot panicked instantly upon login with different clients. Tried to disable several plugins to no avail:
Feb 28 14:43:02 spectre dovecot:
2010 Jul 11
3
Crash while accessing mdbox folders
Hi,
I've converted some accounts with "dsync mirror maildir:~/Maildir". It
seemed to work, but when I access the folders via IMAP I get the
following error:
Jul 11 09:41:59 shrike dovecot: imap(matze): Debug: acl vfile: file
/home/matze/mdbox/mailboxes/Telefon/dbox-Mails/dovecot-acl not found
Jul 11 09:41:59 shrike dovecot: imap(matze): Panic: file
mailbox-list-fs.c: line 150
2010 Sep 21
1
Panic: file mailbox-list-fs.c
Hi,
I have dovecot 2.0.3.
Mailboxes have been converted with dsync from mbox to maildir last week.
There it was still version 2.0.2.
A user "produces" now this error:
imap(userx): Panic: file mailbox-list-fs.c: line 150
(fs_list_get_path): assertion failed:
(mailbox_list_is_valid_pattern(_list, name))
Error: Raw backtrace: follows.
And all other imap processes are closing down.
2012 May 26
1
Crash on force-resync if / is given as mailbox name
Hi,
when I specify a slash a mailbox name on the command line
of doveadm force-resync, it throws a panic. I'm not sure
this is considered a bug.
mail01:~# doveadm force-resync -u user1 at example.org /
doveadm(user1 at example.org): Panic: file mailbox-list-fs.c: line 150 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name))
doveadm(user1 at example.org): Error:
2010 Sep 15
1
dsync crash
Hello,
When I run
dsync -u v.shokov -Dv mirror sdbox:/dsync/v.shokov
first time, process halting.
On second time I receive this error:
dsync(root): Debug: auth input: v.shokov system_groups_user=v.shokov uid=10000 gid=100 home=/home/v.shokov
dsync(root): Debug: Effective uid=10000, gid=100, home=/home/v.shokov
dsync(root): Debug: Namespace : type=private, prefix=, sep=.,
2019 Aug 03
1
segmentation fault in fs_list_get_path
Hi,
There seems to be a straightforward bug in
src/lib-storage/list/mailbox-list-fs.c:79. set->index_dir is unchecked
prior to dereferencing (unlike on line 126 in the same file, where it is
properly checked). This manifested on a FreeBSD server running dovecot
2.3.6 when clients tried to retrieve mail with subscriptions like
`~/bar/baz`. This caused the `imap` child to crash, e.g.
2013 Feb 11
2
error running indexer-worker as non-root user
Using dovecot-2.1.15 if I run indexer-worker as a non-root user it fails with an error:
Feb 11 13:06:47 indexer-worker: Error: user foobar: Error reading configuration: net_connect_unix(/var/run/dovecot/config) failed: Permission denied
This is what I added to 10-master.conf:
service indexer-worker {
user = _dovecot
}
The wiki says it should work:
<http://wiki2.dovecot.org/Services>
2017 Feb 27
0
indexer-worker assert in v2.2.28 (fts-lucene)
I upgraded to 2.2.28 and started seeing this logged:
indexer-worker(dluke): Panic: file mailbox-list.c: line 1158 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0)
indexer-worker(dluke): Error: Raw backtrace:
2 libdovecot.0.dylib 0x000000010ec63d24 default_fatal_finish + 36
-> 3 libdovecot.0.dylib
2018 Dec 20
0
Fatal: master: service(indexer-worker): child 493 killed with signal 11 (core dumped)
I've managed to re-compile the alpine packages inside the container,
creating the debug symbols and disabling compile time optimizations, as
they also disturbed the backtrace. The following output looks much more
meaningful. But unfortunately there are still some symbols missing for
lucene-core. Let me know if this is enough to work with. (It doesn't
seem to be musl after all?)
Reading
2011 Jan 16
1
Panic: file mailbox-list-maildir.c: line 133: unreached
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(holger at mauermann.org): Panic: file mailbox-list-maildir.c: line 133: unreached
imap(holger at mauermann.org):
2019 Dec 15
1
Bug: indexer-worker segfaults with fts_xapian 1.2.5
Core was generated by `dovecot/indexer-worker'.
Program terminated with signal 11, Segmentation fault.
#0 0x00007f30f7ad056d in __exchange_and_add (__val=-1, __mem=0xfffffffffffffff8)
at /usr/src/debug/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/ext/atomicity.h:49
49 { return __atomic_fetch_add(__mem, __val, __ATOMIC_ACQ_REL); }
(gdb) bt full
#0
2018 Dec 21
0
Fatal: master: service(indexer-worker): child 493 killed with signal 11 (core dumped)
Hi, I now this is kinda impolite to ask, but I would like some feedback
on this issue. I'm representing the Mailu user group here, plus the fact
that my own production server is affected and starts to crash due to
file corruption as a result of the indexer-worker segfaults. Last night
my server became unavailable with logs like:
Error: imap(tim at
2018 Dec 22
0
Fatal: master: service(indexer-worker): child 493 killed with signal 11 (core dumped)
Ok, thanks a lot for the reply. I'll keep digging then :)
On 12/21/18 4:19 PM, Aki Tuomi wrote:
> On 21.12.2018 15.01, Tim Mohlmann via dovecot wrote:
>> Hi, I now this is kinda impolite to ask, but I would like some feedback
>> on this issue. I'm representing the Mailu user group here, plus the fact
>> that my own production server is affected and starts to crash due
2014 Jan 05
1
Panic: file mailbox-list-maildir.c: line 133: unreached
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: unreached
Jan 5 18:04:25 mail dovecot: imap(user): Error: Raw backtrace:
2014 Jul 24
1
FTS lucene indexer-worker segfaulting
Hi,
I've just set up fts-lucene and when I run searches on my inbox or when
I run the indexer (`doveadm index INBOX`) I get the following segfault.
I've run it multiple times and noticed that the data value is different
each time so I guess it doesn't always crash at the same point.
I'm running dovecot 2.2.13-1 with clucene 2.3.3.4-8 on Arch Linux.
If you need any more
2018 Dec 21
2
Fatal: master: service(indexer-worker): child 493 killed with signal 11 (core dumped)
On 21.12.2018 15.01, Tim Mohlmann via dovecot wrote:
> Hi, I now this is kinda impolite to ask, but I would like some feedback
> on this issue. I'm representing the Mailu user group here, plus the fact
> that my own production server is affected and starts to crash due to
> file corruption as a result of the indexer-worker segfaults. Last night
> my server became unavailable
2018 Dec 20
2
Fatal: master: service(indexer-worker): child 493 killed with signal 11 (core dumped)
I'm really sorry, but it was a long day yesterday. I forgot to mention
that I used alpine:edge (based on the alpine master branch) image to set
up the build environment. So there were some version changes.
dovecot --version: 2.3.3 (dcead646b)
apk info musl:
musl-1.1.20-r2 description:
the musl c library (libc) implementation
Configuration was unchanged wrt to my first mail. Maybe it's
2015 May 10
0
v2.2.17 release candidate released
On 10/05/2015 5:47 PM, Timo Sirainen wrote:
>> How do I go about debugging this further? How do I go about
>> getting a backtrace on what is essentially a child process that
>> doesn't produce a core? (Note that my installation normally does
>> produce cores when it crashes, so there's something different about
>> these indexer processes..)
>
> One