Error 0 occurred while receiving the document

root@vh1:/var/tmp# wget http://mirror.compevo.com/proxmox/proxmox-ve_5.2-1.iso
--2018-08-30 16:27:37--  http://mirror.compevo.com/proxmox/proxmox-ve_5.2-1.iso
Resolving mirror.compevo.com (mirror.compevo.com)... 103.25.61.44
Connecting to mirror.compevo.com (mirror.compevo.com)|103.25.61.44|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 641517568 (612M) [application/octet-stream]
Saving to: ‘proxmox-ve_5.2-1.iso’

proxmox-ve_5.2-1.iso          80%[==================================>         ] 493.39M  2.38MB/s    in 45s    

2018-08-30 16:28:22 (10.9 MB/s) - Connection closed at byte 517359784. Retrying.

--2018-08-30 16:28:23--  (try: 2)  http://mirror.compevo.com/proxmox/proxmox-ve_5.2-1.iso
Connecting to mirror.compevo.com (mirror.compevo.com)|103.25.61.44|:80... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 641517568 (612M), 124157784 (118M) remaining [application/octet-stream]
Saving to: ‘proxmox-ve_5.2-1.iso’



var/tmp is out of space the same as tmpfs

#this normally happens when Proxmox first uploads it to a place in /tmp on your / filesystem and if you have used a small HDD for testing it's easy for a simple ISO upload to fail for this reason. You'll have to wget directly to the main filesystem or datastore with more space.

proxmox, uploading, iso, solutionerror, receiving, vh, var, tmp, wget, http, compevo, ve_, resolving, connecting, awaiting, ok, length, octet, stream, lsquo, rsquo, mb, byte, retrying, partial, content, remaining, tmpfs, uploads, filesystem, hdd, upload, ll, datastore,

Latest Articles