From owner-freebsd-ports-bugs@freebsd.org Mon Feb 29 18:50:11 2016 Return-Path: Delivered-To: freebsd-ports-bugs@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 599F0AB8639 for ; Mon, 29 Feb 2016 18:50:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3125DF53 for ; Mon, 29 Feb 2016 18:50:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u1TIoAYv036815 for ; Mon, 29 Feb 2016 18:50:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 207589] dns/fastresolve broken, builds but does not run (segfaults) Date: Mon, 29 Feb 2016 18:50:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: 000.fbsd@quip.cz X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Feb 2016 18:50:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207589 --- Comment #2 from Miroslav Lachman <000.fbsd@quip.cz> --- It is strange. I already asked few other people on Czech FreeBSD mailinglist and fastresolve doen't work for them too. http://www.freebsd.cz/listserv/archive/users-l/2016q1/029182.html I have this problem for about one year on all 10.x installations. I previou= sly used it on 8.4 without any problems, but after upgrade to 10.1 or 10.2 it s= tops (after recompilation from fresh ports tree). The behavior is the same on all our webservers (15+ machines). Some of them were upgraded from older releas= es, some of them freshly installed from 10.2 ISO media. Then I migrated from individual ports tree to centralized private pkg repo = with poudriere. All machines have kernel and userland in sync, all machines have installed fastresolve from the same repo where packages are built in 10.2-RELEASE-p8 amd64 environment: # poudriere jail -l JAILNAME VERSION ARCH METHOD TIMESTAMP PATH 10_1_amd64 10.1-RELEASE-p22 amd64 ftp 2015-10-03 19:21:59 /vol0/poudriere/jails/10_1_amd64 10_2_amd64 10.2-RELEASE-p8 amd64 ftp 2016-01-07 10:34:52 /vol0/poudriere/jails/10_2_amd64 Did you tested fastresolve package from official repo or did you compiled it from ports tree? Info from one of our machines # uname -srmi FreeBSD 10.2-RELEASE-p10 amd64 GENERIC # pkg info -d -r fastresolve fastresolve-2.10_5 Depends on : adns-1.5.0 p5-BerkeleyDB-0.55 perl5-5.20.3_8 db5-5.3.28_3 adns (adnslogres command) works without problem I am really out of ideas what to try next to make fastresolve work on 10.2 amd64 machines. Thank you for your reply anyway. --=20 You are receiving this mail because: You are the assignee for the bug.=