Date: Mon, 27 Jul 2009 19:37:26 -0800 From: Mel Flynn <mel.flynn+fbsd.questions@mailing.thruhere.net> To: freebsd-questions@freebsd.org Subject: Re: Bind 9 (Was: bsdstats) - fatal error: RUNTIME_CHECK(((pthread_mutex_destroy(((&manager->lock))) == 0) Message-ID: <200907271937.26660.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> In-Reply-To: <45184C2B17C02813336AB862@ganymede.hub.org> References: <20090727211751.GA76851@mech-cluster241.men.bris.ac.uk> <200907271407.45243.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> <45184C2B17C02813336AB862@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 27 July 2009 18:35:17 Marc G. Fournier wrote: > --On Monday, July 27, 2009 14:07:44 -0800 Mel Flynn > > <mel.flynn+fbsd.questions@mailing.thruhere.net> wrote: > > On Monday 27 July 2009 13:17:51 Anton Shterenlikht wrote: > >> On ia64 8.0-beta1 SMP, running bsdstats-5.4_2, > >> I get this error: > >> > >> # /usr/local/etc/periodic/monthly/300.statistics > >> /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/task.c:1023: fatal > >> error: RUNTIME_CHECK(((pthread_mutex_destroy(((&manager->lock))) == 0) ? > >> 0 > >> > >> : 34) == 0) failed > > > > That error from bind, > > > >> [: 1: unexpected operator > > > > Is not handled gracefully in the bsdstats script. > > Is there something I can do to improve the script to handle it better? Well, if OP can provide sh -x /usr/local/etc/periodic/monthly/300.statistics output, it's easier to see which variable is empty as a result of a resolver error. Then fix the test expression and either exit or use a retry_x_times mechanism. -- Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200907271937.26660.mel.flynn%2Bfbsd.questions>