Hello,
I've been tasked with migrating an old Mailman 2.0.8 install on an old Solaris 8 server to RHEL running Mailman 2.1.12.
Everything was going quite smoothly and thought I was almost ready to proceed with the migration in production but held messages are missing in migrated lists.
I did find the held messages are in /var/lib/mailman/data and migrated them but the admin GUI shows there are No Pending Requests.
Doing a dumpdb on the migrated request.db file lists all the held messages but they're not in the request.pck file.
The config.db file was converted to config.pck without any issues. Is there something I missed?
Thanks, Peter
On 06/26/2015 05:35 PM, Peter Draksler wrote:
I did find the held messages are in /var/lib/mailman/data and migrated them but the admin GUI shows there are No Pending Requests.
Doing a dumpdb on the migrated request.db file lists all the held messages but they're not in the request.pck file.
I'm not sure how this happened. How exactly did you do the migration. If you did something which ran bin/update, It should migrate the requests. Even now, if you still have the requests.db files in the lists/LISTNAME/ directories, running 'bin/update --force' may do it.
The config.db file was converted to config.pck without any issues. Is there something I missed?
It is a good idea, after migration is complete to remove the old config.db and config.db.last files and probably the requests.db as well.
The reason is that if for some reason at some future time, there is an issue with the config.pck(.last) files, Mailman will fall back the the config.db if it's there, and all of a sudden your list reverts to an old state. It's better to discover the issue when it occurs than to find out days or more later that the list has reverted to an old state.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 15-06-27 11:59 AM, Mark Sapiro wrote:
On 06/26/2015 05:35 PM, Peter Draksler wrote:
I did find the held messages are in /var/lib/mailman/data and migrated them but the admin GUI shows there are No Pending Requests.
Doing a dumpdb on the migrated request.db file lists all the held messages but they're not in the request.pck file.
I'm not sure how this happened. How exactly did you do the migration. If you did something which ran bin/update, It should migrate the requests. Even now, if you still have the requests.db files in the lists/LISTNAME/ directories, running 'bin/update --force' may do it.
Thanks Mark, running 'bin/update --force' updated the held requests database; created request.pck and deleted request.db. I did run 'bin/update' earlier but that only resulted in "No updates are necessary".
To answer your question, I just created a tar of the /archives /lists and /data directories of the lists that are being migrated on the old server and then extracted them on the new.
The config.db file was converted to config.pck without any issues. Is there something I missed?
It is a good idea, after migration is complete to remove the old config.db and config.db.last files and probably the requests.db as well.
The reason is that if for some reason at some future time, there is an issue with the config.pck(.last) files, Mailman will fall back the the config.db if it's there, and all of a sudden your list reverts to an old state. It's better to discover the issue when it occurs than to find out days or more later that the list has reverted to an old state.
Thanks for the advice, I'll be sure to add deleting the config.db* files at the end of the migration script.
Thanks again!
Peter
On 06/27/2015 01:19 PM, Peter Draksler wrote:
Thanks Mark, running 'bin/update --force' updated the held requests database; created request.pck and deleted request.db. I did run 'bin/update' earlier but that only resulted in "No updates are necessary".
To answer your question, I just created a tar of the /archives /lists and /data directories of the lists that are being migrated on the old server and then extracted them on the new.
bin/update won't do anything without the --force option unless data/last_mailman_version has an older version than that of the current install. Mailman knows how to migrate/update config.(db|pck) files from older versions on the fly, but other things are only updated by bin/update.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro
-
Peter Draksler