Failed to create VM

Community Support
1

I’m trying to instantiate a virtual machine from the OpenNebula sunstone. The frontend is a CentOS machine with the sandbox installed. The two hosts are ubuntu 12.04 32 bits machines, and they can all connect each other with SSH without any password being asked.
I first downloaded the ubuntu 12.04 server image (i386), then I added an image from the sunstone. Then I create a VM template using the previously loaded image, and finally I created a VM, but I got “status: error”.
Here you can see the details about the template and the image, and the log file: https://onedrive.live.com/redir?resid=768CF89E7CF13325!4429&authkey=!APi2Q9p-3i96l4U&ithint=folder%2C

I’ll also paste the contents of the log file here:

Thu May 21 19:10:52 2015 [Z0][SCHED][I]: Init Scheduler Log system
Thu May 21 19:10:52 2015 [Z0][SCHED][I]: Starting Scheduler Daemon

 Scheduler Configuration File

DEFAULT_DS_SCHED=POLICY=1
DEFAULT_SCHED=POLICY=1
LIVE_RESCHEDS=0
LOG=DEBUG_LEVEL=3,SYSTEM=file
MAX_DISPATCH=30
MAX_HOST=1
MAX_VM=5000
MESSAGE_SIZE=1073741824
ONED_PORT=2633
SCHED_INTERVAL=30

Thu May 21 19:10:52 2015 [Z0][SCHED][I]: XML-RPC client using 1073741824 bytes for response buffer.

Thu May 21 19:10:52 2015 [Z0][SCHED][E]: Cannot contact oned, will retry… Error: Unable to transport XML to server and get XML response back. HTTP POST to URL ‘http://localhost:2633/RPC2’ failed. libcurl failed even to execute the HTTP transaction, explaining: couldn’t connect to host
Thu May 21 19:10:54 2015 [Z0][SCHED][I]: oned successfully contacted.
Thu May 21 19:10:54 2015 [Z0][SCHED][I]: Configuring scheduler for Zone ID: 0
Thu May 21 19:10:54 2015 [Z0][SCHED][I]: Starting scheduler loop…
Thu May 21 19:10:54 2015 [Z0][SCHED][I]: Scheduler loop started.
Thu May 21 19:42:25 2015 [Z0][SCHED][I]: Stopping the scheduler…
Thu May 21 19:42:25 2015 [Z0][SCHED][I]: Scheduler loop stopped.

2

You are probably using a proxy so the secheduler cannot access the oned
URL. Unset the proxy variable before starting the scheduler. Also, if you
are not using a proxy, check that oned is accessible from the machine
running the scheduler (with oneadmin credentials)

3

I have a problem, as described above, too. I have not set variables, but… problems with xml-rpc…
Even if it says that the HTTP POST method is empty (because I have no idea of what parameters I should pass), from the response message I get that the HTTP server is reachable.
I tried to connect to http://localhost:2633/RPC2 via terminal:

curl --data "" http://localhost:2633/RPC2

<HTML><HEAD><TITLE>Error 400</TITLE></HEAD><BODY><H1>Error 400</H1><P>According to your content-length HTTP header, your request is empty (zero length)</P><p><HR><b><i><a href="http://xmlrpc-c.sourceforge.net">ABYSS Web Server for XML-RPC For C/C++</a></i></b> version 1.40.0<br></p></BODY></HTML>

I enabled logging rpc messages in oned.conf
We see in /var/log/one/one_xmlrpc.log:

127.0.0.1:40946 - no_user - [19/Aug/2015:10:43:33 -0600] "POST /RPC2 HTTP/1.1" 200 467
127.0.0.1:40948 - no_user - [19/Aug/2015:10:43:33 -0600] "POST /RPC2 HTTP/1.1" 200 9983
127.0.0.1:40950 - no_user - [19/Aug/2015:10:44:03 -0600] "POST /RPC2 HTTP/1.1" 200 3593
127.0.0.1:40950 - no_user - [19/Aug/2015:10:44:03 -0600] "POST /RPC2 HTTP/1.1" 200 3593
127.0.0.1:40952 - no_user - [19/Aug/2015:10:44:03 -0600] "POST /RPC2 HTTP/1.1" 200 467
127.0.0.1:40954 - no_user - [19/Aug/2015:10:44:29 -0600] "HEAD / HTTP/1.1" 404 533
127.0.0.1:40956 - no_user - [19/Aug/2015:10:44:33 -0600] "POST /RPC2 HTTP/1.1" 200 3593
127.0.0.1:40956 - no_user - [19/Aug/2015:10:44:33 -0600] "POST /RPC2 HTTP/1.1" 200 3593
127.0.0.1:40958 - no_user - [19/Aug/2015:10:44:33 -0600] "POST /RPC2 HTTP/1.1" 200 467
127.0.0.1:40960 - no_user - [19/Aug/2015:10:44:43 -0600] "POST /RPC2 HTTP/1.1" 400 437
192.168.221.22:59502 - no_user - [19/Aug/2015:10:45:02 -0600] "POST /RPC2 HTTP/1.1" 400 437
127.0.0.1:40964 - no_user - [19/Aug/2015:10:45:02 -0600] "POST /RPC2 HTTP/1.1" 200 3593
127.0.0.1:40964 - no_user - [19/Aug/2015:10:45:03 -0600] "POST /RPC2 HTTP/1.1" 200 3593

Please, help fix the problem!