Developers of Sympa

[Olivier Salaün <address@concealed>]

Hi Adam,

To better understand how the bulk mailer works here is a reminder :

• the bulk mailer spool is stored in the RDBMS
• the bulkspool_table has one entry per message to distribute
• the bulkspool_table has one entry per group of receipients; it refers to a message in the bulkspool_table

The error you are reporting happens whenever a bulkmailer table entry refers to a missing entry in bulkspool table. It means that some list members did not get the message. This should never happen because:

1. messages to be distributed are stored in bulkspool first, entries are then created in bulmailer_table
2. entries in bulkspool_table are locked until the last corresponding bulkmailer entry is consumed, thus preventing the messages from being removed too early from bulkspool_table

A good way to track down what's happening would be that you enable detailed mysql logs, until you are able to reproduce the error. This way, we could track down the sequence of SQL operations and better understand the issue.

Le 05/08/2010 21:21, Adam Bernstein a écrit :

address@concealed">I just installed Sympa 6.1b4, and in testing I find that sending any message to a list results in the following logged error message:

Aug  5 12:10:35 npogroups-new bulk[89674]: err internal error : current packet (messagekey= 7992bbb3f551f2bf8c3691fcf234485c) contain a ref to a null message

The message *does* get distributed fine, but I'm wondering what this error means and if it's already known.  A quick look at the new bulk.pl code makes me think it's just a case of the spool-reading loop terminating one iteration later than it should, but I don't see easily how to fix it.

I'm upgrading all the way from Sympa 5.3.4, so it's all very different, and I don't know if this error is only in 6.1b4 or if it was already there in earlier 6.1 or 6.0 versions....

    adam