X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id DEB6A9FB223 for ; Fri, 15 Sep 2006 13:04:46 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 28868-05 for ; Fri, 15 Sep 2006 16:04:42 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mailr.qinetiq-tim.net (mailr.qinetiq-tim.net [128.98.1.9]) by postgresql.org (Postfix) with ESMTP id 8A26E9FA2CA for ; Fri, 15 Sep 2006 13:04:40 -0300 (ADT) Received: from mailhost.eris.qinetiq.com (mailhost.eris.qinetiq.com [128.98.2.2]) by mailr.qinetiq-tim.net (Postfix) with SMTP id EF66812C35C for ; Fri, 15 Sep 2006 17:03:16 +0100 (BST) Received: (qmail 3585 invoked from network); 15 Sep 2006 16:04:05 -0000 Received: from unknown (HELO frost.eris.qinetiq.com) (128.98.76.221) by ins1.eris.qinetiq.com with SMTP; 15 Sep 2006 16:04:05 -0000 From: Nick Howden Reply-To: n.howden@eris.qinetiq.com Organization: QinetiQ To: pgsql-admin@postgresql.org Subject: Re: Auto Vacuum not starting unless postgres is restarted Date: Fri, 15 Sep 2006 16:57:40 +0100 User-Agent: KMail/1.5.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609151657.40122.n.howden@eris.qinetiq.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200609/158 X-Sequence-Number: 23072 >> Hi, >> >> On startup we get an error in the postgres log that the Autovacuum process has >> failed to start -- "autovacuum not started because of misconfiguration". >> However, if we do a restart (/etc/init/d/postgresql8.1 restart) then the >> autovacuum starts fine. >> >> Does anybody have any idea what the problem might be? > Do you have a message about failure to start the statistics collector as > well (on the first try), which is missing on the reattempt? > >It may be that the startup firewall policy (at the time the PostgreSQL >is first started) is restrictive, and is relaxed later on the boot >process. Yes, I do have the message about the failure to start the statistics collector. The firewall rules I have are : # Postgres Statistics Collector iptables -A INPUT -p udp \ -i lo --sport 32779 --dport 32779 \ -j ACCEPT iptables -A OUTPUT -p udp \ -o lo --sport 32779 --dport 32779 \ -j ACCEPT ### iptables -A INPUT -p tcp \ --sport 1024:65535 \ --dport 5432 \ -m state --state NEW,ESTABLISHED,RELATED \ -j ACCEPT iptables -A OUTPUT -p tcp \ --dport 1024:65535 \ --sport 5432 \ -m state --state ESTABLISHED,RELATED \ -j ACCEPT but these should be the same both during boot and after the boot process has finished Nick -- Nick Howden - Senior IT Analyst QinetiQ Trusted Information Management Woodward Building, Room B009 Malvern Technology Park, WR14 3PS Telephone 01684 895566, Fax 896660 The Information contained in this E-Mail and any subsequent correspondence is private and is intended solely for the intended recipient(s). For those other than the recipient any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on such information is prohibited and may be unlawful