Adam Nielsen wrote:
I've followed the FAQ to move some lists across to a new server, but now on the new machine any message posted to a list gets passed to Mailman and then disappears. The Mailman error log says this:
Sep 24 10:34:18 2009 (5311) Uncaught runner exception: regular_exclude_lists Sep 24 10:34:18 2009 (5311) Traceback (most recent call last): File "/usr/lib64/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop File "/usr/lib64/mailman/Mailman/Queue/Runner.py", line 191, in _onefile File "/usr/lib64/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose File "/usr/lib64/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline File "/usr/lib64/mailman/Mailman/Handlers/CalcRecips.py", line 99, in process File "/usr/lib64/mailman/Mailman/Handlers/CalcRecips.py", line 157, in do_exclude File "/usr/lib64/mailman/Mailman/MailList.py", line 146, in __getattr__ AttributeError: regular_exclude_lists
Sep 24 10:34:18 2009 (5311) SHUNTING: 1253752458.0181279+c9484331c59781f0d3cf0af775ece9b9c88a6b43
I can't find any reference to this exception, so I'm a bit stuck where to look next. Any ideas?
It appears that the new server is running 2.1.10 or later with the "sibling lists" feature, and the old server from which the lists were moved did not have this feature, so the lists did not have the corresponding regular_exclude_lists and regular_include_lists attributes.
However, that doesn't explain what is happening, because the first time the moved list is instantiated on the new server, Mailman should detect that the list's data_version is less than the installation's DATA_FILE_VERSION and update the list's attributes. So, the question is why didn't this happen, or if it did, why weren't the regular_exclude_lists and regular_include_lists attributes added?
Did the old installation have patches that increased it's DATA_FILE_VERSION?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan