Solved.

> Hi,
> It is up and running again.
> Thank you.
>
> Regards,
> Marios Protogiros

Dear Marios,

could you please clarify if your service is running on a fi-lab VM or if it is a shelf hosted service in your premises?

Kind Regards,

—

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help

Hi Dimitris,

We have the service into FI-Lab in a VM. Also, in this VM we have build
with a docker (docker-compose) the IDAS and Orion Context Broker connected
to the same MongoDB.
Docker containers was running the last month without any problem (More
specifically from 02/10).
At first glance, we noticed that before 2 days, the connection of
containers with MongoDB had been lost.
We delete all containers, and we rerun them all again, and the problem
resolved.
The application now is in running state.
If we found any extra info for the problem we will info you.

The node is the PiraeusN and the IP (public 185.23.171.114 internal VM:
10.60.4.254)

Best Regards,

On Tue, Nov 3, 2015 at 3:43 PM, Dimitris Soukaras <dsoukaras@di.uoa.gr>

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help