Something is wrong if that VM is running out of RAM. There must be a
memory leak or something. I guess we will have to figure that out somehow.
Dave
On 08/30/2017 12:49 PM, Kevin A. McGrail wrote:
Ran it out of memory it appears and we have no swap to gracefully
recover. Thoughts? Ask for more ram?
-------- Forwarded Message --------
Subject: [jira] [Updated] (INFRA-14986) sa-vm1.apache.org appears
offline.
Date: Wed, 30 Aug 2017 17:46:00 +0000 (UTC)
From: Daniel Takamori (JIRA) <j...@apache.org>
To: kmcgr...@apache.org
[
https://issues.apache.org/jira/browse/INFRA-14986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Takamori updated INFRA-14986:
------------------------------------
Status: Waiting for user (was: Waiting for Infra)
sa-vm1.apache.org appears offline.
----------------------------------
Key: INFRA-14986
URL: https://issues.apache.org/jira/browse/INFRA-14986
Project: Infrastructure
Issue Type: Project
Components: VM
Reporter: Kevin A. McGrail
Assignee: Daniel Takamori
Priority: Blocker
Our VM has been having problems for a few hours. SSH is non-responsive.
Not responding to pings but unsure if ICMP is blocked.
Notification Type: PROBLEM
Service: SSH
Host: SpamAssassin Project VM
Address: sa-vm1.apache.org
State: CRITICAL
Date/Time: Wed Aug 30 08:47:53 CDT 2017
Additional Info:
CRITICAL - Socket timeout
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
