We are in the process of migrating this forum. A new space will be available soon. We are sorry for the inconvenience.

Timeout while copying an object


Schnouki
03-07-2014, 04:41 PM
Well since the switchs were updated it works much much better. Thanks vcasse (and other hubiC team members!)

Rey
03-07-2014, 04:36 PM
This problem exists for 2 years and is still not solved. Dont expect too much about your case...

OderWat
02-21-2014, 10:51 AM
I just chime in to confirm this problem. It works well for smaller files (< 100MB I got no problem so far) but >200 MB I did not manage to copy a single file at all

Schnouki
02-20-2014, 11:44 AM
That makes sense. I'll follow that and keep you posted.
Thanks!

vcasse
02-20-2014, 11:00 AM
Hi,

Your timeout is probably because of a network issue.
We work on it. You could follow our actions on this : http://status.ovh.net/?do=details&id=6361

Vincent

Schnouki
02-20-2014, 10:49 AM
Any news about this?

Schnouki
02-17-2014, 09:32 AM
Hi,

I'm trying to copy an object as described in http://docs.openstack.org/api/openst...py-object.html. However both methods (PUT with X-Copy-From and COPY with Destination) fail with a timeout.
This has also been reported here: https://forums.hubic.com/showthread....ull=1#post4277

My request:

Code:
curl --verbose \
    -X COPY "https://lb1.hubic.ovh.net/v1/AUTH_abcdef/default/path/to/a/file" \
    -H "Destination: /other_container/other_path/to/a/file" \
    -H "X-Auth-Token: my_token" \
    -H "Content-Length: 0"         

...                      

> COPY /v1/AUTH_abcdef/default/path/to/a/file HTTP/1.1
> User-Agent: curl/7.35.0
> Host: lb1.hubic.ovh.net
> Accept: */*
> Destination: /other_container/other_path/to/a/file
> X-Auth-Token: my_token
> Content-Length: 0
> 
< HTTP/1.1 408 Request Timeout
< Content-Length: 116
< Content-Type: text/html; charset=UTF-8
< X-Trans-Id: txabcdef
< Date: Mon, 17 Feb 2014 08:20:25 GMT
< 
* Connection #0 to host lb1.hubic.ovh.net left intact

Request Timeout

The server has waited too long for the request to be sent by the client.

Am I doing something wrong or is there an error on the hubiC side? If so, when can we expect it to be fixed?

Thanks a lot!