Disappearing Groups in Available Group Wikis Page

Question

I found a temporary fix to an ongoing issue and I am looking for a more permanent "fix", if there is such a thing...
The issue is the individual group wiki not appearing in the "Available Group Wikis" when going to https://www.myserver/groups/.
The set up is several xserves within the network, one of which is OD Master, the others are replicas. One of the replicas services the external IP, and this is the one with the no available wikis notation on the Available Group Wikis" page. The group wiki is actually on that server, and can be reached by going to https://www.myserver/groups/mygroup.
In experimenting with this, I found that I can get the mygroup wiki to appear on the Available Group Wikis page IF: I first copy the mygroup folder/directory found in Library/Application Support/Collaboration/Groups to another location (desktop works); then delete the mygroup folder/directory in Collaboration/Groups; then browse to https://www.myserver/groups/mygroup (results in the default wiki page); then browse to https://www.myserver/groups/ and the mygroup listing is there. Next step is to copy the subfolders wiki and weblog from the original mygroup back to the new Collaboration/Groups/mygroup folder; and, change the permissions for the lot back to _teamsserver as it was originally.
All is fine and the mygroup listing and link remains in the Available Groups Wikis page - UNTIL, the server is restarted or web server is restarted. After a restart, the Available Groups Wikis page is back to not showing any groups...
The question is: where is the document that is getting loaded when restarting web server that either deletes the mygroup listing on the Available Groups Wikis page, or fails to see that there is a group to be listed, or how is this otherwise fixed?
Thanks in advance for any insight into what the problem is and how to fix it.

Answer 1

How are you changing the perms back to _teamserver, through Server Admin showing system accounts? Make sure you are connecting to that local machine's Server Admin when setting the _teamserver perms for the Collaboration dir and not the OD Server. This might be causing a conflict if you are using the _teamserver account from your OD Master rather than the local machine.
Otherwise you can try wiping your ACLs using:
sudo chmod -R -N /Library/Collaboration
Then setup your ACLs again on the local machine's Server Admin with system accounts being shown or via the terminal.
Message was edited by: spraguga