ISO Images upload

v.4.12

I try to load a new disk image, nothing happens.
The image starts to be loaded, the traffic to the server and the local machine shows the activity, but 700 megabytes downloaded for 3 hours, and cant finish)

Upload hangs

The problem appeared recently. Before this, image is loaded without problems.
Tested on different servers with OpenNebula.

Whats wrong?

What happens if you try to upload a smaller ISO such as Ubuntu Minimal?

Try to upload 219M - FreeBSD Boot only ISO - the same problem.
Upload hangs on two different servers.

I’m fairly new to this but I guess my approach would be a) to check available space for the store you’re uploading it to and b) to tail -f /var/log/one/oned.log for obvious errors.

Hopefully someone with a bit more experience here will be able to help you out.

Enough space)

There are no errors from beginning upload

[root@opennebula-fr ~]# tail -f /var/log/one/oned.log
Mon Jul 20 01:20:36 2015 [Z0][ReM][D]: Req:9440 UID:0 ClusterPoolInfo invoked 
Mon Jul 20 01:20:36 2015 [Z0][ReM][D]: Req:9440 UID:0 ClusterPoolInfo result SUCCESS, "<CLUSTER_POOL></CLUS..."
Mon Jul 20 01:20:36 2015 [Z0][ReM][D]: Req:1792 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Mon Jul 20 01:20:37 2015 [Z0][ReM][D]: Req:1792 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL><VM><ID>37<..."
Mon Jul 20 01:20:37 2015 [Z0][ReM][D]: Req:1584 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Mon Jul 20 01:20:37 2015 [Z0][ReM][D]: Req:1584 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL><VM><ID>37<..."
Mon Jul 20 01:20:43 2015 [Z0][InM][D]: Monitoring datastore default (1)
Mon Jul 20 01:20:43 2015 [Z0][InM][D]: Monitoring datastore files (2)
Mon Jul 20 01:20:44 2015 [Z0][ImM][D]: Datastore default (1) successfully monitored.
Mon Jul 20 01:20:44 2015 [Z0][ImM][D]: Datastore files (2) successfully monitored.
Mon Jul 20 01:20:52 2015 [Z0][ImM][D]: Datastore system (0) successfully monitored.
Mon Jul 20 01:20:52 2015 [Z0][InM][D]: Host OpenNebula-FR (0) successfully monitored.
Mon Jul 20 01:20:52 2015 [Z0][VMM][D]: VM 37 successfully monitored: STATE=a USEDCPU=0.5 USEDMEMORY=524288 NETRX=1573693426 NETTX=200900786
Mon Jul 20 01:20:53 2015 [Z0][VMM][D]: VM 56 successfully monitored: STATE=a USEDCPU=1.0 USEDMEMORY=2106492 NETRX=659893618 NETTX=908660693
Mon Jul 20 01:20:53 2015 [Z0][VMM][D]: VM 60 successfully monitored: STATE=a USEDCPU=1.5 USEDMEMORY=1185408 NETRX=623995121 NETTX=94854909
Mon Jul 20 01:20:54 2015 [Z0][VMM][D]: VM 70 successfully monitored: STATE=a USEDCPU=0.5 USEDMEMORY=1206700 NETRX=608536946 NETTX=45641253
Mon Jul 20 01:21:06 2015 [Z0][ReM][D]: Req:8176 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Mon Jul 20 01:21:06 2015 [Z0][ReM][D]: Req:8176 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL><VM><ID>37<..."
Mon Jul 20 01:21:07 2015 [Z0][ReM][D]: Req:800 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Mon Jul 20 01:21:07 2015 [Z0][ReM][D]: Req:800 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL><VM><ID>37<..."
Mon Jul 20 01:21:17 2015 [Z0][ImM][D]: Datastore system (0) successfully monitored.
Mon Jul 20 01:21:17 2015 [Z0][InM][D]: Host OpenNebula-FR (0) successfully monitored.
Mon Jul 20 01:21:17 2015 [Z0][VMM][D]: VM 37 successfully monitored: STATE=a USEDCPU=1.0 USEDMEMORY=524288 NETRX=1573711420 NETTX=200901150
Mon Jul 20 01:21:18 2015 [Z0][VMM][D]: VM 56 successfully monitored: STATE=a USEDCPU=1.5 USEDMEMORY=2106492 NETRX=659929699 NETTX=908687528
Mon Jul 20 01:21:18 2015 [Z0][VMM][D]: VM 60 successfully monitored: STATE=a USEDCPU=1.5 USEDMEMORY=1185408 NETRX=624030998 NETTX=94881921
Mon Jul 20 01:21:18 2015 [Z0][VMM][D]: VM 70 successfully monitored: STATE=a USEDCPU=1.0 USEDMEMORY=1206700 NETRX=608554820 NETTX=45641571
Mon Jul 20 01:21:36 2015 [Z0][ReM][D]: Req:5936 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Mon Jul 20 01:21:37 2015 [Z0][ReM][D]: Req:5936 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL><VM><ID>37<..."
Mon Jul 20 01:21:37 2015 [Z0][ReM][D]: Req:8864 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Mon Jul 20 01:21:37 2015 [Z0][ReM][D]: Req:8864 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL><VM><ID>37<..."
Mon Jul 20 01:21:37 2015 [Z0][ImM][D]: Datastore system (0) successfully monitored.
Mon Jul 20 01:21:37 2015 [Z0][InM][D]: Host OpenNebula-FR (0) successfully monitored.
Mon Jul 20 01:21:37 2015 [Z0][VMM][D]: VM 37 successfully monitored: STATE=a USEDCPU=0.0 USEDMEMORY=524288 NETRX=1573725528 NETTX=200901472
Mon Jul 20 01:21:38 2015 [Z0][VMM][D]: VM 56 successfully monitored: STATE=a USEDCPU=0.0 USEDMEMORY=2106492 NETRX=659959931 NETTX=908711414
Mon Jul 20 01:21:38 2015 [Z0][VMM][D]: VM 60 successfully monitored: STATE=a USEDCPU=1.0 USEDMEMORY=1185408 NETRX=624062485 NETTX=94908549
Mon Jul 20 01:21:38 2015 [Z0][VMM][D]: VM 70 successfully monitored: STATE=a USEDCPU=1.0 USEDMEMORY=1206700 NETRX=608568922 NETTX=45641809
Mon Jul 20 01:21:39 2015 [Z0][InM][D]: Monitoring datastore default (1)
Mon Jul 20 01:21:39 2015 [Z0][InM][D]: Monitoring datastore files (2)
Mon Jul 20 01:21:40 2015 [Z0][ImM][D]: Datastore files (2) successfully monitored.
Mon Jul 20 01:21:40 2015 [Z0][ImM][D]: Datastore default (1) successfully monitored.

