[Fiware-demo] Some LiveDemo VMs unexpectedly restarted and required actions

Fermín Galán Márquez fermin at tid.es
Tue Oct 8 18:18:26 CEST 2013


Hi,

Due to an issue in the FI-PPP testbed this afternoon, some VMs machines have been unexpectedly restarted. The following VMs related with LiveDemo where affected:


| instance          | name                   | hostname                   | host      | fixed_ip       | floating_ip  | email                                  |
+-------------------+------------------------+----------------------------+-----------+----------------+--------------+----------------------------------------+
| instance-00000017 | fermin                 | contextbroker-livedemo     | fiwatse02 | 130.206.82.140 | 172.30.1.15  | fermin at tid.es<mailto:fermin at tid.es>                          |
| instance-00000019 | wirecloud              | historymod                 | fiwatse02 | 130.206.82.141 | 172.30.1.8   | aarranz at fi.upm.es<mailto:aarranz at fi.upm.es>                      |
| instance-00000097 | tanguy.bourgault       | locationserver-testbed     | fiwatse02 | 130.206.81.12  | 172.30.1.51  | tanguy.bourgault at thalesaleniaspace.com<mailto:tanguy.bourgault at thalesaleniaspace.com> |
| instance-000000de | fermin                 | cep                        | fiwatse02 | 130.206.81.31  | 172.30.1.78  | fermin at tid.es<mailto:fermin at tid.es>                          |
+-------------------+------------------------+----------------------------+-----------+----------------+--------------+----------------------------------------+


This is the current situation, along with pending recovery actions:

  *   The Context Broker and other processes running in orion.ld.testbed.fi-ware.eu have been restarted and seem to work ok.
  *   CEP instance running in cep.ld.testbed.fi-ware.eu seems to be work ok, so I understand that the CEP processes did a proper automatic restart upon reboot.
  *   In historymod (130.206.82.141) the process that capture information needs to be restarted. @UPM please do it asap. I restarted the event2issue process running in that VM.
  *   LOCS instance seems to be not working. I understand that it need a restarte. @Alain: could you please check this, please?

Thanks!

Best regards,

------
Fermín

________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-demo/attachments/20131008/e1dc4163/attachment.html>


More information about the Fiware-demo mailing list

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