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

FIWARE.Request.Tech.Data.OrionContextBroker.FIWAR.Tech.ssistance4

    Details

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

      Description

      Dear Fiware-Team,

      Iam experiencing huge issues with the context broker these days. after
      having it running and working for a few month i upgraded our account and
      was required to set it up again.

      this morning everything worked. now nothing works. same code, but
      "updateContext" and "queryContext" gives me an error:

      ---raise ConnectionError(err, request=request)
      ---requests.exceptions.ConnectionError: ('Connection aborted.',
      error(111, 'Connection refused'))

      i hope you can help us. the filab id is: "12245"

      thank you very much

      cheers florian


      Florian Eidner Technology Development, Phone: +49 173 88 121 55 Website:
      www.binee.co Email: florian@binee.co

      _______________________________________________
      Fiware-lab-help mailing list
      Fiware-lab-help@lists.fi-ware.org
      https://lists.fi-ware.org/listinfo/fiware-lab-help

      [Created via e-mail received from: Florian Eidner <florian@binee.co>]

        Activity

        Hide
        fermin Fermín Galán added a comment -

        Not sure yet if the issue is related with Orion or with networking or basic cloud infrastructure. The user has been contacted in order to know about it.

        Show
        fermin Fermín Galán added a comment - Not sure yet if the issue is related with Orion or with networking or basic cloud infrastructure. The user has been contacted in order to know about it.
        Hide
        fermin Fermín Galán added a comment -

        Seems to be an already known problem, documented in SOF. User has been redirected there (see email conversation below). Closing.

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

        Dear Florian,

        If Orion is up and running and answering request done in the same VM, then it could be the same problem described here:

        http://stackoverflow.com/questions/29254295/connecting-orion-context-broker-from-another-machine/29258908

        Best regards,

        ------
        Fermín

        El 29/05/2015 a las 20:14, Florian Eidner escribió:
        > Hello Fermin,
        >
        > Sorry for the delay, ive been on the train for hours.
        >
        > I have been able to acces the instance via ssh and its on the berlin2 node. The context Broker is up and running and answering if i adress it directly on the vm (via localhost:1026).
        >
        > The instance is "orion-cb", ip: 193.175.132.29.
        >
        > Let me know if you require more information.
        >
        > Thanks for your help,
        >
        > Cheers Flo
        >
        >
        > Am 29.05.2015 um 12:07 schrieb Fermín Galán Márquez:
        >> Dear,
        >>
        >> Regarding your question to fiware-lab-help:
        >>
        >> Iam experiencing huge issues with the context broker these days. after
        >> having it running and working for a few month i upgraded our account and
        >> was required to set it up again.
        >> this morning everything worked. now nothing works. same code, but
        >> "updateContext" and "queryContext" gives me an error:
        >> ---raise ConnectionError(err, request=request)
        >> ---requests.exceptions.ConnectionError: ('Connection aborted.',
        >> error(111, 'Connection refused'))
        >> i hope you can help us. the filab id is: "12245"
        >> thank you very much
        >> cheers florian
        >> –
        >>
        >> We would need more information in order to know if the problem is related with network or basic VM infrastructure or with the Orion process running in the VM.
        >>
        >> In particular, some questions to debug the issue:
        >>
        >> In which region is the VM running?
        >> What is the id/name of the VM?
        >> Are your able to access to the VM by SSH?
        >> Is the Orion process up and running in the VM (ps ax | grep contextBroker)?
        >>
        >> Once we know the answer to that questions, we can understand the problem better and provide more useful help (or ask new questions).
        >>
        >> Thanks!
        >>
        >> Best regards,
        >>
        >> ------
        >> Fermín

        Show
        fermin Fermín Galán added a comment - Seems to be an already known problem, documented in SOF. User has been redirected there (see email conversation below). Closing. ------------ Dear Florian, If Orion is up and running and answering request done in the same VM, then it could be the same problem described here: http://stackoverflow.com/questions/29254295/connecting-orion-context-broker-from-another-machine/29258908 Best regards, ------ Fermín El 29/05/2015 a las 20:14, Florian Eidner escribió: > Hello Fermin, > > Sorry for the delay, ive been on the train for hours. > > I have been able to acces the instance via ssh and its on the berlin2 node. The context Broker is up and running and answering if i adress it directly on the vm (via localhost:1026). > > The instance is "orion-cb", ip: 193.175.132.29. > > Let me know if you require more information. > > Thanks for your help, > > Cheers Flo > > > Am 29.05.2015 um 12:07 schrieb Fermín Galán Márquez: >> Dear, >> >> Regarding your question to fiware-lab-help: >> >> Iam experiencing huge issues with the context broker these days. after >> having it running and working for a few month i upgraded our account and >> was required to set it up again. >> this morning everything worked. now nothing works. same code, but >> "updateContext" and "queryContext" gives me an error: >> ---raise ConnectionError(err, request=request) >> ---requests.exceptions.ConnectionError: ('Connection aborted.', >> error(111, 'Connection refused')) >> i hope you can help us. the filab id is: "12245" >> thank you very much >> cheers florian >> – >> >> We would need more information in order to know if the problem is related with network or basic VM infrastructure or with the Orion process running in the VM. >> >> In particular, some questions to debug the issue: >> >> In which region is the VM running? >> What is the id/name of the VM? >> Are your able to access to the VM by SSH? >> Is the Orion process up and running in the VM (ps ax | grep contextBroker)? >> >> Once we know the answer to that questions, we can understand the problem better and provide more useful help (or ask new questions). >> >> Thanks! >> >> Best regards, >> >> ------ >> Fermín

          People

          • Assignee:
            fermin Fermín Galán
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: