Date: Sat, 28 Jun 2014 15:50:36 +0200 From: Michael Grimm <trashcan@odo.in-berlin.de> To: ports@FreeBSD.org Subject: Net::DNS 0.77 / resolv.conf with comments (was: FreeBSD Port: spamassassin-3.4.0_11) Message-ID: <F4076F22-B662-4B82-9367-97269F0557EF@odo.in-berlin.de> In-Reply-To: <046FCFFD-811E-4B71-9A91-731FE1C6D44F@odo.in-berlin.de> References: <F868D930-1D30-478C-A5EC-2F0F7653E926@webweaving.org> <20140624100737.GT2586@home.opsec.eu> <B907A9B7-66DD-4441-844F-F0CC7EF6C611@webweaving.org> <046FCFFD-811E-4B71-9A91-731FE1C6D44F@odo.in-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25.06.2014, at 17:21, Michael Grimm <trashcan@odo.in-berlin.de> = wrote: > On 24.06.2014, at 12:57, Dirk-Willem van Gulik <dirkx@webweaving.org> = wrote: >> Op 24 jun. 2014, om 12:07 heeft Kurt Jaeger <lists@opsec.eu> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F4076F22-B662-4B82-9367-97269F0557EF>