Join us at engage.eucalyptus.com
All,
Installed Eucalpytus and having some issues. I'm trying to do a simple ec2-describe-availability-zones command and I am getting the following output:
dns1:euca2-dgarstang-x509 dgarstang$ ec2-describe-availability-zones
Unexpected error:
org.codehaus.xfire.fault.XFireFault: Server returned error code = 400 for URI : http://172.16.99.131:8773/services/Eucalyptus. Check server logs for details
at org.codehaus.xfire.fault.XFireFault.createFault(XFireFault.java:89)
at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:83)
at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:114)
at org.codehaus.xfire.client.Client.invoke(Client.java:336)
at org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:77)
at org.codehaus.xfire.client.XFireProxy.invoke(XFireProxy.java:57)
at $Proxy12.describeAvailabilityZones(Unknown Source)
at com.amazon.aes.webservices.client.Jec2Impl.describeAvailabilityZones(Jec2Impl.java:2097)
at com.amazon.aes.webservices.client.Jec2Impl.describeAvailabilityZones(Jec2Impl.java:2075)
at com.amazon.aes.webservices.client.cmd.DescribeAvailabilityZones.invokeOnline(DescribeAvailabilityZones.java:55)
at com.amazon.aes.webservices.client.cmd.BaseCmd.invoke(BaseCmd.java:876)
at com.amazon.aes.webservices.client.cmd.DescribeAvailabilityZones.main(DescribeAvailabilityZones.java:64)
Caused by: org.codehaus.xfire.XFireRuntimeException: Server returned error code = 400 for URI : http://172.16.99.131:8773/services/Eucalyptus. Check server logs for details
at org.codehaus.xfire.transport.http.HttpChannel.sendViaClient(HttpChannel.java:130)
at org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel.java:48)
at org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26)
at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:79)
... 10 more
All the ec2 commands are returning this output. I can use the ec2 commands right? I'd rather use the ec2 tools, since the euca2 tools require python rather than java and getting them installed has been a pain.
In the cc.log on the front-end, I see it's trying to access this URL, which is on the node controller:
http://172.16.99.133:8775/axis2/services/EucalyptusNC
When I attempt to connect to that URL, I get a 'Not Found' message.
On the node controller, if I look at /opt/euca-axis2c/services/EucalyptusNC (what is axis2 anyway?), I see the following files:
[root@node01 EucalyptusNC]# ls -l
total 1032
-rwxr-xr-x 1 root root 1021440 Apr 11 2011 libEucalyptusNC.so
-rw-r--r-- 1 root root 1597 Apr 11 2011 services_noWS.xml
-rw-r--r-- 1 root root 4074 Apr 11 2011 services_WS.xml
-rwxr-xr-x 1 root root 4074 Apr 11 2011 services.xml
Anyway, what's wrong here? I don't know where else to look, or what to look for
Doug.
I just bought up a new node as per the Eucalyptus instructions. Same deal, same error.
Also... what's the deal with libvirt? The libvirt app does not create the libvirt group, and the eucalyptus-nc software therefore doesn't add the eucalyptus user to the group that doesn't exist. However, eucalyptus-nc does NOT report any errors on start.
I'm confused. Is libvirt even used at all? I think it's connected to locally from the node daemon software rather than over the network, right? I guess that's why eucalyptus-nc doesn't start the libvirt daemon.
Doug.
Apparently I'm the only person in the Universe that's ever had this issue... even after following the docs...
When I go to:
http://172.16.99.133:8775/axis2/services
I see a list of deployed services, but, still http://172.16.99.133:8775/axis2/services/EucalyptuNC gives me :
"Not Found
The requested URL was not found on this server."
Arrrgh!!!!!
Hi,
Can you instead use euca2ools for your user / admin related tasks you want to perform on the eucalyptus cloud ?
This guide will help you get started
http://open.eucalyptus.com/wiki/Euca2oolsGuide_v1.3
Cheers!
Deependra
Deependra, thanks, but I'd rather not. I'm on a Mac and I wasn't able to get the euca2tools to work. There was all sorts of issues with python dependancies etc. That's why I chose ec2-api-tools, which are supposed to work. If I can get this operational, other people in the organization are going to want to use the api tools as well. They can't use euca2tools due to how hard it is to install. ec2 tools installs easy.
So, I went ahead and got euca2tools installed anyway, and now it seems to work...
dns1:.euca dgarstang$ euca-describe-regions
REGION Eucalyptus http://172.16.99.131:8773/services/Eucalyptus
REGION Walrus http://172.16.99.131:8773/services/Walrus
dns1:.euca dgarstang$ euca-describe-availability-zones
AVAILABILITYZONE cluster01 172.16.99.131
So, I guess it doesn't work with ec2-api-tools. How come? It's supposed to isn't it?
Doug.
Hi Doug,
We test and certify Eucalyptus against the ec2 API tools v1.4.1 (ec2ools). However, current version is 1.5 which we don't support or test with and is probably the set you are using. This may explain why it doesn't work for you.