From owner-freebsd-ports@FreeBSD.ORG Tue Oct 20 20:37:10 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB911106568D; Tue, 20 Oct 2009 20:37:10 +0000 (UTC) (envelope-from david@vizion2000.net) Received: from dns1.vizion2000.net (dns1.vizion2000.net [62.49.197.50]) by mx1.freebsd.org (Postfix) with ESMTP id A86328FC0A; Tue, 20 Oct 2009 20:37:10 +0000 (UTC) Received: by dns1.vizion2000.net (Postfix, from userid 1001) id A3BBA34D426; Tue, 20 Oct 2009 21:37:01 +0100 (BST) From: David Southwell Organization: Voice & Vision To: freebsd-ports@freebsd.org, Paul Schmehl Date: Tue, 20 Oct 2009 21:37:01 +0100 User-Agent: KMail/1.12.1 (FreeBSD/7.2-RELEASE-p3; KDE/4.3.1; amd64; ; ) References: <200910171115.30264.david@vizion2000.net> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200910202137.01611.david@vizion2000.net> Cc: ports@freebsd.org Subject: Re: policy-weight -spawn $csock error after power out reboot X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2009 20:37:11 -0000 > --On Saturday, October 17, 2009 05:15:30 -0500 David Southwell > > wrote: > > Hi > > > > FreeBSD dns1.vizion2000.net 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #0: Thu > > Aug 20 12:54:34 BST 2009 > > david@dns1.vizion2000.net:/usr/obj/usr/src/sys/GENERIC amd64 [on intel > > quad] > > > > Following an abrupt power system failure and a system reboot this server > > now gets this error in maillog: > > > > postfix/policyd-weight[9622]: warning: cache_query: $csock couln't be > > created: connect: No such file or directory, calling spawn_cache() > > > > No other problems. Just in case it was due to a retained. pid I deleted > > the .pid file followed by a normal shutdown and reboot - but am still > > getting the same problem. > > > > Thanks in advance for any guidance > > It doesn't look like anyone has answered this. That warning message is > normal to see at startup but should not persist. > > The solution is to rm -fr /tmp/.policyd-weight, then restart > policyd-weight. Policyd-weight will then recreate that dir and recreate > its socket as well as the other files and dirs that go there. > Thanks I found that .. and my script now clears /tmp/.policy-weight if it it exists before policyd-weight is started.!! Thanks David