Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
Sender Email:
-
HD-Chapter:Apps
-
HD-Enabler:Wirecloud
Description
Good morning,
We are a team participating in the Fiware Accelerator Programme more
specific the SmartAgriFood with the project FRESH (ID:15443).
At the moment we are trying to connect to a new instance of the Orion
Context Broker on the Fiware Cloud Platform but we can't, it gives us a
Unified Error 503 (see screenshot below) when trying to assign the IP to
the Orion instance (region Spain).
[image: Inline image 2]
[image: Inline image 1]
And when trying to connect via shh it can't find the server.
We are creating this Orion instance since we have one local in our own
servers but we can't receive notifications, for instance on
ContextUpdate, from
the global Wirecloud GE Mashup in the Fiware Lab. What is happening is that
we can create subscriptions from the Wirecloud Global Instance to our Orion
instance (in our local servers) but after the Wirecloud don't receive any
notifications from Orion. We tested with the Orion Global instance and
everything went like expected, and for debugging purposes we want to test
with a instance in the Fiware Lab.
You can see in the print screen below the communication between the Orion
local instance and the Wirecloud global instance.
[image: Inline image 2]
Thanks in advance,
Os melhores cumprimentos / Best Regards / Gruss
André Silva
Research Engineer
[image: Introsys SA] <http://www.introsys.eu/>Parkim – Parque Industrial da
Moita
Rua dos Girassóis | Nº1 Armazém A3 | 2860-274 Moita – Portugal
GPS: N 38º 38' 50'' W 8º 59' 58''
tel (+351) 212 951 499 | mobile (+351) 919 664 715
fax (+351) 212 893 000
website <http://www.introsys.eu/> | map
<http://www.bing.com/maps/?cp=38.647538~-8.999340&sty=h&lvl=18&rtp=~pos.38.647581_-8.999688__&mm_embed=dir>
| email[image: Facebook] <https://www.facebook.com/pages/Introsys-SA/169156139792189> [image: Youtube] <http://www.youtube.com/introsysSA> [image: Vimeo] <http://vimeo.com/introsys> [image: Google +] <https://plus.google.com/113392896599136312985> [image: Introbot] <http://introbot.pt/>*Confidentiality Note: *This e-mail and any attachments are confidential and may be protected by legal privilege. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this e-mail in error, please notify us immediately by returning it to the sender and delete this copy from your system. Thank you. |
_______________________________________________
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: =?UTF-8?B?QW5kcsOpIFNpbHZh?= <andre.silva@introsys.eu>]
Activity
Seems a platform problem with floating IP allocation
Hi André,
sorry for the delay on the response, the ticket was redirected to the wrong contact person and I have not heard about this until today.
I don't know if you fixed the problem, but the solution is installing rush into the context broker instance. Take a look into this [answer in stackoverflow](http://stackoverflow.com/a/32180653/2255503) for more info. Please upvote this answer if you find it useful.
Best regards,
Álvaro
Renamed attached file: 'Screenshot from 2015-06-09 11:47:06.png' to 'Screenshot from 2015-06-09 11_47_06.png' because it contained invalid character(s).