Mailing List Archive: DBMail: users

dbmail3: insert envelope failed

Index | Next | Previous | View Threaded

h.reindl at thelounge

Feb 4, 2012, 6:11 AM

Post #1 of 4 (260 views)
Permalink

dbmail3: insert envelope failed

randomly error while receive a logwatch-message from crond

the duplicate entry sql-errors leads me to a little bit headache
i saw millions of them while dbmail-util-transition to 3.0 too

what triggers the "hash algorithm not supported"
is there any library missing at compile-time?

Feb 4 14:09:04 rh dbmail/lmtpd[5789]: [0x22e4280] Warning:[misc] dm_get_hash_for_string(+2267): hash algorithm not
supported. Using SHA1.
Feb 4 14:09:04 rh dbmail/lmtpd[5789]: [0x22e4280] Error:[message] dbmail_message_cache_envelope(+1701):
SQLException: Duplicate entry '3847' for key 'physmessage_id_2'
Feb 4 14:09:04 rh dbmail/lmtpd[5789]: [0x22e4280] Error:[message] dbmail_message_cache_envelope(+1703): insert
envelope failed [("Sat, 04 Feb 2012 14:09:03 +0100" "Logwatch for rh.thelounge.net (Linux)" ((NIL NIL "logwatch"

--

Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / software-development / cms-solutions
p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
icq: 154546673, http://www.thelounge.net/

http://www.thelounge.net/signature.asc.what.htm

Attachments:

signature.asc (0.26 KB)

paul at nfg

Feb 4, 2012, 6:24 AM

Post #2 of 4 (242 views)
Permalink

Re: dbmail3: insert envelope failed [In reply to]

On 02/04/2012 03:11 PM, Reindl Harald wrote:
> randomly error while receive a logwatch-message from crond
>
> the duplicate entry sql-errors leads me to a little bit headache
> i saw millions of them while dbmail-util-transition to 3.0 too

Not good.

> what triggers the "hash algorithm not supported"
> is there any library missing at compile-time?

You didn't specify a hash algorithm in dbmail.conf. That's all.

> Feb 4 14:09:04 rh dbmail/lmtpd[5789]: [0x22e4280] Error:[message] dbmail_message_cache_envelope(+1701):
> SQLException: Duplicate entry '3847' for key 'physmessage_id_2'
> Feb 4 14:09:04 rh dbmail/lmtpd[5789]: [0x22e4280] Error:[message] dbmail_message_cache_envelope(+1703): insert
> envelope failed [("Sat, 04 Feb 2012 14:09:03 +0100" "Logwatch for rh.thelounge.net (Linux)" ((NIL NIL "logwatch"

key physmessage_id_2 is defined as:

CREATE TABLE `dbmail_envelope` (
`id` bigint(20) NOT NULL auto_increment,
`physmessage_id` bigint(20) NOT NULL default '0',
`envelope` text NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `physmessage_id_1` (`physmessage_id`),
UNIQUE KEY `physmessage_id_2` (`physmessage_id`,`id`),
CONSTRAINT `dbmail_envelope_ibfk_1` FOREIGN KEY (`physmessage_id`)
REFERENCES `dbmail_physmessage` (`id`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

So if that fails there's something really wrong. I'd need to see the
actual query, or the debug logs just before the exception.

Perhaps the physmessage_id is incorrect somehow.

--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin

* Premium Hosting Services and Web Application Consultancy *

www.nfg.nl/info [at] nfg/+31.85.877.99.97
________________________________________________________________
_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

h.reindl at thelounge

Feb 4, 2012, 6:30 AM

Post #3 of 4 (244 views)
Permalink

Re: dbmail3: insert envelope failed [In reply to]

Am 04.02.2012 15:24, schrieb Paul J Stevens:
> On 02/04/2012 03:11 PM, Reindl Harald wrote:
>> randomly error while receive a logwatch-message from crond
>>
>> the duplicate entry sql-errors leads me to a little bit headache
>> i saw millions of them while dbmail-util-transition to 3.0 too
>
> Not good.
>
>> what triggers the "hash algorithm not supported"
>> is there any library missing at compile-time?
>
> You didn't specify a hash algorithm in dbmail.conf. That's all.
>
>> Feb 4 14:09:04 rh dbmail/lmtpd[5789]: [0x22e4280] Error:[message] dbmail_message_cache_envelope(+1701):
>> SQLException: Duplicate entry '3847' for key 'physmessage_id_2'
>> Feb 4 14:09:04 rh dbmail/lmtpd[5789]: [0x22e4280] Error:[message] dbmail_message_cache_envelope(+1703): insert
>> envelope failed [("Sat, 04 Feb 2012 14:09:03 +0100" "Logwatch for rh.thelounge.net (Linux)" ((NIL NIL "logwatch"
>
> key physmessage_id_2 is defined as:
>
> CREATE TABLE `dbmail_envelope` (
> `id` bigint(20) NOT NULL auto_increment,
> `physmessage_id` bigint(20) NOT NULL default '0',
> `envelope` text NOT NULL,
> PRIMARY KEY (`id`),
> UNIQUE KEY `physmessage_id_1` (`physmessage_id`),
> UNIQUE KEY `physmessage_id_2` (`physmessage_id`,`id`),
> CONSTRAINT `dbmail_envelope_ibfk_1` FOREIGN KEY (`physmessage_id`)
> REFERENCES `dbmail_physmessage` (`id`) ON DELETE CASCADE ON UPDATE CASCADE
> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
>
> So if that fails there's something really wrong. I'd need to see the
> actual query, or the debug logs just before the exception.
>
> Perhaps the physmessage_id is incorrect somehow.

since i can not reproduce this everytime with messages would it help you
if i clone the dbmail-2.2 database start the whole transition
"dbmail-util -by" and "dbmail-util -M -y" again with debug-log
to download offlist?

i guess i have to interrupt this after a while to not
write the disk full :-)

Attachments:

signature.asc (0.26 KB)

paul at nfg

Feb 4, 2012, 8:23 AM

Post #4 of 4 (244 views)
Permalink

Re: dbmail3: insert envelope failed [In reply to]

On 02/04/2012 03:30 PM, Reindl Harald wrote:
>
>
> Am 04.02.2012 15:24, schrieb Paul J Stevens:
>> On 02/04/2012 03:11 PM, Reindl Harald wrote:
>>> randomly error while receive a logwatch-message from crond
>>>
>>> the duplicate entry sql-errors leads me to a little bit headache
>>> i saw millions of them while dbmail-util-transition to 3.0 too
>>
>> Not good.
>>
>>> what triggers the "hash algorithm not supported"
>>> is there any library missing at compile-time?
>>
>> You didn't specify a hash algorithm in dbmail.conf. That's all.
>>
>>> Feb 4 14:09:04 rh dbmail/lmtpd[5789]: [0x22e4280] Error:[message] dbmail_message_cache_envelope(+1701):
>>> SQLException: Duplicate entry '3847' for key 'physmessage_id_2'
>>> Feb 4 14:09:04 rh dbmail/lmtpd[5789]: [0x22e4280] Error:[message] dbmail_message_cache_envelope(+1703): insert
>>> envelope failed [("Sat, 04 Feb 2012 14:09:03 +0100" "Logwatch for rh.thelounge.net (Linux)" ((NIL NIL "logwatch"
>>
>> key physmessage_id_2 is defined as:
>>
>> CREATE TABLE `dbmail_envelope` (
>> `id` bigint(20) NOT NULL auto_increment,
>> `physmessage_id` bigint(20) NOT NULL default '0',
>> `envelope` text NOT NULL,
>> PRIMARY KEY (`id`),
>> UNIQUE KEY `physmessage_id_1` (`physmessage_id`),
>> UNIQUE KEY `physmessage_id_2` (`physmessage_id`,`id`),
>> CONSTRAINT `dbmail_envelope_ibfk_1` FOREIGN KEY (`physmessage_id`)
>> REFERENCES `dbmail_physmessage` (`id`) ON DELETE CASCADE ON UPDATE CASCADE
>> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
>>
>> So if that fails there's something really wrong. I'd need to see the
>> actual query, or the debug logs just before the exception.
>>
>> Perhaps the physmessage_id is incorrect somehow.
>
> since i can not reproduce this everytime with messages would it help you
> if i clone the dbmail-2.2 database start the whole transition
> "dbmail-util -by" and "dbmail-util -M -y" again with debug-log
> to download offlist?
>
> i guess i have to interrupt this after a while to not
> write the disk full :-)

indeed. Spare me and don't run dbmail-util run all the way. Just cut it
short after the first error.

--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin

* Premium Hosting Services and Web Application Consultancy *

www.nfg.nl/info [at] nfg/+31.85.877.99.97
________________________________________________________________
_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads