[Dovecot] Panic when attempting index with Apache Solr : fts_solr plugin

[A Dovecot User]

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)
Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x3aa41)
[0xbd5a41] ->
/usr/local/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x47)
[0xbd5b57] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xbab8de]
->
/usr/local/lib/dovecot/lib21_fts_solr_plugin.so(solr_connection_post_more+0x293)
[0x191d53] -> /usr/local/lib/dovecot/lib21_fts_solr_plugin.so(+0x2723)
[0x18f723] ->
/usr/local/lib/dovecot/lib20_fts_plugin.so(fts_backend_build_more+0x1f)
[0x45d2ff] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0x5515)
[0x460515] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0x5928)
[0x460928] ->
/usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_deinit+0x3a)
[0xf3d03a] ->
/usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x55)
[0xf3d0f5] -> doveadm() [0x805184d] -> doveadm() [0x804ef55] ->
doveadm(doveadm_mail_single_user+0x5b) [0x804f3ab] -> doveadm() [0x804f813]
-> doveadm(doveadm_mail_try_run+0x12e) [0x804fc6e] -> doveadm(main+0x3a4)
[0x8055b64] -> /lib/libc.so.6(__libc_start_main+0xe6) [0x729e36] ->
doveadm() [0x804ed61]


On Thu, 08 Dec 2011 07:22:22 +0200, Timo Sirainen <tss at iki.fi> wrote:
> On Fri, 2011-12-02 at 12:47 -0600, A Dovecot User wrote:
>> [root at 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_connection_post_more): assertion failed: (maxfd >= 0)
> 
> This happens every time? It can't index any mails at all? Have you tried
> with Dovecot v2.0?
> 
> I can't reproduce it. Anyway I guess either I'm using libcurl wrong
> somehow, or there's a bug in libcurl..