You are viewing a plain text version of this content. The canonical link for it is here.

Posted to infrastructure-issues@apache.org by "Daniel Gruno (JIRA)" <ji...@apache.org> on 2014/12/16 21:30:13 UTC

[jira] [Commented] (INFRA-8885) bloodhound-vm2 unaccessible

    [ https://issues.apache.org/jira/browse/INFRA-8885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248859#comment-14248859 ] 

Daniel Gruno commented on INFRA-8885:
-------------------------------------

I'll try a soft reset, and if that doesn't work, I'll bounce the VM.

> bloodhound-vm2 unaccessible
> ---------------------------
>
>                 Key: INFRA-8885
>                 URL: https://issues.apache.org/jira/browse/INFRA-8885
>             Project: Infrastructure
>          Issue Type: Bug
>         Environment: Ubuntu vm bloodhound-vm2.apache.org
>            Reporter: Gary Martin
>            Assignee: Daniel Gruno
>
> Would it be possible to reboot bloodhound-vm2.apache.org?
> It seems that this VM has become seriously messed up as I appear to lack the ability to ssh into it to attempt fix problems
> It the medium term I am tempted to request the creation of a new similarly specced VM so we can migrate the service bloodhound-vm2 provides so that we can then decommision it. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)