Thanks for the explanations, Jacob! I agree that your command would have been better. Now I know! Luckily for me, the list I reindexed
wasn’t a big one.
Cheers,
--
David
UCF emails are public record.
On Feb 9, 2021, at 12:28 PM, David Collantes <[log in to unmask]> wrote:
REINDEX DATABASE WWW BOTH IMMEDiate <listname>
And that did the trick, indeed. Thanks much!
I want to give some more details about the difference between the version of the command I suggested and the version you used, in case anyone is curious.
-
The above version of the command has DATABASE and WWW. However, the BOTH parameter already tells LISTSERV to include both of these two types of indexes, making this redundant.
These are the two types of indexes I was referring to when I said that LISTSERV "should then rebuild both its internal index of the archives, and the web interface files related to the mailing list."
-
IMMEDIATE means that LISTSERV should do the reindexing using its main process, meaning that it can’t do anything else while reindexing the mailing list.
For mailing lists with a large back catalog of messages, this could take some time, so I left off the ‘IMMEDIATE parameter. With my version of the command, the processing would be done in the background, and LISTSERV would be able to do
other things while reindexing the mailing list. For mailing lists with small archives, the reindexing should happen virtually instantly, regardless of whether IMMEDIATE is present or not.
UCF emails are public record.
We recently created a list, and used the wrong path for its notebook. I have moved the notebook to the right location, but the archives are broken now with message:
“The archive files could not be accessed, either because the list does not have Web-accessible archives or because they are being updated. If you know that the list has Web
archives, please try again in about 30 seconds, and report the problem if it persists for more than a few minutes. The file that could not be opened is '/old/list/notebook/path/listname.log2019' and the error code was 2 (No such file or directory).”
How one forces the archives to be rebuilt afresh?
Go under ’Server Administration’ or ’List Management’ to ‘LISTSERV Command’ and issue this command:
replacing ‘listname’ with the name of the mailing list. It should then rebuild both its internal index of the archives, and the web interface files related to the mailing list.
If any errors result, then you can investigate those further — but hopefully this will take care of it.
To unsubscribe from the LSTSRV-L list, click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
To unsubscribe from the LSTSRV-L list, click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
To unsubscribe from the LSTSRV-L list, click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1