I have the exact same issue. I can upload smaller iso images. But I tried a 3.7GB windows iso, the uploader stops at a random point. I live monitored the sunstone log, and it showed each packet received until it just stopped without any warnings or even timeouts.

But in my case every time it fails, sunstone-server crashes and the logs don’t indicate anything. I basically have to restart sunstone-server each time to bring it back up.

host: centos 7
Opennebula 4.12.1

Amit Biswas forum@opennebula.org writes:

I have the exact same issue. I can upload smaller iso images. But I
tried a 3.7GB windows iso, the uploader stops at a random point. I
live monitored the sunstone log, and it showed each packet received
until it just stopped without any warnings or even timeouts.

But in my case every time it fails, sunstone-server crashes and the
logs don’t indicate anything. I basically have to restart
sunstone-server each time to bring it back up.

According to documentation[1]:

  • make sure you have enough space in :tmpdir: defined in
    sunstone-server.conf

  • make sure any HTTP reverse-proxy does not limit the body size

Regards.

Footnotes:
[1] http://docs.opennebula.org/4.12/user/virtual_resource_management/img_guide.html#uploading-images-from-sunstone

3 Likes

Really! The problem was in client_max_body_size in NGINX.
Thank you!

Wow. As soon as you posted the reply, my monitoring daemon just set off on the disk space the /var/tmp directory is in. Thanks for pointing me to the right direction.

Also @GabrielDias can you tell me where is the config file located for NGINX. I didn’t see it under /etc

Hi, @akbisw

As default sunstone didn’t work with nginx, it is a custom solution.
But you can do it yourself installing nginx and adding next lines to nginx .conf

server {
	server_name yourdomain.name;
	listen 443;
	ssl on;
	ssl_certificate /etc/nginx/server.crt;
	ssl_certificate_key /etc/nginx/server.key;

location / {
	proxy_pass http://127.0.0.1:9869;
	}
}