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

[Fiware-tech-help] FIWARE Tour Guide Application / Raspberry Pi Implementation

    Details

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

      Description

      Good afternoon,

      I'm having some problems implementing the following tutorial:
      http://fiwaretourguide.readthedocs.io/en/latest/fiware-tour-guide-application-a-tutorial-on-how-to-integrate-the-main-fiware-
      Ges / introduction /
      <http://fiwaretourguide.readthedocs.io/en/latest/fiware-tour-guide-application-a-tutorial-on-how-to-integrate-the-main-fiware-%20Ges%20/%20introduction%20/>

      I'm using Ubuntu 40.04 (LTS) for implementation.

      1º Issue: In the topic (Configuring security aspects), when I run the
      following command: sudo curl -X GET -H "Content-Type: application/json" -H
      "X-auth-token: ADMIN" "http://keyrock:5000/v3/OS-OAUTH2/consumers/"

      I have the following error: curl: (6) Could not resolve host: keyrock

      And I can not proceed to the next step.

      2º issue: In the topic (Running the front-end application), I do all the
      required steps and when I put the web page: http: // tourguide / client,
      it gives 404 error.

      3º issue: I would like to use FIWARE on a raspberry pi, but all the
      existing documentation online does not work or is incomplete, could you
      help me? Or give a functional example? I would like to read any kind of
      sensor (Ex: DHT22), see the data, update the data, etc.

      I am a beginner and I have a lot of difficulties using FIWARE.

      Thank you.

      __________________________________________________________________________________________

      You can get more information about our cookies and privacy policies on the following links:

      Fiware-tech-help mailing list
      Fiware-tech-help@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-tech-help

      [Created via e-mail received from: Whis Whis <c6ta02@gmail.com>]

      1. c1.png
        103 kB
      2. c2.png
        60 kB

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        38d 17h 33m 1 Jose Manuel Cantera 14/Mar/17 9:47 AM
        In Progress In Progress Answered Answered
        21d 2h 21m 1 Jose Manuel Cantera 04/Apr/17 1:08 PM
        Answered Answered Closed Closed
        9s 1 Jose Manuel Cantera 04/Apr/17 1:08 PM
        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        fla Fernando Lopez made changes -
        HD-Enabler Orion [ 10875 ]
        HD-Chapter Data [ 10838 ]
        jmcantera Jose Manuel Cantera made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        jmcantera Jose Manuel Cantera made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        jmcantera Jose Manuel Cantera made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        pablo.fernandez Pablo Fernandez Moniz made changes -
        Attachment c2.png [ 29498 ]
        Attachment c1.png [ 29499 ]
        Hide
        pablo.fernandez Pablo Fernandez Moniz added a comment - - edited

        It seems that there is a problem with your /etc/hosts file.

        First of all, you need to verify that all containers are running properly. If you type in your console the docker ps command, you should see something like:

        If not, you should start the tourguide application using ./tour-guide start to start all the containers or ./tour-guide start <container-name> to start a single container.

        Once you have checked that all containers are running and in order to access to a container using their alias you should modify your /etc/hosts file. You can add the recently created docker images to your /etc/hosts file using the ./tour-guide configure hosts -m command (root privileges needed). Your /etc/hosts file should looks like:


        With that, you should be able to use the alias for accessing to the containers.

        Please, provide feedback to know if this solve your issue

        Show
        pablo.fernandez Pablo Fernandez Moniz added a comment - - edited It seems that there is a problem with your /etc/hosts file. First of all, you need to verify that all containers are running properly. If you type in your console the docker ps command, you should see something like: If not, you should start the tourguide application using ./tour-guide start to start all the containers or ./tour-guide start <container-name> to start a single container. Once you have checked that all containers are running and in order to access to a container using their alias you should modify your /etc/hosts file. You can add the recently created docker images to your /etc/hosts file using the ./tour-guide configure hosts -m command (root privileges needed). Your /etc/hosts file should looks like: With that, you should be able to use the alias for accessing to the containers. Please, provide feedback to know if this solve your issue
        fla Fernando Lopez made changes -
        Assignee Jose Manuel Cantera [ jmcantera ]
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        fw.ext.user FW External User created issue -

          People

          • Assignee:
            jmcantera Jose Manuel Cantera
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: