Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Just for information, when I put this command in Proxy server:

root@srv-os-swift-proxy:~# swift-recon -d -v

===============================================================================
--> Starting reconnaissance on 1 hosts
===============================================================================
[2013-06-13 11:03:44] Checking disk usage now
-> http://192.168.220.62:6000/recon/diskusage: [{'device': 'sdb1', 'avail': 1606
Distribution Graph:
  0%    1 *********************************************************************
Disk usage: space used: 358199296 of 160981585920
Disk usage: space free: 160623386624 of 160981585920
Disk usage: lowest: 0.22%, highest: 0.22%, avg: 0.222509483897%
===============================================================================

root@srv-os-swift-proxy:~# swift -V 2.0 -A http://192.168.220.70:5000/v2.0 -U

demo:admin -K $ADMINPASS stat
Account: AUTH_57XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Containers: 1
   Objects: 6
     Bytes: 720243
Accept-Ranges: bytes
X-Timestamp: 1371030931.41193
Content-Type: text/plain; charset=utf-8

root@srv-os-swift-proxy:~# curl -k -v -H 'X-Storage-User: demo:admin' -H 'X-Storage-Pass: $ADMINPASS' http://192.168.220.70:5000/auth/v2.0

* About to connect() to 192.168.220.70 port 5000 (#0)
*   Trying 192.168.220.70... connected
> GET /auth/v2.0 HTTP/1.1
> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
> Host: 192.168.220.70:5000
> Accept: */*
> X-Storage-User: demo:admin
> X-Storage-Pass: $ADMINPASS
>
< HTTP/1.1 404 Not Found
< Vary: X-Auth-Token
< Content-Type: application/json
< Content-Length: 93
< Date: Thu, 13 Jun 2013 09:37:02 GMT
<
* Connection #0 to host 192.168.220.70 left intact
* Closing connection #0
{"error": {"message": "The resource could not be found.", "code": 404, "title": "Not Found"}}

Just for information, when I put this command in Proxy server:

root@srv-os-swift-proxy:~# swift-recon -d -v

===============================================================================
--> Starting reconnaissance on 1 hosts
===============================================================================
[2013-06-13 11:03:44] Checking disk usage now
-> http://192.168.220.62:6000/recon/diskusage: [{'device': 'sdb1', 'avail': 1606
Distribution Graph:
  0%    1 *********************************************************************
Disk usage: space used: 358199296 of 160981585920
Disk usage: space free: 160623386624 of 160981585920
Disk usage: lowest: 0.22%, highest: 0.22%, avg: 0.222509483897%
===============================================================================

root@srv-os-swift-proxy:~# swift -V 2.0 -A http://192.168.220.70:5000/v2.0 -U

demo:admin -K $ADMINPASS stat
Account: AUTH_57XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Containers: 1
   Objects: 6
     Bytes: 720243
Accept-Ranges: bytes
X-Timestamp: 1371030931.41193
Content-Type: text/plain; charset=utf-8

root@srv-os-swift-proxy:~# curl -k -v -H 'X-Storage-User: demo:admin' -H 'X-Storage-Pass: $ADMINPASS' http://192.168.220.70:5000/auth/v2.0

* About to connect() to 192.168.220.70 port 5000 (#0)
*   Trying 192.168.220.70... connected
> GET /auth/v2.0 HTTP/1.1
> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
> Host: 192.168.220.70:5000
> Accept: */*
> X-Storage-User: demo:admin
> X-Storage-Pass: $ADMINPASS
>
< HTTP/1.1 404 Not Found
< Vary: X-Auth-Token
< Content-Type: application/json
< Content-Length: 93
< Date: Thu, 13 Jun 2013 09:37:02 GMT
<
* Connection #0 to host 192.168.220.70 left intact
* Closing connection #0
{"error": {"message": "The resource could not be found.", "code": 404, "title": "Not Found"}}

root@srv-os-swift-proxy:~# curl -k -v -X 'POST' http://192.168.220.70:5000/v2.0/tokens -d '{"auth":{"passwordCredentials":{"username":"admin", "password":"test2013"}, "tenantName":"demo"}}' -H 'Content-type: application/json' -H 'Accept: application/xml'

* About to connect() to 192.168.220.70 port 5000 (#0)
*   Trying 192.168.220.70... connected
> POST /v2.0/tokens HTTP/1.1
> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
> Host: 192.168.220.70:5000
> Content-type: application/json
> Accept: application/xml
> Content-Length: 96
>
* upload completely sent off: 96out of 96 bytes
< HTTP/1.1 200 OK
< Vary: X-Auth-Token
< Content-Type: application/xml
< Content-Length: 5428
< Date: Thu, 13 Jun 2013 12:25:49 GMT
<
<?xml version="1.0" encoding="UTF-8"?>
<access xmlns="http://docs.openstack.org/identity/api/v2.0">
  <token issued_at="2013-06-13T12:25:49.632643" expires="2013-06-14T12:25:49Z" id="XXXXXXXX">
    <tenant enabled="true" name="demo" id="57XXXXXXXXXXXXXXXXXXX"/>
  </token>
  <serviceCatalog>
    <service type="object-store" name="swift">
      <endpoints_links/>
      <endpoint adminURL="http://192.168.220.71:8080/v1" region="RegionOne" publicURL="http://192.168.220.71:8080/v1/AUTH_57XXXXXXXXXXXXXXXXXXX" internalURL="http://192.168.220.71:8080/v1/AUTH_57XXXXXXXXXXXXXXXXXXX" id="78XXXXXXXXXXXXXXXXXXXXX"/>
    </service>
    <service type="image" name="glance">
      <endpoints_links/>
      <endpoint adminURL="http://192.168.220.64:9292/v2" region="RegionOne" publicURL="http://192.168.220.64:9292/v2" internalURL="http://192.168.220.64:9292/v2" id="0dXXXXXXXXXXXXXXXXXXXXXXXX"/>
    </service>
    <service type="compute" name="nova">
      <endpoints_links/>
      <endpoint adminURL="http://192.168.220.60:8774/v2/57XXXXXXXXXXXXXXXXXXX" region="RegionOne" publicURL="http://192.168.220.60:8774/v2/57XXXXXXXXXXXXXXXXXXX" internalURL="http://192.168.220.60:8774/v2/57XXXXXXXXXXXXXXXXXXX" id="17XXXXXXXXXXXXXXXXXXXXXX"/>
    </service>
    <service type="ec2" name="ec2">
      <endpoints_links/>
      <endpoint adminURL="http://192.168.220.70:8773/services/Admin" region="RegionOne" publicURL="http://192.168.220.70:8773/services/Cloud" internalURL="http://192.168.220.70:8773/services/Cloud" id="28XXXXXXXXXXXXXXXX"/>
    </service>
    <service type="identity" name="keystone">
      <endpoints_links/>
      <endpoint adminURL="http://192.168.220.70:35357/v2.0" region="RegionOne" publicURL="http://192.168.220.70:5000/v2.0" internalURL="http://192.168.220.70:5000/v2.0" id="00XXXXXXXXXXXXXXXXXXXXXX"/>
    </service>
  </serviceCatalog>
  <user username="admin" id="a5XXXXXXXXXXXXXXXXXXXXXXX" name="admin">
    <roles_links/>
    <role name="admin"/>
  </user>
  <metadata is_admin="0">
    <roles>
      <role>bdXXXXXXXXXXXXXXXXXX</role>
    </roles>
  </metadata>
</access>
* Connection #0 to host 192.168.220.70 left intact
* Closing connection #0

root@srv-os-swift-proxy:~# curl -k -v -H 'X-Auth-Token: XXXXX' http://192.168.220.71:8080/v1/AUTH_57XXXXXXXXXXXXXXXXXXX

   * About to connect() to 192.168.220.71 port 8080 (#0)
    *   Trying 192.168.220.71... connected
    > GET /v1/AUTH_57XXXXXXXXXXXXXXXXXXX HTTP/1.1
    > User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
    > Host: 192.168.220.71:8080
    > Accept: */*
    > X-Auth-Token: XXXXXX
    >
    < HTTP/1.1 200 OK
    < Content-Length: 10
    < Accept-Ranges: bytes
    < X-Timestamp: 1371030931.41193
    < X-Account-Bytes-Used: 720243
    < X-Account-Container-Count: 1
    < Content-Type: text/plain; charset=utf-8
    < X-Account-Object-Count: 6
    < Date: Thu, 13 Jun 2013 12:30:15 GMT
    <
    VEEAM-WAN
    * Connection #0 to host 192.168.220.71 left intact
    * Closing connection #0

UP ! Please ! :) The problem is the result of OpenStack.


A member of the community Veeam left a message at my problem:

I'm not sure about the second error message, but the disk space inefficient message is correct if you are trying to upload large chunks without using the "Advanced" option. When using "Advanced" we automatically break large files into smaller "chunks" that can be uploaded (default is 10MB, can be set under options). With "Simple" mode we attempt upload the files exactly as they exist on the local disk, so you hit chunk size limits with large files.

Veeam support response:

Hello,
 
Thank you for your reply.
 
Here is the information that I have seen in the log:
"
2013-06-12 14:26:23,700 [PL] [1] INFO - Loading info for share drive cbb_configuration
2013-06-12 14:26:23,989 [Base] [14] WARN - memoryManager: Memory allocation limit is used. Available: 314572800, Need: 25894115115
2013-06-12 14:26:23,992 [Base] [14] WARN - Allocating 25,894,115,115 bytes store on disk.
2013-06-12 14:26:24,004 [Base] [14] ERROR - memoryManager: Failed to allocate file on disk. Available: 0, Need: 25894115115. Error: Not enough space on the disk.
"
It will define the cause of occurrence of problem. I do not think the problem came from the side of Veeam.
OpenStack is probably that returns the value of the space incorrectly.
 
Have you ever contacted OpenStack? What is the answer?
 
I am always in your disposal.
 
Waiting for your answer,
Sincerely,
Veeam Software.

-------------------------------------

Just for information, when I put this command in Proxy server:

root@srv-os-swift-proxy:~# swift-recon -d -v

===============================================================================
--> Starting reconnaissance on 1 hosts
===============================================================================
[2013-06-13 11:03:44] Checking disk usage now
-> http://192.168.220.62:6000/recon/diskusage: [{'device': 'sdb1', 'avail': 1606
Distribution Graph:
  0%    1 *********************************************************************
Disk usage: space used: 358199296 of 160981585920
Disk usage: space free: 160623386624 of 160981585920
Disk usage: lowest: 0.22%, highest: 0.22%, avg: 0.222509483897%
===============================================================================

root@srv-os-swift-proxy:~# swift -V 2.0 -A http://192.168.220.70:5000/v2.0 -U

demo:admin -K $ADMINPASS stat
Account: AUTH_57XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Containers: 1
   Objects: 6
     Bytes: 720243
Accept-Ranges: bytes
X-Timestamp: 1371030931.41193
Content-Type: text/plain; charset=utf-8

root@srv-os-swift-proxy:~# curl -k -v -H 'X-Storage-User: demo:admin' -H 'X-Storage-Pass: $ADMINPASS' http://192.168.220.70:5000/auth/v2.0

* About to connect() to 192.168.220.70 port 5000 (#0)
*   Trying 192.168.220.70... connected
> GET /auth/v2.0 HTTP/1.1
> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
> Host: 192.168.220.70:5000
> Accept: */*
> X-Storage-User: demo:admin
> X-Storage-Pass: $ADMINPASS
>
< HTTP/1.1 404 Not Found
< Vary: X-Auth-Token
< Content-Type: application/json
< Content-Length: 93
< Date: Thu, 13 Jun 2013 09:37:02 GMT
<
* Connection #0 to host 192.168.220.70 left intact
* Closing connection #0
{"error": {"message": "The resource could not be found.", "code": 404, "title": "Not Found"}}

root@srv-os-swift-proxy:~# curl -k -v -X 'POST' http://192.168.220.70:5000/v2.0/tokens -d '{"auth":{"passwordCredentials":{"username":"admin", "password":"test2013"}, "tenantName":"demo"}}' -H 'Content-type: application/json' -H 'Accept: application/xml'

* About to connect() to 192.168.220.70 port 5000 (#0)
*   Trying 192.168.220.70... connected
> POST /v2.0/tokens HTTP/1.1
> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
> Host: 192.168.220.70:5000
> Content-type: application/json
> Accept: application/xml
> Content-Length: 96
>
* upload completely sent off: 96out of 96 bytes
< HTTP/1.1 200 OK
< Vary: X-Auth-Token
< Content-Type: application/xml
< Content-Length: 5428
< Date: Thu, 13 Jun 2013 12:25:49 GMT
<
<?xml version="1.0" encoding="UTF-8"?>
<access xmlns="http://docs.openstack.org/identity/api/v2.0">
  <token issued_at="2013-06-13T12:25:49.632643" expires="2013-06-14T12:25:49Z" id="XXXXXXXX">
    <tenant enabled="true" name="demo" id="57XXXXXXXXXXXXXXXXXXX"/>
  </token>
  <serviceCatalog>
    <service type="object-store" name="swift">
      <endpoints_links/>
      <endpoint adminURL="http://192.168.220.71:8080/v1" region="RegionOne" publicURL="http://192.168.220.71:8080/v1/AUTH_57XXXXXXXXXXXXXXXXXXX" internalURL="http://192.168.220.71:8080/v1/AUTH_57XXXXXXXXXXXXXXXXXXX" id="78XXXXXXXXXXXXXXXXXXXXX"/>
    </service>
    <service type="image" name="glance">
      <endpoints_links/>
      <endpoint adminURL="http://192.168.220.64:9292/v2" region="RegionOne" publicURL="http://192.168.220.64:9292/v2" internalURL="http://192.168.220.64:9292/v2" id="0dXXXXXXXXXXXXXXXXXXXXXXXX"/>
    </service>
    <service type="compute" name="nova">
      <endpoints_links/>
      <endpoint adminURL="http://192.168.220.60:8774/v2/57XXXXXXXXXXXXXXXXXXX" region="RegionOne" publicURL="http://192.168.220.60:8774/v2/57XXXXXXXXXXXXXXXXXXX" internalURL="http://192.168.220.60:8774/v2/57XXXXXXXXXXXXXXXXXXX" id="17XXXXXXXXXXXXXXXXXXXXXX"/>
    </service>
    <service type="ec2" name="ec2">
      <endpoints_links/>
      <endpoint adminURL="http://192.168.220.70:8773/services/Admin" region="RegionOne" publicURL="http://192.168.220.70:8773/services/Cloud" internalURL="http://192.168.220.70:8773/services/Cloud" id="28XXXXXXXXXXXXXXXX"/>
    </service>
    <service type="identity" name="keystone">
      <endpoints_links/>
      <endpoint adminURL="http://192.168.220.70:35357/v2.0" region="RegionOne" publicURL="http://192.168.220.70:5000/v2.0" internalURL="http://192.168.220.70:5000/v2.0" id="00XXXXXXXXXXXXXXXXXXXXXX"/>
    </service>
  </serviceCatalog>
  <user username="admin" id="a5XXXXXXXXXXXXXXXXXXXXXXX" name="admin">
    <roles_links/>
    <role name="admin"/>
  </user>
  <metadata is_admin="0">
    <roles>
      <role>bdXXXXXXXXXXXXXXXXXX</role>
    </roles>
  </metadata>
</access>
* Connection #0 to host 192.168.220.70 left intact
* Closing connection #0

root@srv-os-swift-proxy:~# curl -k -v -H 'X-Auth-Token: XXXXX' http://192.168.220.71:8080/v1/AUTH_57XXXXXXXXXXXXXXXXXXX

   * About to connect() to 192.168.220.71 port 8080 (#0)
    *   Trying 192.168.220.71... connected
    > GET /v1/AUTH_57XXXXXXXXXXXXXXXXXXX HTTP/1.1
    > User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
    > Host: 192.168.220.71:8080
    > Accept: */*
    > X-Auth-Token: XXXXXX
    >
    < HTTP/1.1 200 OK
    < Content-Length: 10
    < Accept-Ranges: bytes
    < X-Timestamp: 1371030931.41193
    < X-Account-Bytes-Used: 720243
    < X-Account-Container-Count: 1
    < Content-Type: text/plain; charset=utf-8
    < X-Account-Object-Count: 6
    < Date: Thu, 13 Jun 2013 12:30:15 GMT
    <
    VEEAM-WAN
    * Connection #0 to host 192.168.220.71 left intact
    * Closing connection #0