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/[email protected]/+31.85.877.99.97
________________________________________________________________
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
