Without the agent.log on the two machines that you have added, I won't be able to diagnose the problem. If I had to guess at a cause I would check:
1. That each new agent has a fully qualified domain name that is reachable from both the internet and the manager
2. That the new agent can ping the manager, and vice versa, using that hostname, as well as it's IP (make sure the hostname points at the same IP)
3. That there is no firewalling that prevents the new agent from reaching the manager on port 5222
If those don't point out the problem, I'll need to see the contents of the agent.log on each of these new agents, including an agent restart.
I'll address these log entries all inline.
> manager.log:
>
> 2011-06-02 21:47:37+1000 [HTTPChannel,150,127.0.0.1] [WARNING -
> turbogears.identity.soprovider] No such user:
This is probably either a mismatch between your spotcloud and ecp credentials, and the manager/ui ones. This is not an error, this is a normal output when the credentials don't match.
>
> info.log
>
> 2011-06-02 21:47:37,508 cherrypy.msg INFO : Error getting csrf token
> cannot concatenate 'str' and 'NoneType' objects
This is an information message that shows when you have logging turned up, and there is no current login when calculating a CSRF token. Again, not an error, just saying it cannot merge the token and "NO USER". Turning error logging back to WARN, or fixing your login will remedy this issue.
>
> debug.log
>
> 2011-06-02 18:36:00,534 enomalism2.exceptions ERROR Machine
> 24bbd30c-8cef-11e0-bf41-005056b50032 not found.
This is just the output when ECP scans for a machine that is off. I don't think this is a problem either.
>
> spotcloud.log
>
> File "cherrypy/_cpengine.py", line 24, in SIGTERM
> AttributeError: 'module' object has no attribute 'engine'
> 18:14:24.984: warning : virProxyReadClientSocket:274 : Failed to read
> socket 12
This is two separate messages. One is from terminating the agent (the no attribute 'engine' one) that shows that the http engine has been turned off, and the other (failed to read socket 12) is a side effect of our probing the system for all potential hypervisor connections. This probing raises a warning in libvirt, which is part of the Redhat/Centos stack, and is harmless.
- Derek