From owner-freebsd-threads@FreeBSD.ORG Fri Feb 13 08:44:50 2015 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B4FE4BE8; Fri, 13 Feb 2015 08:44:50 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2740FE06; Fri, 13 Feb 2015 08:44:49 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id t1D8iifO001171 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Feb 2015 10:44:44 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t1D8iifO001171 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id t1D8ih1O001170; Fri, 13 Feb 2015 10:44:43 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 13 Feb 2015 10:44:43 +0200 From: Konstantin Belousov To: "Matthew D. Fuller" Subject: Re: Troubles with BIND + r276630 (/r277317 MFC) Message-ID: <20150213084443.GJ34251@kib.kiev.ua> References: <20150212225909.GB15127@over-yonder.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150212225909.GB15127@over-yonder.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: kib@freebsd.org, freebsd-threads@freebsd.org X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2015 08:44:50 -0000 On Thu, Feb 12, 2015 at 04:59:09PM -0600, Matthew D. Fuller wrote: > I've been setting up a stable/10 system (currently r278451, ~early > this week), and had some disturbing troubles out of BIND (net/bind910, > but also tested bind99). Sporadically, on restart, I get errors like > > > Feb 12 10:42:37 dns named[4071]: dns_master_load: /usr/local/etc/namedb/master/empty.db:1: isc_lex_gettoken() failed: I/O error > Feb 12 10:42:37 dns named[4071]: dns_master_load: /usr/local/etc/namedb/master/empty.db:1: I/O error > Feb 12 10:42:37 dns named[4071]: zone 112.100.in-addr.arpa/IN: loading from master file /usr/local/etc/namedb/master/empty.db failed: I/O error > Feb 12 10:42:37 dns named[4071]: zone 112.100.in-addr.arpa/IN: not loaded due to errors. > > > and similar. Nothing wrong with the files, and it's wildly > inconsistent. Easy to reproduce; just hammering 'service named > restart' while tail -f'ing the messages log will show some startups > going problem-free, while others will get random errors in random > files. I can also reproduce it on my -CURRENT workstation (r278359, > ~late last week), but not on several stable/10 systems of late-Dec > vintage. > > In some testing on the -CURRENT box, if I build libc/libthr as of > r276629 and do LD_LIBRARY_PATH hackery (and obviously not the > 'service' wrapper) to use them, I can kick the reload without ever > getting troubles (tried at least a hundred times). Going to 276630, > or using the system libs, it'll happen sporadically (maybe once a > dozen or so on average?). > > > So far, I haven't seen anything odd in anything but BIND. I was > running a mid-Jan -CURRENT before this for a couple weeks too, so > there should have been time for Firefox to throw a hissy fit or > something, but no hint of trouble. So it's not clear whether the > problem is in the libc/libthr changes or in BIND 9.9 and 9.10, but > certainly something between the two is unhappy... Start with ktrace/kdump around the place where the error is thrown out. Does 'reload' involves full process restart, or only reinitialization of the existing program ?