> >> > Now I have to duplicate the sitegroup as I need 2 nearly identical sites. > >> > I tried it the way I did it many times before with non-midcom sites: > >> > > >> > - repligard -c repligard_sg1.conf -a -e sg1.xml (repligard_sg1.conf uses > >> > repligard.xml; login is sg1_admin+sg1) > >> > - create new company in aegir. > >> > - repligard -c repligard_sg2.conf -a -i sg1.xml (repligard_sg2.conf uses > >> > repligard.xml; login is sg2_admin+sg2) > >> > - adjust host in aegir and it should be done... > >> > > >> > But with MidCOM both the old and the new site are damaged now -( No > >> > midcom-init helps on any of the sites.
Hmmm.. some reverse engineering :-)
1. export from SG1 created package with some GUIDs 2. import to SG2 created new objects with GUIDs stored in sg1.xml 3. finally you got doubled GUIDs and MidCOM using GUIDS gets mad
Solution? After importing to SG try regenerating GUIDs by -r option and then adjust midcom installation in SG2
Did like you wrote, but nothing changed. In the meantime and after ~10 reinstallations of midgard-data and friends I saw something funny:
"AIS topic" and "MidCOM root topic" are not prefixed with the hostname of the sitegroup but with the hostname of SG0. If I have only one MidCOM site installed an rename these topics they are recreated in MidCOM init with this obviously wrong hostname. Could this be a reason why the two MIdCOM sites can not coexist?
btw: I use Debian woody/Apache 1.3.26/PHP 4.1.2/Midgard 1.5/ midcom-1.2rc+cvs.2004.01.30
Any ideas how to continue?
thanks, Ingo
Solt
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
