From owner-freebsd-stable@FreeBSD.ORG Tue Mar 11 13:29:35 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1C6423D8 for ; Tue, 11 Mar 2014 13:29:35 +0000 (UTC) Received: from mail-ve0-x242.google.com (mail-ve0-x242.google.com [IPv6:2607:f8b0:400c:c01::242]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CE3CD674 for ; Tue, 11 Mar 2014 13:29:34 +0000 (UTC) Received: by mail-ve0-f194.google.com with SMTP id pa12so3199845veb.9 for ; Tue, 11 Mar 2014 06:29:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=wUcFDVOOIMbWj5Xg+A71PO7LcMf7ivHKiOLh7ayJOwY=; b=vv5kw4+dmXcTWH8MZk8wrEDtvj9lIz09fUqBK/LHpg9yvfVVrXN055Zt47OlDj7Y1j Dp7SQxul5Q4UzgT6/rs0ekLHr/YcMr6XZmqZMT5lbZeqTJZL7xcdG5sPIHRJ+bONNFFG Lo7zps3PFwnpMqWVon7fNuCtlxrL46iibkoRZk6iLoRGWasrjyieqkHzlml4J9oMBBCW osZKBxEgmF5nw2va04YdgCipFx/H5gPsBMqsF71XX8cOSRd+hDi2mPHMLxUYCXqE2vS0 6302lyeWCTOpSDFY4cHF/VgzATZUCPMgU856TllU+nsilXQGWf08ePfC+5Vg7GL0q03H 1yeg== MIME-Version: 1.0 X-Received: by 10.52.230.105 with SMTP id sx9mr27203025vdc.10.1394544573923; Tue, 11 Mar 2014 06:29:33 -0700 (PDT) Received: by 10.220.150.132 with HTTP; Tue, 11 Mar 2014 06:29:33 -0700 (PDT) Date: Tue, 11 Mar 2014 08:29:33 -0500 Message-ID: Subject: Two odd problems with STABLE-10 r262921 From: Karl Denninger To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Mar 2014 13:29:35 -0000 Two things I've run into with this coming from 9.2-STABLE.... 1. I am getting errors coming from mail transmissions to certain MX relays -- and only those relays. One of them is (ironically) mx1.freebsd.org, which precludes emailing the list from my primary email address! The error logs in the maillog file show: Mar 11 08:17:46 NewFS sm-mta[3605]: STARTTLS=client, relay=mx1.freebsd.org., version=TLSv1/SSLv3, verify=FAIL, cipher=ECDHE-RSA-AES256-GCM-SHA384, bits=256/256 Mar 11 08:17:46 NewFS sm-mta[3605]: STARTTLS: write error=syscall error (-1), errno=13, get_error=error:00000000:lib(0):func(0):reason(0), retry=99, ssl_err=5 Mar 11 08:17:46 NewFS sm-mta[3605]: s2AKht3B064414: SYSERR(root): putbody: write error: Permission denied Mar 11 08:17:46 NewFS sm-mta[3605]: s2AKht3B064414: SYSERR(root): timeout writing message to mx1.freebsd.org.: Permission denied Mar 11 08:17:46 NewFS sm-mta[3605]: s2AKht3B064414: to=< freebsd-fs@freebsd.org>, ctladdr= (1001/1001), delay=16:33:50, xdelay=00:00:05, mailer=esmtp, pri=4186247, relay= mx1.freebsd.org. [8.8.178.115], dsn=4.0.0, stat=Deferred Permission denied -- on a socket? As root? What am I missing here? (Shutting off TLS does not resolve this.) However, this is not universal; it only impacts *some* emails.... Mar 11 08:20:37 NewFS sm-mta[5433]: s2BDKbF4005433: from=< ticker@fs.denninger.net>, size=962, class=0, nrcpts=1, msgid=< 201403111320.s2BDKTF3005412@fs.denninger.net>, proto=ESMTP, daemon=IPv4, relay=localhost [127.0.0.1] Mar 11 08:20:37 NewFS sendmail[5412]: s2BDKTF3005412: to=xxxxxxxx@yahoo.com, ctladdr=ticker (20098/20098), delay=00:00:08, xdelay=00:00:05, mailer=relay, pri=3 0494, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (Message accepted) Mar 11 08:20:37 NewFS sm-mta[5461]: STARTTLS=client, relay= mta5.am0.yahoodns.net., version=TLSv1/SSLv3, verify=FAIL, cipher=DHE-RSA-CAMELLIA256-SHA, bits=256/256 Mar 11 08:20:39 NewFS sm-mta[5461]: s2BDKbF4005433: to=, ctladdr= (20098/20098), delay=00:00:02, xdelay=00:00:02, mailer=esmtp, pri=30962, relay=mta5.am0.yahoodns.net. [66.196.118.35], dsn=2.0.0, stat=Sent (ok dirdel) That one went through successfully.... This is new; I didn't have any trouble on 9.2-STABLE at all. Ideas? The other issue is that I am running into bizarre wired memory behavior. I have ZFS on the box and it was wiring down ~20GB, driving the system into paging. I dropped arc_max to 16GB as a hard limit, it's currently showing 15GB, but... 20531152 wire zfs-stats -A shows: ------------------------------------------------------------------------ ZFS Subsystem Report Tue Mar 11 08:27:55 2014 ------------------------------------------------------------------------ ARC Summary: (HEALTHY) Memory Throttle Count: 0 ARC Misc: Deleted: 4.22m Recycle Misses: 57.10k Mutex Misses: 320 Evict Skips: 2.35m ARC Size: 95.96% 15.35 GiB Target Size: (Adaptive) 100.00% 16.00 GiB Min Size (Hard Limit): 12.50% 2.00 GiB Max Size (High Water): 8:1 16.00 GiB ARC Size Breakdown: Recently Used Cache Size: 75.49% 12.08 GiB Frequently Used Cache Size: 24.51% 3.92 GiB ARC Hash Breakdown: Elements Max: 1.59m Elements Current: 55.53% 883.80k Collisions: 5.84m Chain Max: 16 Chains: 261.48k ------------------------------------------------------------------------ Ok, where's the rest coming from? There's nothing in the shared memory segment list that appears to be related. Is there a memory leak in here somewhere?