From owner-freebsd-stable@freebsd.org Sat Feb 6 00:45:43 2016 Return-Path: Delivered-To: freebsd-stable@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 C255FA9E5C0 for ; Sat, 6 Feb 2016 00:45:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (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 8EA991D31 for ; Sat, 6 Feb 2016 00:45:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-ig0-x22e.google.com with SMTP id 5so25503373igt.0 for ; Fri, 05 Feb 2016 16:45:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=M6s/D1/r7uJ2Rc5b3hFK8/N5lkH+TWRI+3jIW+N0SYo=; b=yFvHL3UmqKhYzz5cUAsqRZp9BQL5EdecGhB2ubUjdKhSBJ5if3ra2IGh6nxZYlVGlP 77JMnFbninHjTqur3dUXg67hu7047PPTup2Tx9mw1vwg8FJp51Xs0RKJE6Z8x69kai8C w7ez+U/iiI4Mv0cZ6N81qDkNDgN24b1QnZfu0ZZpecorBtlXD9xpwHYXP4yUDr7FEbCB P/Evo/EUs2mgHn9PqwBHLSmddNVS9KPPIVZNQSUcwsInE9elLpUqhp6xceKZfKXSJ/fW Rs0ECC3k2Pxv7owcjQ+GP3DsbjYc55thyNYQmLRjwcy0aQTTyRRI7NZjOBT0ighXVtWA 7+VA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=M6s/D1/r7uJ2Rc5b3hFK8/N5lkH+TWRI+3jIW+N0SYo=; b=chcbNXGsDCTaQ/3/cgZ2pDU0WkzuDUJ9J6a1IFfwSAcRr7PbAPREZo0wuLaxPjEAXp eRaiQ/M8ds3UOANjRjtDO3UQ09LKnp9B4/jpe19QAziNIKAjnpWiIg1be80ENc3+Uexp EdG107EvM2EcWbhxK3/pu1qKn8xtajY3ajiB1abdw7s74rNuyIdFH5PHdIn5ItYTro3B 54mTUy3j4SM7OdCbtHwpww0qE06pCfnlLrS+szFCk9WRO4cwm6TOhjOyIN8POSqxZDzW 8xbwKIbO0WWQ1HH7amvP0CGgLhvbxhHdSpopTKC29DiLxcK/9e1b532jMaNaSE6pME5x umkQ== X-Gm-Message-State: AG10YOQFTm65KhIt9G0n+WoC7RO1uHlzGgwStK0Ok698pRo7M+JCNp1ExY52It3NE6MU8/y3KGNVjaFqpsPBQA== MIME-Version: 1.0 X-Received: by 10.50.93.36 with SMTP id cr4mr17465721igb.22.1454719543045; Fri, 05 Feb 2016 16:45:43 -0800 (PST) Received: by 10.36.14.19 with HTTP; Fri, 5 Feb 2016 16:45:42 -0800 (PST) In-Reply-To: References: Date: Fri, 5 Feb 2016 16:45:42 -0800 Message-ID: Subject: Re: 10.2 Release seems to be crashing on Azure with "Standard DS" VM sizes From: Adrian Chadd To: Scott Otis Cc: "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Feb 2016 00:45:43 -0000 hiya, how much RAM does the VM have? Yes, you need to either run dumpon or reboot once you update /etc/rc.conf . -a On 5 February 2016 at 13:55, Scott Otis wrote: > Been trying to get a FreeBSD VM server running on Azure on a "Standard DS= " size VM (so I have access to SSD storage for PostgreSQL). The "Standard = DS" series of VMs also have faster/newer CPUs than the original "Standard A= " series of VMs. I am using the image of FreeBSD from here: https://vmdepo= t.msopentech.com/Vhd/Show?vhdId=3D56718&version=3D61117 . After setting up= the VM it started rebooting every hour or so. Initially I thought this wa= s an Azure issue and Azure was forcibly rebooting the VM because it wasn't = getting health reports back. But I don't' believe this is the case anymore= and I think FreeBSD is crashing. (Note: I have setup a FreeBSD VM with a = "Standard A" series VM and that seems to be running fine - though it looks = like it might have crashed after about 38 hours which is much better than c= rashing after 1 hour). > > Here is the "last" log from the last two days: > > [--redacted--] pts/2 [--redacted--] Fri Feb 5 21:10 still logged = in > [--redacted--] pts/1 [--redacted--] Fri Feb 5 21:10 still logged = in > [--redacted--] pts/0 [--redacted--] Fri Feb 5 20:58 - 21:10 (00:12= ) > boot time Fri Feb 5 20:53 > [--redacted--] pts/1 [--redacted--] Fri Feb 5 04:59 - crash (15:54= ) > [--redacted--] pts/0 [--redacted--] Fri Feb 5 04:59 - 04:59 (00:00= ) > boot time Fri Feb 5 04:41 > boot time Fri Feb 5 02:16 > [--redacted--] pts/1 [--redacted--] Fri Feb 5 00:36 - crash (01:40= ) > [--redacted--] pts/0 [--redacted--] Fri Feb 5 00:36 - 00:36 (00:00= ) > boot time Fri Feb 5 00:29 > shutdown time Thu Feb 4 09:33 > boot time Thu Feb 4 08:47 > [--redacted--] pts/0 [--redacted--] Thu Feb 4 07:25 - crash (01:21= ) > boot time Thu Feb 4 07:00 > boot time Thu Feb 4 05:03 > boot time Thu Feb 4 02:45 > [--redacted--] pts/0 [--redacted--] Thu Feb 4 01:08 - crash (01:36= ) > boot time Thu Feb 4 00:58 > > There are boot times without previous shutdown times - and there is that = "crash" text (which is why I'm thinking it is a crash). > > It looks by default the OS is setup to NOT save crash dumps > > > sudo dumpon -v -l > > kernel dumps on /dev/null > > > If that is the case - do I add this to /etc/rc.conf? > > > > dumpdev=3D"AUTO" > > dumpdir=3D"/var/crash" > > > > Is there anything I need to adjust there? > > Does that only take affect after a reboot? > > Do I need to set anything with dumpon(8)? > > > > Here is the info on the swapfile: > > > > sudo swapinfo -h > > Device 512-blocks Used Avail Capacity > > /dev/gpt/swapfs 2097152 0B 1.0G 0% > > > > Is that enough space for a kernel crash dump? > > > > Thanks for all your help with this. > > Regards, > > Scott Otis > CTO & Co-Founder > Tandem > www.tandemcal.com > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"