From owner-freebsd-questions@freebsd.org Mon Jul 6 16:58:54 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B7BDAF1A for ; Mon, 6 Jul 2015 16:58:54 +0000 (UTC) (envelope-from jd1008@gmail.com) Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4509B150F for ; Mon, 6 Jul 2015 16:58:54 +0000 (UTC) (envelope-from jd1008@gmail.com) Received: by igh16 with SMTP id 16so30257544igh.0 for ; Mon, 06 Jul 2015 09:58:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=JKU/xOz1bHR1vCogddZM+ct4vDNjC4d7iJ13G53r0A8=; b=N3xx+lX8LM6+NNRzZsfpZrdTV37AYHQXPzNuTZOxqCNX/vYkmawhueXpFTcdRZ1nmS gRgsrbYhXYF1sHR50AqvsdQ5grxlRg8zw+oIvZdtysoZFmx712/rv02+XnaRKFWNMgOM 3H9R7YqXxjl4shzTw3y9ZfEPIwm/yBc68qTmUDu5P1lxeDABEeHbwC2uPvMF7MyhSsgd ZX6eIVg2HAfN2oQVZ0RUmEQ+kuj/FI+DtdyH4NkbZp0k1HTyhKNAcGVFSztpKxPXtO61 W8Wq/h70R7FZ2qMlY5fZCHj76LrAnsQuxz4j8CwjbzN1Rr4vCBH+KikXwCxC/jHjCGnq Cp2Q== X-Received: by 10.107.169.16 with SMTP id s16mr72295825ioe.74.1436201933621; Mon, 06 Jul 2015 09:58:53 -0700 (PDT) Received: from localhost.localdomain ([50.243.6.59]) by mx.google.com with ESMTPSA id v40sm3495942ioi.37.2015.07.06.09.58.52 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Jul 2015 09:58:52 -0700 (PDT) Message-ID: <559AB3CB.3010703@gmail.com> Date: Mon, 06 Jul 2015 10:58:51 -0600 From: jd1008 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: best way to debug kernel panic on remote machine References: <559AA88E.3080407@gmx.com> In-Reply-To: <559AA88E.3080407@gmx.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jul 2015 16:58:54 -0000 On 07/06/2015 10:10 AM, Nikos Vassiliadis wrote: > Hi, > > I have a system on a hosting provider and it panics. Any ideas how > to debug this without asking the provider to install serial cables? > I am thinking of reproducing the panic locally but there might be > an easier way. > > Thanks in advance, > Nikos > _______ Hi Nikos. Been there done that. Only way to debug a kernel panic on a remote machine is to first make sure that the remote machine's kernel is built to save the coredump and the krenel file copy into a crashdump directory. In addition, it would also require that the kernel be built with full debug enabled, and it symbols NOT STRIPPED!!! This way, the crashdump analyzer program will be able to show you the source lines of code.