Error during upgrade/migration

Hello all. I just took over a job where I have to admin a mailman server that died over the weekend. I have all the files, so I thought I'd just roll a new server and upgrade to the latest version. I'm going from version 2.1.4 to 2.1.9.
After installing mailman from yum on Fedora 5, I added DEFAULT_EMAIL_HOST, DEFAULT_URL_HOST to mm_cfg.py, and set the VAR_PREFIX to point to a folder containing my old data, lists, archive, and spam folders.
I ran check_perms -f, which set all the old list data to the correct mailman group. However, I can't seem to see the lists in my mailman setup anywhere. If I run list_lists, I get no results. If I create a new list, it shows up in the same place as my old list data, so I think it's pointing to the right place, but it's just not finding the old lists.
I read about the move_list command, which seems to be deprecated. I tried doing withlist -l -r list-name, as well, but I would always get back the following error:
Importing fix_url... Running fix_url.fix_url()... Loading list list-name (locked) Unknown list: list-name Traceback (most recent call last): File "/usr/lib/mailman/bin/withlist", line 297, in ? main() File "/usr/lib/mailman/bin/withlist", line 275, in main r = do_list(listname, args, func) File "/usr/lib/mailman/bin/withlist", line 201, in do_list return func(m, *args) File "/usr/lib/mailman/bin/fix_url.py", line 81, in fix_url mlist.web_page_url = web_page_url AttributeError: 'NoneType' object has no attribute 'web_page_url'
Been pretty stuck at this point for awhile now. Any guidance would be appreciated.

Camden Daily wrote:
If I create a new list, it shows up in the same place as my old list data, so I think it's pointing to the right place, but it's just not finding the old lists.
Are you saying that you create a new list and it creates a directory at path/to/lists/new_list_name/ containing amomg other files, a config.pck file, and that you have some path/to/lists/old_list_name/ directories with config.pck files, and the new_list_name is listed by bin/list_lists, but the old_list_name is not?
I read about the move_list command, which seems to be deprecated. I tried doing withlist -l -r list-name, as well, but I would always get back the following error:
Presumably you actually ran
withlist -l -r fix_url list-name
Importing fix_url... Running fix_url.fix_url()... Loading list list-name (locked) Unknown list: list-name
withlist doesn't find the list 'list-name'
Traceback (most recent call last): File "/usr/lib/mailman/bin/withlist", line 297, in ? main() File "/usr/lib/mailman/bin/withlist", line 275, in main r = do_list(listname, args, func) File "/usr/lib/mailman/bin/withlist", line 201, in do_list return func(m, *args) File "/usr/lib/mailman/bin/fix_url.py", line 81, in fix_url mlist.web_page_url = web_page_url AttributeError: 'NoneType' object has no attribute 'web_page_url'
The above is really a bug in withlist in that it tries to run the callable script (fix_url in this case) even though it failed to load the list.
All of the above say there is not a lists/list-name/config.pck file in the place mailman is looking for it.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Are you saying that you create a new list and it creates a directory at path/to/lists/new_list_name/ containing amomg other files, a config.pck file, and that you have some path/to/lists/old_list_name/ directories with config.pck files, and the new_list_name is listed by bin/list_lists, but the old_list_name is not?
exactly.
Presumably you actually ran
withlist -l -r fix_url list-name
Yes, I ran it with the fix_url argument. Sorry I left that out of my post.
All of the above say there is not a lists/list-name/config.pck file in the place mailman is looking for it.
They all seem to be there just fine... mailman just doesn't want to read them. Is there something special that I need to do since they're from an old version? Each lists/list-name folder has config.pck, config.pck.last, and request.db in it. Some also have a digest.mbox file.
Thanks for the reply!

Camden Daily wrote:
All of the above say there is not a lists/list-name/config.pck file in the place mailman is looking for it.
They all seem to be there just fine... mailman just doesn't want to read them. Is there something special that I need to do since they're from an old version? Each lists/list-name folder has config.pck, config.pck.last, and request.db in it. Some also have a digest.mbox file.
No, there is nothing special to do for the 'old version'. Mailman will take care of updating the data automatically when it successfully accesses the lists. If the list data files are in the same lists/ directory as new lists that work, perhaps it is an ownership/permissions issue. is the group and permissions of the lists/list-name/ directory and contents the same as those of a list that is found?
BTW, the requests.db changed to requests.pck in 2.1.5. After the lists are actually working and a requests.pck has been created, you can remove the requests.db. There will also be a pending.pck when things are working.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Camden Daily
-
Mark Sapiro