Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 17FF91337B97 for ; Fri, 8 Apr 2011 10:17:54 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 32313-01-4 for ; Fri, 8 Apr 2011 13:17:45 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail1.hosting.digiweb.ie (mail1.hosting.digiweb.ie [89.234.64.49]) by mail.postgresql.org (Postfix) with SMTP id F25BA1337BD9 for ; Fri, 8 Apr 2011 10:17:17 -0300 (ADT) Received: (qmail 884 invoked by uid 399); 8 Apr 2011 13:17:11 -0000 Received: from unknown (HELO ?127.0.0.1?) (ray@teladesign.ie@86.43.79.16) by mail1.hosting.digiweb.ie with SMTP; 8 Apr 2011 13:17:11 -0000 X-Originating-IP: 86.43.79.16 Message-ID: <4D9F0AD5.2060301@iol.ie> Date: Fri, 08 Apr 2011 14:17:09 +0100 From: Raymond O'Donnell Reply-To: rod@iol.ie User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: Rich Shepard CC: pgsql-php@postgresql.org Subject: Re: Connecting PHP-based Application to Postgres-9.0.3 References: <201104070920.37258@hal.medialogik.com> <20110407125635.1ae13751.wmoran@potentialtech.com> <20110407132029.be595363.wmoran@potentialtech.com> <4D9DFAB2.2080902@consistentstate.com> <4D9E0B35.3060402@consistentstate.com> <4D9E210C.3080009@iol.ie> <4D9E387F.4030600@iol.ie> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 110408-0, 08/04/2011), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201104/32 X-Sequence-Number: 4194 On 07/04/2011 23:51, Rich Shepard wrote: > On Thu, 7 Apr 2011, Raymond O'Donnell wrote: > >> That is a bit odd. Yes, please do post the relevant bits of the .conf - >> clearer heads than mine may spot something. > > Ray, > > #------------------------------------------------------------------------------ > > # ERROR REPORTING AND LOGGING > #------------------------------------------------------------------------------ > > > # - Where to Log - > > log_destination = 'syslog' # Valid values are combinations of > # stderr, csvlog, syslog, and eventlog, > # depending on platform. csvlog > # requires logging_collector to be on. > > # This is used when logging to stderr: > logging_collector = on # Enable capturing of stderr and csvlog > # into log files. Required to be on for > # csvlogs. > # (change requires restart) > > # These are only used if logging_collector is on: > #log_directory = 'pg_log' # directory where log files are written, > # can be absolute or relative to PGDATA > #log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log' # log file name pattern, > # can include strftime() escapes That all looks fine.... I seem to remember from upthread that you were looking for logging output in /var/log/messages, but syslog output should be in /var/log/syslog (on my Debian system anyway). Also, from the above, look in the pg_log directory under the data directory for any log files that might get written there. Ray. -- Raymond O'Donnell :: Galway :: Ireland rod@iol.ie