Hello,

I did not receive any answer to this subject.
It is crucial to follow our implementation and we need support or feedback.

Thanks,

–

Confidentiality notice:
This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer.

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-tech-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-tech-help

The issue has been emailed:

• Time sent: 29/Mar/16 10:32 AM
• To: jose@secmotic.com
• Cc: *fernando.lopezaguilar@telefonica.com,joseignacio.carreteroguarde@telefonica.com ,henar.munozfrutos@telefonica.com *
• with subject: *(HELP-6210) [Fiware-tech-help] FIWARE LAB Instance shutdown and won't recover *
  

Dear José,

This seems to be a CentOS / Red Hat bug which happens after a kernel update. We are working to find out a solution to this problem.

However, we've realized that the virtualized disk is ok and there seem to be no sign of data loss.

Regards,
José Ignacio.

The issue has been emailed:

• Time sent: 29/Mar/16 1:56 PM
• To: jose@secmotic.com
• Cc: *fernando.lopezaguilar@telefonica.com,joseignacio.carreteroguarde@telefonica.com ,henar.munozfrutos@telefonica.com *
• with subject: *(HELP-6210) [Fiware-tech-help] FIWARE LAB Instance shutdown and won't recover *
  

I think you should be able to access you VM as usual.

Regards,
José Ignacio.

Hello everyone,

I was able to connect to the machine, but now while working, it has shut down suddenly and I can no longer connect via ssh.
In the FIWARE cloud, the status is active and running, and I can trace the whole route to the machine.

I would appreciate your help again.

Thanks in advance

–

Confidentiality notice:
This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer.

Both issues are not related. But this comment proves that this issue is ok now.

However, the new problem is that there seems to be a fiber cut which is being repaired at this time.

We've detected a fiber cut in part of our infrastructure and we are working to solve it.

Sorry for the inconveniences.

Regards,
José Ignacio.

El 31/03/16 a las 14:23, Jose Benítez escribió:
Hello everyone,

I was able to connect to the machine, but now while working, it has shut down suddenly and I can no longer connect via ssh.
In the FIWARE cloud, the status is active and running, and I can trace the whole route to the machine.

I would appreciate your help again.

Thanks in advance

–

[cid:part1.03000703.03020609@telefonica.com]
Confidentiality notice:
This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer.

El 29/3/2016, a las 13:57, Help-Desk <jira-help-desk@fi-ware.org<jira-help-desk@fi-ware.org>> escribió:

I think you should be able to access you VM as usual.

Regards,
José Ignacio.

-------------------------------------------------------------------------------
José Ignacio Carretero Guarde created HELP-6210:
---------------------------------------------------

Summary: [Fiware-tech-help] FIWARE LAB Instance shutdown and won't recover
Key: HELP-6210
URL: https://jira.fiware.org/browse/HELP-6210
Project: Help-Desk
Issue Type: extRequest
Components: FIWARE-LAB-HELP
Reporter: FW External User
Assignee: José Ignacio Carretero Guarde

Hello,

Today I detected that I couldn't connect to my instance (130.206.125.211). When I went to the FIWARE LAB dashboard, I detected that the status of the machine was "SHUTDOWN", so I tried to activate, I found the following logs, where it's said that the HDD cannot be mounted. Could you please provide me a solution?

Thanks in advance

[ 0.889343] usb 1-1: New USB device found, idVendor=0627, idProduct=0001
[ 0.892732] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=5
[ 0.895630] usb 1-1: Product: QEMU USB Tablet
[ 0.897705] usb 1-1: Manufacturer: QEMU
[ 0.898841] usb 1-1: SerialNumber: 42
[ 0.909173] input: QEMU QEMU USB Tablet as /devices/pci0000:00/0000:00:01.2/usb1/1-1/1-1:1.0/input/input2
[ 0.913578] hid-generic 0003:0627:0001.0001: input,hidraw0: USB HID v0.01 Pointer [QEMU QEMU USB Tablet] on usb-0000:00:01.2-1/input0
[ 1.284208] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3
[ 1.291135] md: Waiting for all devices to be available before autodetect
[ 1.293999] md: If you don't use raid, use raid=noautodetect
[ 1.295502] md: Autodetecting RAID arrays.
[ 1.296681] md: Scanned 0 and added 0 devices.
[ 1.297880] md: autorun ...
[ 1.298840] md: ... autorun DONE.
[ 1.299896] List of all partitions:
[ 1.301005] No filesystem could mount root, tried:
[ 1.302423] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 1.303418] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.10.0-327.4.5.el7.x86_64 #1
[ 1.303418] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.7.5-20150310_111955-batsu 04/01/2014
[ 1.303418] ffffffff8184e990 00000000a4b256f8 ffff88007c77fd60 ffffffff8163515c
[ 1.303418] ffff88007c77fde0 ffffffff8162e9d7 ffffffff00000010 ffff88007c77fdf0
[ 1.303418] ffff88007c77fd90 00000000a4b256f8 00000000a4b256f8 ffff88007c77fe00
[ 1.303418] Call Trace:
[ 1.303418] [] dump_stack+0x19/0x1b
[ 1.303418] [] panic+0xd8/0x1e7
[ 1.303418] [] mount_block_root+0x2a1/0x2b0
[ 1.303418] [] mount_root+0x53/0x56
[ 1.303418] [] prepare_namespace+0x13c/0x174
[ 1.303418] [] kernel_init_freeable+0x1f0/0x217
[ 1.303418] [] ? initcall_blacklist+0xb0/0xb0
[ 1.303418] [] ? rest_init+0x80/0x80
[ 1.303418] [] kernel_init+0xe/0xf0
[ 1.303418] [] ret_from_fork+0x58/0x90
[ 1.303418] [] ? rest_init+0x80/0x80

–

Confidentiality notice:
This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer.

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