From owner-freebsd-ports@FreeBSD.ORG Sat Jun 28 13:50:41 2014 Return-Path: Delivered-To: ports@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 8918B672 for ; Sat, 28 Jun 2014 13:50:41 +0000 (UTC) Received: from mx1.enfer-du-nord.net (mx1.enfer-du-nord.net [IPv6:2001:41d0:8:3c67:1:1:0:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4EBED28A6 for ; Sat, 28 Jun 2014 13:50:40 +0000 (UTC) Received: from sulu.fritz.box (p5DDC2A25.dip0.t-ipconnect.de [93.220.42.37]) by mx1.enfer-du-nord.net (Postfix) with ESMTPSA id 3h0xDs5TfPzVyl for ; Sat, 28 Jun 2014 15:50:37 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) Subject: Net::DNS 0.77 / resolv.conf with comments (was: FreeBSD Port: spamassassin-3.4.0_11) From: Michael Grimm In-Reply-To: <046FCFFD-811E-4B71-9A91-731FE1C6D44F@odo.in-berlin.de> Date: Sat, 28 Jun 2014 15:50:36 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20140624100737.GT2586@home.opsec.eu> <046FCFFD-811E-4B71-9A91-731FE1C6D44F@odo.in-berlin.de> To: ports@FreeBSD.org X-Mailer: Apple Mail (2.1878.2) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2014 13:50:41 -0000 On 25.06.2014, at 17:21, Michael Grimm = wrote: > On 24.06.2014, at 12:57, Dirk-Willem van Gulik = wrote: >> Op 24 jun. 2014, om 12:07 heeft Kurt Jaeger het = volgende geschreven: >>> If you still see the problem, can you provide more details ? >>> What did you test ? What was the output ? >>=20 >>=20 >> The symptom is all DNS failing within Spam Assassin in the default = FreeBSD 10-p3 with latest packages situations; logs will show: >>=20 >> Jun 24 12:02:04 weser spamd[78829]: plugin: eval failed: = available_nameservers: No DNS servers available!=20 >> Jun 24 12:02:04 weser spamd[78829]: (available_nameservers: = [...] No DNS servers available!)=20 >> =09 >> and the solution is to apply the patch from above SA link (below) = -OR- go to a version from apache.org >=3D revision 1603518; for which=20 >> there is not yet a release/tag = (http://svn.apache.org/viewvc?view=3Drevision&revision=3D1603518). >=20 > I ran into the same issue (10-STABLE, recent ports), and JFTR: I had = to downgrade p5-Net-DNS-0.77 back to p5-Net-DNS-0.76 to get = spamassassin-3.4.0_11 running again, no patches applied. > spamassassin-3.4.0 spamassassin-3.4.0_11 and p5-Net-DNS-0.76 worked as expected. After = upgrading to p5-Net-DNS-0.77 I ran into an issue that looked similar to = the one reported above. spamd couldn't be daemonized at start-up (timed = out). After some investigations I found the reason why spamd didn't = start after upgrading to p5-Net-DNS-0.77: /etc/resolv.conf nameserver 1.2.3.4 # some comment nameserver 8.8.8.8 # another comment That has been accepted by p5-Net-DNS-0.76, but for p5-Net-DNS-0.77 I had = to remove the comments: /etc/resolv.conf nameserver 1.2.3.4 nameserver 8.8.8.8 After removing those comments spamassassin-3.4.0_11 and p5-Net-DNS-0.77 = run as expected. Is this a bug or a feature? Thanks and regards, Michael