From owner-freebsd-questions@FreeBSD.ORG  Sat Apr 11 15:54:49 2015
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 5B907194
 for <freebsd-questions@freebsd.org>; Sat, 11 Apr 2015 15:54:49 +0000 (UTC)
Received: from smtp2.hushmail.com (smtp2.hushmail.com [65.39.178.134])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.hushmail.com", Issuer "smtp.hushmail.com" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 3A27E382
 for <freebsd-questions@freebsd.org>; Sat, 11 Apr 2015 15:54:48 +0000 (UTC)
Received: from smtp2.hushmail.com (localhost [127.0.0.1])
 by smtp2.hushmail.com (Postfix) with SMTP id 4C4BAA0239
 for <freebsd-questions@freebsd.org>; Sat, 11 Apr 2015 15:19:46 +0000 (UTC)
Received: from smtp.hushmail.com (w5.hushmail.com [65.39.178.80])
 by smtp2.hushmail.com (Postfix) with ESMTP;
 Sat, 11 Apr 2015 15:19:45 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id B265FA01DE; Sat, 11 Apr 2015 15:19:45 +0000 (UTC)
MIME-Version: 1.0
Date: Sat, 11 Apr 2015 15:19:45 +0000
To: "Raimund Sacherer" <rs@logitravel.com>
Subject: Re: Initial request to server extremely slow after longer periods of
 inactivity
From: opendaddy@hushmail.com
In-Reply-To: <369199529.123430074.1428656504549.JavaMail.zimbra@logitravel.com>
References: <20150409034121.7D7C720395@smtp.hushmail.com>
 <CADqw_gL6b4fYyda9GzKt4BGv=d=sASttf4bp2_W+6JnuKQUCjg@mail.gmail.com>
 <20150409113928.EE31F401E4@smtp.hushmail.com>
 <CADqw_gK8-bxeNTYw4ATQnSM-w0iNBVWma83hMScdbsCwzEGxEw@mail.gmail.com>
 <20150409185801.1B1E9401E3@smtp.hushmail.com>
 <369199529.123430074.1428656504549.JavaMail.zimbra@logitravel.com> 
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20150411151945.B265FA01DE@smtp.hushmail.com>
Cc: freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Apr 2015 15:54:49 -0000

Hello,

On 10. april 2015 at 9:01 AM, "Raimund Sacherer" <rs@logitravel.com> wrote:
>
>Then what I would do in your case is open a few ssh sessions, run 
>top with cpu focus in one, top with IO focus in another and in a 
>third i would take a tcpdump written to a file. Maybe another 
>session with vmstat to check on pagin/pageout, etc. 
>
>Then I'd wait the appropriate amount of time and try a web 
>connection, if it takes long, I'l check the top's if there is 
>something going on (lot's of CPU, lot's of IO, pages etc.) and 
>check the tcpdump in wireshark to see if there are problematic DNS 
>queries which maybe are timing out, etc.

Wouldn't SSH sessions act as "continuous feedback loops" preventing the server from going unresponsive in the first place?

Also, how can I do stuff like `traceroute` or `mtr` knowing beforehand that the server is indeed unresponsive? Since it's only unresponsive on first requests, if I send a request to check, things will have returned to normal by the time I get to run those commands.

Thanks!

O.D.