Join the Community
and take part in the story

Error 404 message when connecting to the Proxy - install process - Centos 7


#1

I’m following the installation documentation for OpenIO on Centos7.
At the very end of the installation I’m supposed to be connected to the proxy :
"All done !
Now you have your 3 nodes ready for testing purpose, and the proxy is accessible at http://YOUR_SERVER_IP:6006 (port 6006 by default as mentioned in the puppet manifest (oioproxy_url) )"
but I’m receiving the following error message within my web browser :
{code}
{“status”:404,“message”:“No handler found”}
{code}

Here are some details :

  1. Netstat -l | grep ‘6006’
    {code}
    tcp 0 0 node1.home:6006 0.0.0.0:* LISTEN
    {code}

  2. gridinit_cmd status
    {code}
    KEY STATUS PID GROUP
    OPENIO-account-0 UP 657 OPENIO,account,account-0
    OPENIO-beanstalkd-0 UP 1933 OPENIO,beanstalkd,beanstalkd-0
    OPENIO-conscience-0 UP 1119 OPENIO,conscience,conscience-0
    OPENIO-conscienceagent-0 UP 658 OPENIO,conscienceagent,conscienceagent-0
    OPENIO-meta0-0 UP 11346 OPENIO,meta0,meta0-0
    OPENIO-meta1-0 UP 11358 OPENIO,meta1,meta1-0
    OPENIO-meta2-0 UP 11357 OPENIO,meta2,meta2-0
    OPENIO-oio-blob-indexer-0 UP 652 OPENIO,oio-blob-indexer,oio-blob-indexer-0
    OPENIO-oio-event-agent-0 UP 653 OPENIO,oio-event-agent,oio-event-agent-0
    OPENIO-oioproxy-0 UP 1120 OPENIO,oioproxy,oioproxy-0
    OPENIO-rawx-0 UP 890 OPENIO,rawx,rawx-0
    OPENIO-rdir-0 UP 1932 OPENIO,rdir,rdir-0
    OPENIO-redis-0 UP 2542 OPENIO,redis,redis-0
    OPENIO-redissentinel-0 UP 2541 OPENIO,redissentinel,redissentinel-0
    OPENIO-zookeeper-0 UP 648 OPENIO,zookeeper,zookeeper-0
    {code}

  3. openio --oio-ns OPENIO cluster list
    ±--------±------------------±--------------------------------±---------±------±-----±------+
    | Type | Id | Volume | Location | Slots | Up | Score |
    ±--------±------------------±--------------------------------±---------±------±-----±------+
    | rdir | 192.168.1.26:6010 | /var/lib/oio/sds/OPENIO/rdir-0 | node3 | n/a | True | 97 |
    | rdir | 192.168.1.25:6010 | /var/lib/oio/sds/OPENIO/rdir-0 | node2 | n/a | True | 98 |
    | rdir | 192.168.1.24:6010 | /var/lib/oio/sds/OPENIO/rdir-0 | node1 | n/a | True | 98 |
    | account | 192.168.1.26:6009 | n/a | node3 | n/a | True | 97 |
    | account | 192.168.1.25:6009 | n/a | node2 | n/a | True | 98 |
    | account | 192.168.1.24:6009 | n/a | node1 | n/a | True | 98 |
    | rawx | 192.168.1.26:6004 | /var/lib/oio/sds/OPENIO/rawx-0 | node3 | n/a | True | 96 |
    | rawx | 192.168.1.25:6004 | /var/lib/oio/sds/OPENIO/rawx-0 | node2 | n/a | True | 96 |
    | rawx | 192.168.1.24:6004 | /var/lib/oio/sds/OPENIO/rawx-0 | node1 | n/a | True | 96 |
    | meta2 | 192.168.1.26:6003 | /var/lib/oio/sds/OPENIO/meta2-0 | node3 | n/a | True | 96 |
    | meta2 | 192.168.1.25:6003 | /var/lib/oio/sds/OPENIO/meta2-0 | node2 | n/a | True | 96 |
    | meta2 | 192.168.1.24:6003 | /var/lib/oio/sds/OPENIO/meta2-0 | node1 | n/a | True | 96 |
    | meta1 | 192.168.1.26:6002 | /var/lib/oio/sds/OPENIO/meta1-0 | node3 | n/a | True | 96 |
    | meta1 | 192.168.1.25:6002 | /var/lib/oio/sds/OPENIO/meta1-0 | node2 | n/a | True | 96 |
    | meta1 | 192.168.1.24:6002 | /var/lib/oio/sds/OPENIO/meta1-0 | node1 | n/a | True | 96 |
    | meta0 | 192.168.1.26:6001 | /var/lib/oio/sds/OPENIO/meta0-0 | node3 | n/a | True | 98 |
    | meta0 | 192.168.1.25:6001 | /var/lib/oio/sds/OPENIO/meta0-0 | node2 | n/a | True | 99 |
    | meta0 | 192.168.1.24:6001 | /var/lib/oio/sds/OPENIO/meta0-0 | node1 | n/a | True | 99 |
    ±--------±------------------±--------------------------------±---------±------±-----±------+

Any idea?


#2

someone said in other posts this is for commercial edition.


#3

Hello @RedLeu,

The role of oio-proxy has been explained here.

It has nothing to do with the commercial edition. There is no HTTP API to interact with OpenIO SDS directly. This is why we provide SDKs and connectors (e.g. Swift/S3) that will give you the APIs to store your objects.


#4

Thanks Vladimir
Ok,
So this 404, No Handler found is normal. To properly test it is requested to use SDKs and Connectors like Swift/S3.
Fine.
The install documentation is unclear.
br