Posted by j2parker on May 12, 2010 at 6:14pm
Following a hostmaster upgrade the next step is to get the platforms and associated sites into the new front end (node/add/platform). The process creates a new platform_###.conf in /var/aegir/config/platform.d
The platform_###.conf files from the previous hostmaster install still exist. This causes multiple apache directives to be applied to the same directory.
The platform_###.conf files from the previous hostmaster install should be manually deleted following a hostmaster upgrade.
Comments
I'm not following this at
I'm not following this at all, sorry..
I'm lost already.. following a hostmaster upgrade, all the existing platforms and sites are still in the database, it's just been upgraded.. why are you having to add the nodes again?
Why are they being applied to the same directory? The new hostmaster frontend should be in a new platform (that's the whole point, it's basically the same as the Migrate task for normal sites
Why? We don't delete the previous hostmaster platform, so why would we delete its apache config?
It sort of sounds like you misunderstood the steps of the UPGRADE.txt and what it's meant to do. Either that or I'm completely misunderstanding :)
manual upgrade
I was remiss in not including that the upgrade was by a fresh hostmaster install not by using UPGRADE.txt. So when the platforms were added they received a new node number and a new platform config.
Since there were now multiple configs for the same platform there were multiple directives being applied to the same directory.