From owner-freebsd-stable@FreeBSD.ORG Tue Sep 28 18:30:33 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F148E1065693 for ; Tue, 28 Sep 2010 18:30:33 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id B3D998FC24 for ; Tue, 28 Sep 2010 18:30:33 +0000 (UTC) Received: from elsa.codelab.cz (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 9D6C019E036 for ; Tue, 28 Sep 2010 20:12:03 +0200 (CEST) Received: from [192.168.1.2] (ip-86-49-61-235.net.upcbroadband.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 0D79919E030 for ; Tue, 28 Sep 2010 20:12:00 +0200 (CEST) Message-ID: <4CA22FF0.8060303@quip.cz> Date: Tue, 28 Sep 2010 20:12:00 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.13) Gecko/20100914 SeaMonkey/2.0.8 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: fetch: Non-recoverable resolver failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Sep 2010 18:30:34 -0000 Hi, we are using fetch command from cron to run PHP scripts periodically and sometimes cron sends error e-mails like this: fetch: https://hiden.example.com/cron/fiveminutes: Non-recoverable resolver failure The exact lines from crontab are: */5 * * * * fetch -qo /dev/null "https://hiden.example.com/cron/fiveminutes" */5 * * * * fetch -qo /dev/null "http://another.example.com/wd.php?hash=cslhakjs87LJ3rysalj79" Network is working without problems, resolvers are working fine too. I also tried to use local instance of named at 127.0.0.1 but it did not fix the issue so it seems there is some problem with fetch in phase of resolving address. Note: target domains are hosted on the server it-self and named too. The system is FreeBSD 7.3-RELEASE-p2 i386 GENERIC Can somebody help me to diagnose this random fetch+resolver issue? Miroslav Lachman