Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
Sender Email:
-
HD-Node:Budapest
Description
Dear Sirs,
Info: Connected to project DusanKrsticNS cloud (ID 88cc2d55126f4865b91c2cae47078832)
12 hours ago, I started function to making instance snapshot on 4 instances on Fiware Cloud Lab . Almost immediately server was created two snapshots the instances:
Name: dataServer-1
ID: f2caa0e3-5c88-4d33-b123-186b81822be1
Name: vpn
ID: 8d49c197-986d-4a21-9ea5-5ff9dc9fdca6
RAM: 8192MB
VCPUs: 4 VCPU
Disk: 80GB
RAM: 512MB
VCPUs: 1 VCPU
Disk: 1GB
but on this instances, tasks are still image_pending
Name: appServer
ID: 4de3bf0e-32e2-4558-ba51-3c3a0deabb8e
Name: sensorServer
ID: a0fecd22-35e9-4fa1-aee8-172a382ff09c
RAM: 4096MB
VCPUs: 2 VCPU
Disk: 40GB
RAM: 4096MB
VCPUs: 2 VCPU
Disk: 40GB
Can you provide more information, when the servers will work again?
Sincerely,
Dusan Krstic
Warning:This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
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
[Created via e-mail received from: =?UTF-8?B?RHVzYW4gS3JzdGlj?= <dusan.krstic@beemonsolution.com>]
Activity
Renamed attached file: 'Screenshot_from_2015-12-07_14:03:16.png' to 'Screenshot_from_2015-12-07_14_03_16.png' because it contained invalid character(s).
Dear Dusan,
we found also that your VMs in 'NOSTATE' task. So we restarted your VM, and now you can connect to it. Please try it again, and please check you snapshots (maybe you need to create new snapshots) and write us that everythings fine or something is wrong.
Sorry for the inconvenience,
Gergő
Dear Gergő,
Three of the four servers work, but for sensorServer I got error for reboot
Error rebooting instance sensorServer. Cause: 409 Error
{"conflictingRequest": {"message": "Cannot 'reboot' while instance is in vm_state stopped", "code": 409}}
How can I sensorServer instance, start again?
Best regards,
Dusan
Dusan Krstic
Warning:This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
Dear Dusan,
i started it. Now it's working. If everything is fine, i will close this ticket.
Gergő
Dear Gergő, thanks a lot 
Dusan Krstic
Warning:This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
Renamed attached file: 'Screenshot from 2015-12-03 07:47:26.png' to 'Screenshot from 2015-12-03 07_47_26.png' because it contained invalid character(s).