Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-8915

[fiware-stackoverflow] Fiware error on creating service and registration for a device

    Details

    • Type: Monitor
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:

      Description

      Created question in FIWARE Q/A platform on 12-02-2017 at 13:02
      Please, ANSWER this question AT https://stackoverflow.com/questions/42187427/fiware-error-on-creating-service-and-registration-for-a-device

      Question:
      Fiware error on creating service and registration for a device

      Description:
      i am a fiware user and i have created an iot agent on an ubuntu 14.04 empty vm and when i send a create service or a device registration request , i get an error. And i've made sure that the ports listen properly and i've also allowed tcp connection on the port 4061. and also get an error whenever i send the request .

      here's the create service request

      (curl H 'content-type: application/json' -H 'fiware-service: bla770' -H 'fiware-servicepath: /howtobla770' -X POST 'http://217.172.12.243:4061/iot/services' -d @ ) << EOF
      {
      "services": [

      { "apikey": "api70", "token": "token", "cbroker": "http://147.27.60.58:1026", "resource": "/iot/d", "entity_type": "thing" }

      ]
      }
      EOF

      and this is the error which i get .

      connect to 217.172.12.243 port 4061 failed: Connection timed out

      • Failed to connect to 217.172.12.243 port 4061: Connection timed out

      Although i have allowed the port 4061 through the firewall by the command
      sudo ufw allow 4061

      sudo ufw allow 4061

      So, what could be done to solve this error please ?

        Activity

        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        fla Fernando Lopez made changes -
        Assignee Backlog Manager [ backlogmanager ]
        fla Fernando Lopez made changes -
        HD-Enabler Orion [ 10875 ]
        Description
        Created question in FIWARE Q/A platform on 12-02-2017 at 13:02
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/42187427/fiware-error-on-creating-service-and-registration-for-a-device


        +Question:+
        Fiware error on creating service and registration for a device

        +Description:+
        i am a fiware user and i have created an iot agent on an ubuntu 14.04 empty vm and when i send a create service or a device registration request , i get an error. And i've made sure that the ports listen properly and i've also allowed tcp connection on the port 4061. and also get an error whenever i send the request .

        here's the create service request

        (curl -H 'content-type: application/json' -H 'fiware-service: bla770' -H 'fiware-servicepath: /howtobla770' -X POST 'http://217.172.12.243:4061/iot/services&#39; -d @- ) &lt;&lt; EOF
        {
            "services": [
                {
                    "apikey": "api70",
                    "token": "token",
                    "cbroker": "http://147.27.60.58:1026",
                    "resource": "/iot/d",
                    "entity_type": "thing"
                }
            ]
        }
        EOF


        and this is the error which i get .

        connect to 217.172.12.243 port 4061 failed: Connection timed out
        * Failed to connect to 217.172.12.243 port 4061: Connection timed out


        Although i have allowed the port 4061 through the firewall by the command
        sudo ufw allow 4061

        sudo ufw allow 4061


        So, what could be done to solve this error please ?
        Created question in FIWARE Q/A platform on 12-02-2017 at 13:02
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/42187427/fiware-error-on-creating-service-and-registration-for-a-device


        +Question:+
        Fiware error on creating service and registration for a device

        +Description:+
        i am a fiware user and i have created an iot agent on an ubuntu 14.04 empty vm and when i send a create service or a device registration request , i get an error. And i've made sure that the ports listen properly and i've also allowed tcp connection on the port 4061. and also get an error whenever i send the request .

        here's the create service request

        (curl -H 'content-type: application/json' -H 'fiware-service: bla770' -H 'fiware-servicepath: /howtobla770' -X POST 'http://217.172.12.243:4061/iot/services&#39; -d @- ) &lt;&lt; EOF
        {
            "services": [
                {
                    "apikey": "api70",
                    "token": "token",
                    "cbroker": "http://147.27.60.58:1026",
                    "resource": "/iot/d",
                    "entity_type": "thing"
                }
            ]
        }
        EOF


        and this is the error which i get .

        connect to 217.172.12.243 port 4061 failed: Connection timed out
        * Failed to connect to 217.172.12.243 port 4061: Connection timed out


        Although i have allowed the port 4061 through the firewall by the command
        sudo ufw allow 4061

        sudo ufw allow 4061


        So, what could be done to solve this error please ?
        backlogmanager Backlog Manager made changes -
        Resolution Done [ 10000 ]
        Status In Progress [ 3 ] Closed [ 6 ]
        backlogmanager Backlog Manager made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        backlogmanager Backlog Manager created issue -

          People

          • Assignee:
            backlogmanager Backlog Manager
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: