Hi all,
I cloned a small site (ie 4MB database and no files) but the task spins forever.
omega8cc says here http://omega8.cc/aegir-task-fails-or-spins-forever-126
"But before you will go to the steps nr 7 and 8 above (platform and site re-verify), you must delete also the migrated/cloned site node in Aegir first."
I don't follow this - it can't mean delete the original site because then after the clone I would have only one site not two sites - but then if it does not mean delete the cloned site I am not sure what "delete the cloned site node" means.
Also omega8cc says here https://drupal.org/node/941068#comment-3699026 that task spinning forever can be caused by php / mysql limits being too low. Can anyone please suggest what the php and mysql limits should be to avoid tasks spinning forever? Prevention is better than cure so if possible I would prefer to prevent the tasks spinning forever problem arising.
Thanks...
Comments
You delte the site node, not the site itself
As it says below, "Warning! Don’t mix up deleting site’s or platform’s node with using the Delete task!"
So you will delete the site node that contains the site's 'metadata' like url. The site files and database are still in place, so when you re-verify the platform where the site files are located, Aegir will discover the site and create an import task. The import task will create a new site node with 'metadata'.
@ omega8cc you just said on
@ omega8cc you just said on the other thread -https://groups.drupal.org/node/306518#comment-941698 - that BOA sets values in my.cnf that are specifically intended for BOA requirements so does your old comment here https://drupal.org/node/941068#comment-3699026 about increasing php/mysql limits apply to BOA? If so can you please tell me specifically what php/mysql increases I should try to avoid the problem of simple migrate tasks spinning forever?
Thanks...