We have a operational Aegir server thats seems to functioning normally - we can add new platforms, create new sites, clone, migrate sites no problem.
The trouble is that the base site, the 'Hostmaster' site won't Verify. Here is a partial log of the attempt (just to the point of failure - everything after the failure was okay):
(My hostmaster platform is 6.26)
Task starts processing
Trying to get property of non-object hosting.module:854
Running: /usr/share/drush/drush.php --uri='aegir.kern.org' provision-save '@hostmaster' --backend 2>&1
Bootstrap to phase 0.
Drush bootstrap phase : _drush_bootstrap_drush()
Bootstrap to phase 0.
Found command: provision-save (commandfile=provision)
Initializing drush commandfile: drush_make
Initializing drush commandfile: drush_make_d_o
Initializing drush commandfile: provision
Load alias @self
Load alias @
Could not find provision alias named: @
...
I have re-verified all of my platforms with no error, re-verified all of my servers with no error and all other sites on this install verify no problem.
I see on another Aegir instance I have access to that the base site does verify, and the missing alias appears to be @server_localhost on that box.
On the failing server I do have an @server_localhost alias present in my .drush directory.
If anyone could please point me in the right direction I would appreciate.
Thank you.
-Erin
Comments
Comment #1
anarcat CreditAttribution: anarcat commentedI am not sure I understand the last bits - are you saying that there's no "@server_localhost" alias on the failing server? That would seem strange: that alias is installed by default when a new server is setup, for the database server. Unless you installed Aegir using a remote mysql server, this should be present. If it's present in the frontend, try to reverify that server...
Comment #2
anarcat CreditAttribution: anarcat commentedComment #3
anarcat CreditAttribution: anarcat commentedFun, I just reproduced this on 2.x head. Bleh. I can't verify a new D7 platform here:
Comment #4
anarcat CreditAttribution: anarcat commentedOkay, so in my case what happened is that the platform didn't have a webserver associated to it. I added validation for this in commit [b0cdb4d] so that platforms like this can't be created in the future. I also added better error handling in [14bc1f97] so that those empty aliases provoke a real error instead of an unnoticed PHP notice that slipped into both our logs without being noticed:
That was actually one of the most important symptoms of the problem. If you try the latest 5.x branch again, you should see this instead:
.. which is still a bit cryptic, but at least it is an error, and therefore noticed and stops processing earlier.
Now to the actual cause of the problem - I am not sure. I reinstalled this site with provision-install earlier today, and for some reason the main webserver wasn't configured at all. I'll need to look into that, but in the meantime the workaround is to make sure you have a verified webserver and reverify the platform.
So next step: test reinstalling the frontend to see if the main webserver is configured properly in the frontend. Use:
OBVIOUSLY DON'T DO THIS IN PRODUCTION, IT WILL KILL YOUR AEGIR SITE! Marking needs work until i figure this out.
Comment #5
anarcat CreditAttribution: anarcat commentedi think this works now, at least I haven't reproduced this problem lately.
Comment #9
Keysource CreditAttribution: Keysource commentedHello
We are running Aegir to share multiples sites and we get this error whitout having found a solution.
We have check the logs and each files opened during the run and also the connectivity to the mysql server.
We have some logs to share if needed.
Our error message is : Error cannot load node id 13 to find its context
This happened when we tried to verify our websites hosted on a plateform with a server which is verify properly.
Any ideas?
Thanks you
Keysource