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

[fiware-stackoverflow] Configuring a VM with contextBroker and IoTAgent

    Details

      Description

      Created question in FIWARE Q/A platform on 01-12-2015 at 12:12
      Please, ANSWER this question AT https://stackoverflow.com/questions/34019348/configuring-a-vm-with-contextbroker-and-iotagent

      Question:
      Configuring a VM with contextBroker and IoTAgent

      Description:
      I am experimenting with fiware and I would like to setup a VM with those 2 compoments in order to have an environment to be used with IoT devices.
      I have been able (let me say with a great effort) to create a VM with the two components installed, by using the base contextBroker instance and building IoTAgent from source and then installing the generated RPMs. ContextBroker seems to work fine, because I can query for entities and I get 200 status as response, but if I try to create a service in IoTA I get no response, so I guess there is something wrong with the configuration.
      I'll list all the steps I have performed so troubleshooting can be easier:

      Deployed the VM in fiware Lab Cloud (orion-psb-image-R4.4)
      Opened ports in the security group
      Associated a floating IP to the VM
      Built IoTAgent
      Generated and installed RPMs packages
      Set PATH and LD_LIBRARY_PATH in .bashrc to start iotagent properly
      Created the configuration file "config.json" in /etc/iot as described on GitHub (I used the example one)
      Started iotagent as a service with the command sudo service iotagent start protocol
      Used the figway scripts to create a service, but the script hangs

      Does iotagent_protocol.conf file in /usr/local/iot/config need any particular configuration as well or is there in general something I am missing or that I could check? Also, if I check the log in /tmp I can see this message: OAuth for northbound is not configured. Is authentication needed? In GitHub README the example configuration file has no authentication.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        2h 54m 1 Backlog Manager 22/May/17 6:10 PM
        In Progress In Progress Closed Closed
        3h 1 Backlog Manager 22/May/17 9:10 PM

          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: