Unsolved
This post is more than 5 years old
9 Posts
0
1694
March 5th, 2010 14:00
new url doesn't seem to work
Hello.
I'm getting a 404 on the new url for atmos online. Do you see any problem below?
2010-03-05 11:02:24,376 DEBUG [jclouds.headers] (i/o thread 0) >> GET https://www.atmosonline.com/rest/namespace HTTP/1.1
2010-03-05 11:02:24,377 DEBUG [jclouds.headers] (i/o thread 0) >> x-emc-signature: XXXXXXXXXXXXXXXXX
010-03-05 11:02:24,377 DEBUG [jclouds.headers] (i/o thread 0) >> Date: Fri, 05 Mar 2010 19:02:23 GMT
2010-03-05 11:02:24,378 DEBUG [jclouds.headers] (i/o thread 0) >> Accept: text/xml
2010-03-05 11:02:24,378 DEBUG [jclouds.headers] (i/o thread 0) >> x-emc-uid: XXXXXXXXXXXXXXXX
2010-03-05 11:02:25,970 DEBUG [jclouds.headers] (i/o thread 0) << HTTP/1.1 404 Not Found
2010-03-05 11:02:25,970 DEBUG [jclouds.headers] (i/o thread 0) << null: HTTP/1.1 404 Not Found
2010-03-05 11:02:25,970 DEBUG [jclouds.headers] (i/o thread 0) << Date: Fri, 05 Mar 2010 13:48:52 GMT
2010-03-05 11:02:25,970 DEBUG [jclouds.headers] (i/o thread 0) << Content-Length: 297
2010-03-05 11:02:25,971 DEBUG [jclouds.headers] (i/o thread 0) << X-Cnection: close
2010-03-05 11:02:25,971 DEBUG [jclouds.headers] (i/o thread 0) << Content-Type: text/html; charset=iso-8859-1
2010-03-05 11:02:25,971 DEBUG [jclouds.headers] (i/o thread 0) << Server: Apache/2.2.3 (Red Hat)
2010-03-05 11:02:25,972 DEBUG [jclouds.wire] (i/o thread 0) << "[\n]"
2010-03-05 11:02:25,972 DEBUG [jclouds.wire] (i/o thread 0) << "[\n]"
2010-03-05 11:02:25,972 DEBUG [jclouds.wire] (i/o thread 0) << "
2010-03-05 11:02:25,972 DEBUG [jclouds.wire] (i/o thread 0) << "[\n]"
2010-03-05 11:02:25,972 DEBUG [jclouds.wire] (i/o thread 0) << "
Not Found
[\n]"2010-03-05 11:02:25,972 DEBUG [jclouds.wire] (i/o thread 0) << "
The requested URL /rest/namespace was not found on this server.
[\n]"2010-03-05 11:02:25,972 DEBUG [jclouds.wire] (i/o thread 0) << "
[\n]"
2010-03-05 11:02:25,972 DEBUG [jclouds.wire] (i/o thread 0) << " Apache/2.2.3 (Red Hat) Server at www.atmosonline.com Port 80[\n]"
2010-03-05 11:02:25,972 DEBUG [jclouds.wire] (i/o thread 0) << "[\n]"
jclouds
9 Posts
0
March 6th, 2010 18:00
I'll open a new thread for the server errors. I suggest that the documentation should clearly identify the online endpoint as https://accesspoint.atmosonline.com
jclouds
9 Posts
0
March 6th, 2010 18:00
I see that if I use instead: https://accesspoint.atmosonline.com I get farther.
However, I am getting a lot of server errors:
2010-03-06 18:32:21,786 DEBUG [jclouds.headers] (i/o thread 0) >> DELETE https://accesspoint.atmosonline.com/rest/namespace/adriancole-blobstore0/apps/ HTTP/1.1[\n]"The server encountered an internal error. Please try again. [\n]" [\n]"
2010-03-06 18:32:21,787 DEBUG [jclouds.headers] (i/o thread 0) >> x-emc-signature: XXXXXXXXXXXXXXXXX
2010-03-06 18:32:21,787 DEBUG [jclouds.headers] (i/o thread 0) >> Date: Sun, 07 Mar 2010 02:32:21 GMT
2010-03-06 18:32:21,787 DEBUG [jclouds.headers] (i/o thread 0) >> Accept: */*
2010-03-06 18:32:21,787 DEBUG [jclouds.headers] (i/o thread 0) >> x-emc-uid: XXXXXXXXXXXXXXXXXXXX
2010-03-06 18:32:36,931 DEBUG [jclouds.headers] (i/o thread 0) << HTTP/1.1 500 Internal Server Error
2010-03-06 18:32:36,931 DEBUG [jclouds.headers] (i/o thread 0) << null: HTTP/1.1 500 Internal Server Error
2010-03-06 18:32:36,931 DEBUG [jclouds.headers] (i/o thread 0) << Date: Sun, 07 Mar 2010 02:32:21 GMT
2010-03-06 18:32:36,931 DEBUG [jclouds.headers] (i/o thread 0) << Content-Length: 155
2010-03-06 18:32:36,931 DEBUG [jclouds.headers] (i/o thread 0) << X-Cnection: close
2010-03-06 18:32:36,931 DEBUG [jclouds.headers] (i/o thread 0) << Content-Type: text/xml
2010-03-06 18:32:36,931 DEBUG [jclouds.headers] (i/o thread 0) << Server: Apache
2010-03-06 18:32:36,932 DEBUG [jclouds.wire] (i/o thread 0) << "[\n]"
2010-03-06 18:32:36,932 DEBUG [jclouds.wire] (i/o thread 0) << "
2010-03-06 18:32:36,932 DEBUG [jclouds.wire] (i/o thread 0) << "[0x9]
1001[\n]"2010-03-06 18:32:36,932 DEBUG [jclouds.wire] (i/o thread 0) << "[0x9]
2010-03-06 18:32:36,932 DEBUG [jclouds.wire] (i/o thread 0) << "
2010-03-06 18:32:37,382 DEBUG [jclouds.headers] (i/o thread 0) >> DELETE https://
amarcionek
1 Rookie
•
56 Posts
0
March 8th, 2010 06:00
jclouds, I've been getting some similar behavior when I delete objects which were in the cloud prior to the URL and 1.2.7 upgrade. Occasionally I get a 500 with no API specific headers. More often, I get no response at all and my predefined timeout value kicks in, and in that case when I then retry, the server replies with a 404 indicating the object no longer exists.
However, I've created new subtoken IDs and retried writing, reading and then deleting and all of that is successful within good time frames.