>From FIWARE JIRA - Main Help Desk ---- ------------------------------------------------------------------------------- Comments: FW External User - Today 6:33 PM ------------------ Comment by lumetti.consultant at gmail.com : Hello, Yesterday afternoon the VMs has worked correctly and today we haven't any problem. Thanks and regards Fabiano Lumetti Il 27/06/2016 11:05, Help-Desk ha scritto: > We've experienced a problem with some of our hosts. We've worked it around the problem to make things work properly and we have opened an issue with the hardware provider so we can solve the issue for good. > > Sorry for the inconveniences, > > BR, > José Ignacio. > > ------------------------------------------------------------------------------- > José Ignacio Carretero Guarde created HELP-6832: > --------------------------------------------------- > > Summary: [Fiware-lab-help] Fwd: [FInish-Technology] INTOFOOD PROJECT - URGENT!!! Virtual Machine unreachable ... AGAIN! > Key: HELP-6832 > URL: https://jira.fiware.org/browse/HELP-6832 > Project: Help-Desk > Issue Type: extRequest > Components: FIWARE-LAB-HELP > Reporter: FW External User > Assignee: José Ignacio Carretero Guarde > > > *//*Dear Peter, > > Yesterday our VMs on fiwarelab were unreachable and today the situation > isn't changed. > > We have tried to reboot VM but the problem remain. > > One week ago we had the same problem (on saturday, sunday and monday 20 > of june) and after many tentative and many hours of works and test, > after reboot of VM from a snapshoot we have resolved the problem (in > that case we had a recently snapshot and we haven't lost production data) > > Now the VM is unreachable and we have no posssibilty to restart from a > snapshoot because we have production data on VM that we could loose in > that case. > > Could you take in care the problem and made up a resolution? > > Our account is base on lumetti.consultant at gmail.com address > > Our VMs is on Spain2 node > > We access using 1 pubblic ip and access to VM named Nuvolau > > IntoFoodDraft02BI-*nuvolau*-1-a2e3f9 192.168.226.230, 130.206.119.74 > 2048 MB RAM | 1 VCPU | 20GB Disk nuvolau ACTIVE None RUNNING > averau2 192.168.227.131 2048 MB RAM | 1 VCPU | 20GB Disk averau2 > ACTIVE None RUNNING > conturines 192.168.228.188 2048 MB RAM | 1 VCPU | 20GB Disk > conturines SHUTOFF None SHUTDOWN > lagazuoi 192.168.227.121 2048 MB RAM | 1 VCPU | 20GB Disk > lagazuoi ACTIVE None RUNNING > larsec 192.168.248.176 2048 MB RAM | 1 VCPU | 20GB Disk larsec > ACTIVE None RUNNING > > Thanks and Regards > > Fabiano Lumetti > > > -------- Messaggio Inoltrato -------- > Oggetto: [FInish-Technology] INTOFOOD PROJECT - URGENT!!! Virtual > Machine unreachable ... AGAIN! > Data: Mon, 27 Jun 2016 07:53:07 +0200 > Mittente: Lumetti Consultant <lumetti.consultant at gmail.com> > A: Peter Einramhof <einramhof at atb-bremen.de>, fabiano.lumetti > <fabiano.lumetti at eostech.it> > CC: FInish-Technology at finish-project.eu > <FInish-Technology at finish-project.eu>, Massimo Garuti > <m.garuti at fondazionedemocenter.it>, Harald Sundmaeker > <sundmaeker at atb-bremen.de>, 'Mauro Aleotti' <mauro.aleotti at eostech.it>, > fabiano.lumetti at eostech.it > > > > Dear Peter, > > Yesterday our VMs on fiwarelab were unreachable and today the situation > isn't changed. > > We have tried to reboot VM but the problem remain. > > One week ago we had the same problem (on saturday, sunday and monday 20 > of june) and after many tentative and many hours of works and test, > after reboot of VM from a snapshoot we have resolved the problem (in > that case we had a recently snapshot and we haven't lost production data) > > Now the VM is unreachable and we have no posssibilty to restart from a > snapshoot because we have production data on VM that we could loose in > that case. > > Could you ask to support to resolve the problem? > > Thanks and Regards > > Fabiano Lumetti > > > > 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 at lists.fiware.org) instead of the old one. > José Ignacio Carretero Guarde - Yesterday 11:04 AM ------------------ The issue has been emailed: \\ - Time sent: *27/Jun/16 11:04 AM* - To: *lumetti.consultant at gmail.com* - with subject: *(HELP-6832) [Fiware-lab-help] Fwd: [FInish-Technology] INTOFOOD PROJECT - URGENT!!! Virtual Machine unreachable ... AGAIN! * \\ ---- We've experienced a problem with some of our hosts. We've worked it around the problem to make things work properly and we have opened an issue with the hardware provider so we can solve the issue for good. Sorry for the inconveniences, BR, José Ignacio. Daniele Santoro - Yesterday 10:08 AM ------------------ Dear, I've forwarded your request to the Spain2 support team. Best, Daniele ------------------------ Issue id: HELP-6832 Description: *//*Dear Peter, Yesterday our VMs on fiwarelab were unreachable and today the situation isn't changed. We have tried to reboot VM but the problem remain. One week ago we had the same problem (on saturday, sunday and monday 20 of june) and after many tentative and many hours of works and test, after reboot of VM from a snapshoot we have resolved the problem (in that case we had a recently snapshot and we haven't lost production data) Now the VM is unreachable and we have no posssibilty to restart from a snapshoot because we have production data on VM that we could loose in that case. Could you take in care the problem and made up a resolution? Our account is base on lumetti.consultant at gmail.com address Our VMs is on Spain2 node We access using 1 pubblic ip and access to VM named Nuvolau IntoFoodDraft02BI-*nuvolau*-1-a2e3f9 192.168.226.230, 130.206.119.74 2048 MB RAM | 1 VCPU | 20GB Disk nuvolau ACTIVE None RUNNING averau2 192.168.227.131 2048 MB RAM | 1 VCPU | 20GB Disk averau2 ACTIVE None RUNNING conturines 192.168.228.188 2048 MB RAM | 1 VCPU | 20GB Disk conturines SHUTOFF None SHUTDOWN lagazuoi 192.168.227.121 2048 MB RAM | 1 VCPU | 20GB Disk lagazuoi ACTIVE None RUNNING larsec 192.168.248.176 2048 MB RAM | 1 VCPU | 20GB Disk larsec ACTIVE None RUNNING Thanks and Regards Fabiano Lumetti -------- Messaggio Inoltrato -------- Oggetto: [FInish-Technology] INTOFOOD PROJECT - URGENT!!! Virtual Machine unreachable ... AGAIN! Data: Mon, 27 Jun 2016 07:53:07 +0200 Mittente: Lumetti Consultant <lumetti.consultant at gmail.com> A: Peter Einramhof <einramhof at atb-bremen.de>, fabiano.lumetti <fabiano.lumetti at eostech.it> CC: FInish-Technology at finish-project.eu <FInish-Technology at finish-project.eu>, Massimo Garuti <m.garuti at fondazionedemocenter.it>, Harald Sundmaeker <sundmaeker at atb-bremen.de>, 'Mauro Aleotti' <mauro.aleotti at eostech.it>, fabiano.lumetti at eostech.it Dear Peter, Yesterday our VMs on fiwarelab were unreachable and today the situation isn't changed. We have tried to reboot VM but the problem remain. One week ago we had the same problem (on saturday, sunday and monday 20 of june) and after many tentative and many hours of works and test, after reboot of VM from a snapshoot we have resolved the problem (in that case we had a recently snapshot and we haven't lost production data) Now the VM is unreachable and we have no posssibilty to restart from a snapshoot because we have production data on VM that we could loose in that case. Could you ask to support to resolve the problem? Thanks and Regards Fabiano Lumetti 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 at lists.fiware.org) instead of the old one. _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help at lists.fiware.org https://lists.fiware.org/listinfo/fiware-lab-help [Created via e-mail received from: Lumetti Consultant <lumetti.consultant at gmail.com>] FIWARE Chapter: FIWARE GEri: Status: Closed Resolution: Done --------------------- This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy