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

FIWARE.Request.Lab.Spain.virtual machines periodically stop working after half an hour

        Details

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

          Description

          Dear all,

          We are trying to install the latest Orion Context Broker 0.22 on a CentOS
          6.5 instance with instance ID c29a54af-b0bc-4975-aea3-b0ee7fff1c14.

          After half an hour of usage time through ssh, the machine stops being
          reacheable and no further ssh connections are accepted (timeout error).
          Restarting the machine solved this issue before, but that trick does not
          work anymore.

          What can we do to keep virtual machines running and accesible?

          Best regards,
          Rafael M.

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

          [Created via e-mail received from: =?UTF-8?Q?Rafael_Mor=C3=B3n?= <rafaelmoron@gmail.com>]

            Activity

            Ascending order - Click to sort in descending order
            fw.ext.user FW External User created issue -
            mev Manuel Escriche made changes -
            Field Original Value New Value
            Component/s FIWARE-TECH-HELP [ 10278 ]
            mev Manuel Escriche made changes -
            Assignee Fermín Galán [ fermin ]
            Hide
            Permalink
            fermin Fermín Galán added a comment -

            It seems to be a connectivity error or some other infrastructure related problem. Thus, I'm assigning it to the cloud team.

            Show
            fermin Fermín Galán added a comment - It seems to be a connectivity error or some other infrastructure related problem. Thus, I'm assigning it to the cloud team.
            fermin Fermín Galán made changes -
            Assignee Fermín Galán [ fermin ] Fernando Lopez [ fla ]
            fla Fernando Lopez made changes -
            Assignee Fernando Lopez [ fla ] Henar Muñoz [ henar ]
            Hide
            Permalink
            henar Henar Muñoz added a comment -

            No enough information

            Show
            henar Henar Muñoz added a comment - No enough information
            henar Henar Muñoz made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            henar Henar Muñoz made changes -
            Status In Progress [ 3 ] Impeded [ 10004 ]
            Hide
            Permalink
            fw.ext.user FW External User added a comment -

            Account is contact(at)allinbyte.com

            Instance is now:

            Centos-6.5_instance2
            <https://cloud.lab.fiware.org/#nova/instances/5393306c-6d77-4171-b58d-6ef2180e9c48/detail>
            192.168.200.225
            130.206.121.169
            2048 MB RAM | 1 VCPU | 20GB Disk allinbyte_filab ACTIVE None RUNNING

            No matter how many times I restart the machine, create a new one or
            allocate any public IP to it, since last friday neither me nor my
            colleagues have access through ssh (no response at all, like when an ssh
            connection gets blocked by a firewall), and the security group should allow
            connection.

            CentOS machines seem also stuck when starting up in the VNC Display.

            Best regards.
            Rafael M.

            On Wed, Jun 3, 2015 at 4:40 PM, Help-Desk <jira-help-desk@fi-ware.org>

            Show
            fw.ext.user FW External User added a comment - Account is contact(at)allinbyte.com Instance is now: Centos-6.5_instance2 < https://cloud.lab.fiware.org/#nova/instances/5393306c-6d77-4171-b58d-6ef2180e9c48/detail > 192.168.200.225 130.206.121.169 2048 MB RAM | 1 VCPU | 20GB Disk allinbyte_filab ACTIVE None RUNNING No matter how many times I restart the machine, create a new one or allocate any public IP to it, since last friday neither me nor my colleagues have access through ssh (no response at all, like when an ssh connection gets blocked by a firewall), and the security group should allow connection. CentOS machines seem also stuck when starting up in the VNC Display. Best regards. Rafael M. On Wed, Jun 3, 2015 at 4:40 PM, Help-Desk <jira-help-desk@fi-ware.org>
            Hide
            Permalink
            fw.ext.user FW External User added a comment -

            Hi Henar,

            We can currently communicate with the VMs as well as to allocate the public
            IP address, whereas we only use enabler images for the VMs and wait for
            some time for the IP allocation to be effective.

            Nevertheless, we are unable to log in to ubuntu or CentOS 6.5 or CentOS 7
            machines we deploy. We are prompted for a password regardless of the
            certificate, and no message about the certificate is shown (as if
            certificate-based authentication is not enabled). Even adding some tested
            script fragment to create a separate regular sudoer does not seem to create
            a user + password pair which is accepted to log in:

            useradd -m <user>
            echo <user>:<pass> | chpasswd
            echo '<user> ALL=(ALL:ALL) ALL' >> /etc/sudoers

            The script works in the VMs based on enabler images for both CentOS and
            Ubuntu.

            Trying to log in in the Qemu results in the same desperating result: login
            failed.

            How can we use the base CentOS images to create a VM where we can log in?

            Best regards!
            Rafael M.

            On Thu, Jun 4, 2015 at 7:08 PM, Help-Desk <jira-help-desk@fi-ware.org>

            Show
            fw.ext.user FW External User added a comment - Hi Henar, We can currently communicate with the VMs as well as to allocate the public IP address, whereas we only use enabler images for the VMs and wait for some time for the IP allocation to be effective. Nevertheless, we are unable to log in to ubuntu or CentOS 6.5 or CentOS 7 machines we deploy. We are prompted for a password regardless of the certificate, and no message about the certificate is shown (as if certificate-based authentication is not enabled). Even adding some tested script fragment to create a separate regular sudoer does not seem to create a user + password pair which is accepted to log in: useradd -m <user> echo <user>:<pass> | chpasswd echo '<user> ALL=(ALL:ALL) ALL' >> /etc/sudoers The script works in the VMs based on enabler images for both CentOS and Ubuntu. Trying to log in in the Qemu results in the same desperating result: login failed. How can we use the base CentOS images to create a VM where we can log in? Best regards! Rafael M. On Thu, Jun 4, 2015 at 7:08 PM, Help-Desk <jira-help-desk@fi-ware.org>
            henar Henar Muñoz made changes -
            Status Impeded [ 10004 ] In Progress [ 3 ]
            henar Henar Muñoz made changes -
            Status In Progress [ 3 ] Answered [ 10104 ]
            Hide
            Permalink
            fw.ext.user FW External User added a comment -

            Hi Henar,

            Today, I created a new CentOS 6.5 as usual and login did work as expected.

            I've accessed with exactly the same commands and certificate permissions
            (600) my colleagues and me used the last 6 times but this time it worked!

            Thank you so much for your support!

            Best regards,
            Rafael M.

            On Fri, Jun 5, 2015 at 12:11 PM, Help-Desk <jira-help-desk@fi-ware.org>

            Show
            fw.ext.user FW External User added a comment - Hi Henar, Today, I created a new CentOS 6.5 as usual and login did work as expected. I've accessed with exactly the same commands and certificate permissions (600) my colleagues and me used the last 6 times but this time it worked! Thank you so much for your support! Best regards, Rafael M. On Fri, Jun 5, 2015 at 12:11 PM, Help-Desk <jira-help-desk@fi-ware.org>
            henar Henar Muñoz made changes -
            Resolution Done [ 10000 ]
            Status Answered [ 10104 ] Closed [ 6 ]
            backlogmanager Backlog Manager made changes -
            Summary [Fiware-lab-help] virtual machines periodically stop working after half an hour FIWARE.Request.Lab.virtual machines periodically stop working after half an hour
            mev Manuel Escriche made changes -
            Component/s FIWARE-TECH-HELP [ 10278 ]
            Component/s FIWARE-LAB-HELP [ 10279 ]
            mev Manuel Escriche made changes -
            Sender Email rafaelmoron@gmail.com
            mev Manuel Escriche made changes -
            HD-Node Spain [ 10846 ]
            backlogmanager Backlog Manager made changes -
            Summary FIWARE.Request.Lab.virtual machines periodically stop working after half an hour FIWARE.Request.Lab.Spain.virtual machines periodically stop working after half an hour
            fla Fernando Lopez made changes -
            Fix Version/s 2021 [ 12600 ]
            Transition Time In Source Status Execution Times Last Executer Last Execution Date
            Open Open In Progress In Progress
            		6d 1h 38m 1 Henar Muñoz 03/Jun/15 4:40 PM
            In Progress In Progress Impeded Impeded
            		7m 15s 1 Henar Muñoz 03/Jun/15 4:47 PM
            Impeded Impeded In Progress In Progress
            		1d 19h 23m 1 Henar Muñoz 05/Jun/15 12:10 PM
            In Progress In Progress Answered Answered
            		2s 1 Henar Muñoz 05/Jun/15 12:10 PM
            Answered Answered Closed Closed
            		3d 4h 33m 1 Henar Muñoz 08/Jun/15 4:44 PM

              People

              • Assignee:
                henar Henar Muñoz
                Reporter:
                fw.ext.user FW External User
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: