Here are some tips to overcome issues you may run into while using DevShop.
If tasks are being queued up, but not running you may have to restart your queue runner.
Check your tasks list to see if anything is actually running:
Click the Gear icon in the header.
Click Task Logs link.
If you see Queued tasks (gray background) and none of them are running (you would see a spinner icon.) then your supervisor queue may have stopped.
To restart supervisor run the following command on your web server as a user that can sudo:
sudo service supervisor stopsudo service supervisor start
Your queued tasks should start running again.
This means that a settings.php file was found in a platform's codebase at sites/DOMAIN/settings.php.
This can happen if a site fails on clone, or cannot import the data for some reason.
SSH into the server as aegir.
cd into the folder of the environment (platform) you are trying to delete.
cd into the "sites" folder. Run "ls" to see what sites might still be there.
These sites might still exist (have a database created, etc.) so you should first try to run:
$ drush @DOMAIN provision-delete
If this doesn't work, then force-remove the folder:
$ rm -rf sites/DOMAIN
Retry the platform deletion task.
You might see this when submitting either a project or an environment settings form.
This is core Drupal behavior. If you open any node form, then someone else saves a node, then you submit the form, you will receive this message. This is to prevent you from overwriting the other users changes.
This happens occasionally in devshop without the other user, because "Verify" tasks save the node object.
The solution is to re-visit the settings page and try again once the verify tasks are complete.
A fix for this might be to block the user from loading the settings form if we detect a running verify task.
This obscure message comes from Aegir. It happens during an Install task, if there is already a
sites/env.proj.devshop.site folder within the environment. Sometimes the install task ran successfully first, and then for some reason, it a second install was attempted.
If you receive a PROVISION_SITE_INSTALLED error in an install task, but the site does work, you can simply verify the environment and ignore the failed installation
If a database was created as well as the
sites/env.proj.devshop.site folder, you can ignore it and the next install will create a new database and leave the old one. You can delete the database manually, or you can try a
$ drush @env.proj.devshop.site provision-delete
If the site does not work and there is no settings.php and database created, you can just remove the
$ rm -rf /var/aegir/projects/proj/env/sites/env.proj.devshop.site
...then Retry the Install task. Your site will install as normal.