From owner-freebsd-stable@freebsd.org Fri Feb 5 21:55:18 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 092EEA9EEE3 for ; Fri, 5 Feb 2016 21:55:18 +0000 (UTC) (envelope-from scott.otis@tandemcal.com) Received: from Filter01.GreenHouseData.com (outmail.fchosted.com [205.234.75.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "filter.greenhousedata.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E07E265A for ; Fri, 5 Feb 2016 21:55:17 +0000 (UTC) (envelope-from scott.otis@tandemcal.com) X-ASG-Debug-ID: 1454709316-0a955c0aa817e7590001-BIHDGU Received: from mail.fchosted.com (mailflow.greenhousedata.com [10.36.251.68]) by Filter01.GreenHouseData.com with ESMTP id DHmjcQnMm3pLRGpm (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 05 Feb 2016 13:55:16 -0800 (PST) X-Barracuda-Envelope-From: scott.otis@tandemcal.com Received: from EVT01FEVWEXA001.fchosted.com ([10.10.2.130]) by sea02fevwexa001 ([10.10.2.131]) with mapi id 14.03.0266.001; Fri, 5 Feb 2016 13:55:16 -0800 From: Scott Otis To: "freebsd-stable@freebsd.org" Subject: 10.2 Release seems to be crashing on Azure with "Standard DS" VM sizes Thread-Topic: 10.2 Release seems to be crashing on Azure with "Standard DS" VM sizes X-ASG-Orig-Subj: 10.2 Release seems to be crashing on Azure with "Standard DS" VM sizes Thread-Index: AdFgXh+MGR2ZakJhS8y7lHqrkKi5uw== Date: Fri, 5 Feb 2016 21:55:15 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [24.19.233.47] MIME-Version: 1.0 X-Barracuda-Connect: mailflow.greenhousedata.com[10.36.251.68] X-Barracuda-Start-Time: 1454709316 X-Barracuda-Encrypted: AES128-SHA X-Barracuda-URL: https://Filter.GreenHouseData.com:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 12891 X-Virus-Scanned: by bsmtpd at GreenHouseData.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=HTML_MESSAGE X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.26781 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 HTML_MESSAGE BODY: HTML included in message Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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: Fri, 05 Feb 2016 21:55:18 -0000 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://vmdepot.= msopentech.com/Vhd/Show?vhdId=3D56718&version=3D61117 . After setting up t= he VM it started rebooting every hour or so. Initially I thought this was = an Azure issue and Azure was forcibly rebooting the VM because it wasn't ge= tting health reports back. But I don't' believe this is the case anymore a= nd I think FreeBSD is crashing. (Note: I have setup a FreeBSD VM with a "S= tandard A" series VM and that seems to be running fine - though it looks li= ke it might have crashed after about 38 hours which is much better than cra= shing 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 "c= rash" 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