From owner-freebsd-questions@FreeBSD.ORG Mon Jan 6 10:11:45 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A1D5B3B5 for ; Mon, 6 Jan 2014 10:11:45 +0000 (UTC) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 287A819F9 for ; Mon, 6 Jan 2014 10:11:44 +0000 (UTC) Received: from [192.168.1.35] (host86-150-242-158.range86-150.btcentralplus.com [86.150.242.158]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id s06ABXK2041893 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 6 Jan 2014 10:11:36 GMT (envelope-from frank2@fjl.co.uk) Message-ID: <52CA8156.5070909@fjl.co.uk> Date: Mon, 06 Jan 2014 10:11:34 +0000 From: Frank Leonhardt User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jan 2014 10:11:45 -0000 On 06/01/2014 09:48, eras mus wrote: > After a few minutes the sever > console be pinged or ssh. In server console also the machine hungs unable > to enter root password in the prompt. If I do a power restart it is > restarting up again and I can ssh also login from the console, but after > few minutes it hungs no ssh and pinging from LAN machine not possible. How > to trouble shoot, Please shed some light on it. This sounds like a hardware problem. Do a proper RAM test if you can. If this is okay, look at disk problems and if these are okay it is probably a fault on the CPU or motherboard. If you are worried it is a problem with your FreeBSD configuration, start the machine from a LiveCD (or memory stick) and see if this is stable, although this will not show up problems with the disk so easily. Regards, Frank