[DBMail 0001037]: dbmail-imapd segfault. Postgres: prepared statement already exists

Mantis Bug Tracker <[email protected]>
Newsgroups gmane.mail.imap.dbmail.devel
Message-ID <[email protected]>
The following issue has been SUBMITTED. 
====================================================================== 
http://www.dbmail.org/mantis/view.php?id=1037 
====================================================================== 
Reported By:                ALyarskiy
Assigned To:                
====================================================================== 
Project:                    DBMail
Issue ID:                   1037
Category:                   IMAP daemon
Reproducibility:            have not tried
Severity:                   crash
Priority:                   normal
Status:                     new
target:                      
====================================================================== 
Date Submitted:             16-Jan-14 07:17 CET
Last Modified:              16-Jan-14 07:17 CET
====================================================================== 
Summary:                    dbmail-imapd segfault. Postgres: prepared statement
already exists
Description: 
During migration of messages (~120k) (imapsync) dbmail-imapd crashed:

Jan 15 21:12:40 mail2 kernel: dbmail-imapd[1326]: segfault at 25 ip
00007fee2361e48f sp 00007fee18294c20 error 4 in
libglib-2.0.so.0.2600.1[7fee235b1000+103000]

Postgres log:
< 2014-01-15 21:12:40.517 MSK >ERROR:  prepared statement "697757122"
already exists
< 2014-01-15 21:12:40.517 MSK >STATEMENT:  SELECT DISTINCT(keyword) FROM
dbmail_keywords k LEFT JOIN dbmail_messages m ON
k.message_idnr=m.message_idnr LEFT JOIN dbmail_mailboxes b ON
m.mailbox_idnr=b.mailbox_idnr WHERE b.mailbox_idnr=$1
< 2014-01-15 21:12:40.518 MSK >ERROR:  bind message supplies 1 parameters,
but prepared statement "697757122" requires 3
< 2014-01-15 21:12:40.518 MSK >STATEMENT:  INSERT INTO dbmail_header
(physmessage_id, headername_id, headervalue_id) VALUES ($1,$2,$3)
< 2014-01-15 21:12:40.754 MSK >LOG:  could not receive data from client:
Connection reset by peer
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
16-Jan-14 07:17  ALyarskiy      New Issue                                    
======================================================================
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.