Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
Sender Email:
-
HD-Enabler:Orion
Description
Thanks to Daniel Moran I could resolve the Rush installation problem I had,
but I still can't see the markers on the mapViewer widget. I have post a
new question here
http://stackoverflow.com/questions/27952485/mapviewer-widget-doesnt-show-map-markers
.
I hope you can help me, because everything seems to work properly, but I
don't know why that is not working.
Nohelia Merino
National University of Engineering
2015-01-12 6:24 GMT-05:00 DANIEL MORAN JIMENEZ <
daniel.moranjimenez@telefonica.com>:
> Hello Noelia,
>
> We have found the problem. You are working with the 0.14 version of
> Orion Context Broker, and it turns out some problems with Rush integration
> were fixed in later versions. We have downloaded the 0.17 version binaries
> to the “/root/tmp” folder of your machine, and tried with the following
> command (having both Rush listener and consumer running in the background):
>
> ./contextBroker -port 1026 -logDir /var/log/contextBroker -pidpath
> /var/log/contextBroker/contextBroker.pid -dbhost localhost -db orion -t
> 0-255 -rush localhost:5001 –fg
>
> With that configuration, everything seems to work like a charm.
>
> As Alvaro will be answering you in Stack Overflow, you should update
> your Context Broker version to the 0.17.0 version or later. Once with the
> new version, modify /etc/sysconfig/contextBroker to match the configuration
> above, and everything should work. You will notice that, during the tests,
> we commented out your database user and password in
> /etc/sysconfig/contextBroker, as we were not able to connect with Mongo
> using them (even with the mongo client). I also added the BROKER_EXTRA_OPS
> variable including the rush flag and increasing the log level.
>
> Talking about Rush, I also raised the log level to DEBUG to find the
> problems. You can change it in the /Rush-1.8.3/lib/configBase.js file (but
> I suggest you keep it until you are sure everything is working as expected).
>
> I have left the /root/tmp folder in your machine just in case you want
> to test the 0.17.0 version of the Context Broker before updating it.
>
> I hope this solves your problem.
>
> Best regards
> Daniel Moran
>
> De: Nohelia Merino <noheliams1@gmail.com>
> Fecha: lunes, 12 de enero de 2015, 10:04
> Para: Daniel Morán Jiménez <daniel.moranjimenez@telefonica.com>
> Asunto: Re: Help with Context Broker and Rush problem
>
> Thanks so much Daniel, this is the ip : 130.206.83.193
> And the pem is fiware2.pem which is attached.
>
> Best Regards.
>
> Nohelia Merino
> National University of Engineering
>
> 2015-01-12 3:58 GMT-05:00 DANIEL MORAN JIMENEZ <
> daniel.moranjimenez@telefonica.com>:
>
>> Hello Nohelia,
>>
>> I’m Daniel Moran, one of the developers of the Fiware Core team. In
>> order to help you with this problem, I would need to access the instance
>> you are using. Can you provide me with access details (PEM and IP)? Thanks
>>
>> Best regards,
>> Daniel Moran
>>
>> ------------------------------
>>
>> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
>> puede contener información privilegiada o confidencial y es para uso
>> exclusivo de la persona o entidad de destino. Si no es usted. el
>> destinatario indicado, queda notificado de que la lectura, utilización,
>> divulgación y/o copia sin autorización puede estar prohibida en virtud de
>> la legislación vigente. Si ha recibido este mensaje por error, le rogamos
>> que nos lo comunique inmediatamente por esta misma vía y proceda a su
>> destrucción.
>>
>> The information contained in this transmission is privileged and
>> confidential information intended only for the use of the individual or
>> entity named above. If the reader of this message is not the intended
>> recipient, you are hereby notified that any dissemination, distribution or
>> copying of this communication is strictly prohibited. If you have received
>> this transmission in error, do not read it. Please immediately reply to the
>> sender that you have received this communication in error and then delete
>> it.
>>
>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
>> destinatário, pode conter informação privilegiada ou confidencial e é para
>> uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o
>> destinatário indicado, fica notificado de que a leitura, utilização,
>> divulgação e/ou cópia sem autorização pode estar proibida em virtude da
>> legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos
>> o comunique imediatamente por esta mesma via e proceda a sua destruição
>>
>
>
> ------------------------------
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener información privilegiada o confidencial y es para uso
> exclusivo de la persona o entidad de destino. Si no es usted. el
> destinatario indicado, queda notificado de que la lectura, utilización,
> divulgación y/o copia sin autorización puede estar prohibida en virtud de
> la legislación vigente. Si ha recibido este mensaje por error, le rogamos
> que nos lo comunique inmediatamente por esta misma vía y proceda a su
> destrucción.
>
> The information contained in this transmission is privileged and
> confidential information intended only for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. If you have received
> this transmission in error, do not read it. Please immediately reply to the
> sender that you have received this communication in error and then delete
> it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário,
> pode conter informação privilegiada ou confidencial e é para uso exclusivo
> da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário
> indicado, fica notificado de que a leitura, utilização, divulgação e/ou
> cópia sem autorização pode estar proibida em virtude da legislação vigente.
> Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
> imediatamente por esta mesma via e proceda a sua destruição
>
_______________________________________________
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: Nohelia Merino <noheliams1@gmail.com>]
Issue Links
- is duplicated by
-
HELP-1934 FIWARE.Request.Lab.Re: Help with Context Broker and Rush problem.
- Closed
Dear Nohelia,
I’m seeing that yesterday someone of the support team answered your question on StackOverflow, asking you to provide the traces at the Consumer process.
So, about this issue, I guess you can get help by continuing the thread on StackOverflow.
Please, do not hesitate to contact us if you will experience any other problem.
Best regards
Marco
Da: fiware-lab-help-bounces@lists.fi-ware.org fiware-lab-help-bounces@lists.fi-ware.org Per conto di Nohelia Merino
Inviato: mercoledì 14 gennaio 2015 22:14
A: fiware-lab-help@lists.fi-ware.eu; Fiware-lab-help@lists.fi-ware.org
Oggetto: Re: [Fiware-lab-help] Help with Context Broker and Rush problem
Thanks to Daniel Moran I could resolve the Rush installation problem I had, but I still can't see the markers on the mapViewer widget. I have post a new question here http://stackoverflow.com/questions/27952485/mapviewer-widget-doesnt-show-map-markers .
I hope you can help me, because everything seems to work properly, but I don't know why that is not working.
Nohelia Merino
National University of Engineering
2015-01-12 6:24 GMT-05:00 DANIEL MORAN JIMENEZ <daniel.moranjimenez@telefonica.com<daniel.moranjimenez@telefonica.com>>:
Hello Noelia,
We have found the problem. You are working with the 0.14 version of Orion Context Broker, and it turns out some problems with Rush integration were fixed in later versions. We have downloaded the 0.17 version binaries to the “/root/tmp” folder of your machine, and tried with the following command (having both Rush listener and consumer running in the background):
./contextBroker -port 1026 -logDir /var/log/contextBroker -pidpath /var/log/contextBroker/contextBroker.pid -dbhost localhost -db orion -t 0-255 -rush localhost:5001 –fg
With that configuration, everything seems to work like a charm.
As Alvaro will be answering you in Stack Overflow, you should update your Context Broker version to the 0.17.0 version or later. Once with the new version, modify /etc/sysconfig/contextBroker to match the configuration above, and everything should work. You will notice that, during the tests, we commented out your database user and password in /etc/sysconfig/contextBroker, as we were not able to connect with Mongo using them (even with the mongo client). I also added the BROKER_EXTRA_OPS variable including the rush flag and increasing the log level.
Talking about Rush, I also raised the log level to DEBUG to find the problems. You can change it in the /Rush-1.8.3/lib/configBase.js file (but I suggest you keep it until you are sure everything is working as expected).
I have left the /root/tmp folder in your machine just in case you want to test the 0.17.0 version of the Context Broker before updating it.
I hope this solves your problem.
Best regards
Daniel Moran
De: Nohelia Merino <noheliams1@gmail.com<noheliams1@gmail.com>>
Fecha: lunes, 12 de enero de 2015, 10:04
Para: Daniel Morán Jiménez <daniel.moranjimenez@telefonica.com<daniel.moranjimenez@telefonica.com>>
Asunto: Re: Help with Context Broker and Rush problem
Thanks so much Daniel, this is the ip : 130.206.83.193
And the pem is fiware2.pem which is attached.
Best Regards.
Nohelia Merino
National University of Engineering
2015-01-12 3:58 GMT-05:00 DANIEL MORAN JIMENEZ <daniel.moranjimenez@telefonica.com<daniel.moranjimenez@telefonica.com>>:
Hello Nohelia,
I’m Daniel Moran, one of the developers of the Fiware Core team. In order to help you with this problem, I would need to access the instance you are using. Can you provide me with access details (PEM and IP)? Thanks
Best regards,
Daniel Moran