Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-4415

FIWARE.Request.Lab.PiraeusU.FIWARE Lab Assistance.

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-LAB-HELP
    • Labels:
      None

      Description

      Hi,
      I am facing various issues with the fiware cloud GE. I have installed
      the CentOS orion-psb-image-R4.2
      <https://cloud.lab.fiware.org/#nova/images/488f8701-8077-43e9-bef4-c0f852049fc7>,
      which contains the orion context broker and a mongoDB for persistent
      storage of data. On the same node I have deployed a tomcat application
      server. An external IP and a security policy were assigned.
      The overall framework was accessible and worked fine for more than a month.

      The first issues started when the instance changed from active state to
      suspended without any obvious reason. I tried to activate again the
      instance or reboot it and the result is that now is permanently on a
      rebooting state. Of course I can't access it through SSH and I have no
      access to mongoDB or to orion context broker.
      I deployed another instance with a similar configuration (CentOS, Orion
      context broker, mongo DB, Tomcat) that worked fine for a few hours. Now
      eventhough I see the instance through the cloud portal as "Active" I
      can't access it through SSH and Orion context broker is not accessible.

      Any help is more than welcome.

      Regards,
      Nikos.

      _______________________________________________
      Fiware-lab-help mailing list
      Fiware-lab-help@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-lab-help-new
      [Created via e-mail received from: Nikos Kalatzis <nikosk@mail.ntua.gr>]

        Activity

        Hide
        gcossu Giuseppe Cossu added a comment -

        Hello,
        In which node is deployed your VM?

        Regards,
        Giuseppe

        _______________________________________________
        Fiware-lab-help mailing list
        Fiware-lab-help@lists.fiware.org
        https://lists.fiware.org/listinfo/fiware-lab-help-new

        Show
        gcossu Giuseppe Cossu added a comment - Hello, In which node is deployed your VM? Regards, Giuseppe _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fiware.org https://lists.fiware.org/listinfo/fiware-lab-help-new
        Hide
        fermin Fermín Galán added a comment -

        After reading issue description, it doesn't seem to be related with Orion Context Broker itself, but with the cloud infrastructure where the VM runs. Thus, I'm assiging the issue to Backlog Manager, so he can reassign the issue to the right people.

        Show
        fermin Fermín Galán added a comment - After reading issue description, it doesn't seem to be related with Orion Context Broker itself, but with the cloud infrastructure where the VM runs. Thus, I'm assiging the issue to Backlog Manager, so he can reassign the issue to the right people.
        Hide
        fw.ext.user FW External User added a comment -

        Hi,
        the node I am working is PiraeusU. I also contact their support and they
        informed me about some service disrupts they had.
        Now it seems that the cloud instance is recovered but I am not sure if
        everything is fixed and stable.
        I am waiting for a confirmation.

        Thanks,
        Nikos

        Show
        fw.ext.user FW External User added a comment - Hi, the node I am working is PiraeusU. I also contact their support and they informed me about some service disrupts they had. Now it seems that the cloud instance is recovered but I am not sure if everything is fixed and stable. I am waiting for a confirmation. Thanks, Nikos
        Hide
        aalonsog Alvaro Alonso added a comment -

        I reassign the ticket to the specific node team.

        Show
        aalonsog Alvaro Alonso added a comment - I reassign the ticket to the specific node team.
        Hide
        UPRC PiraeusU Node Helpdesk added a comment -

        Dear user,

        we are working on your problem. Temporarily your instance may be in shutoff state, however we will bring it in the fully functional state asap. Of course we will inform you since the problem will be solved.

        Thank you for your understanding and sorry for the inconvenience.
        Best Regards,
        Dimitris

        Show
        UPRC PiraeusU Node Helpdesk added a comment - Dear user, we are working on your problem. Temporarily your instance may be in shutoff state, however we will bring it in the fully functional state asap. Of course we will inform you since the problem will be solved. Thank you for your understanding and sorry for the inconvenience. Best Regards, Dimitris
        Hide
        UPRC PiraeusU Node Helpdesk added a comment -

        Dear user,

        after some debugging on our node we managed to bring back in the proper functionality your VM.
        Please provide us your feedback in case everything is alright for your instance, so as to close this helpdesk ticket.

        Best Regards,
        Dimitris

        Show
        UPRC PiraeusU Node Helpdesk added a comment - Dear user, after some debugging on our node we managed to bring back in the proper functionality your VM. Please provide us your feedback in case everything is alright for your instance, so as to close this helpdesk ticket. Best Regards, Dimitris
        Hide
        UPRC PiraeusU Node Helpdesk added a comment -

        No response from user so far.
        Problem is considered as solved.
        Ticket closed.

        Show
        UPRC PiraeusU Node Helpdesk added a comment - No response from user so far. Problem is considered as solved. Ticket closed.

          People

          • Assignee:
            UPRC PiraeusU Node Helpdesk
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: