Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UxZZt-0002HK-Rh for pgsql-admin@arkaria.postgresql.org; Fri, 12 Jul 2013 09:23:50 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1UxZZt-00083R-78 for pgsql-admin@arkaria.postgresql.org; Fri, 12 Jul 2013 09:23:49 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UxZZq-00083I-Tq for pgsql-admin@postgresql.org; Fri, 12 Jul 2013 09:23:47 +0000 Received: from mail03.pnet.xcon.it ([62.48.53.116]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UxZZi-00044X-OG for pgsql-admin@postgresql.org; Fri, 12 Jul 2013 09:23:46 +0000 Received: from localhost (av.pnet.xcon.it [10.68.1.18]) by mail03.pnet.xcon.it (Postfix) with ESMTP id 1F6DD4E913 for ; Fri, 12 Jul 2013 11:23:36 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at av Received: from mail03.pnet.xcon.it ([10.68.1.24]) by localhost (av.pnet.xcon.it [10.68.1.18]) (amavisd-new, port 10024) with LMTP id ifPIs9UZ+XUf for ; Fri, 12 Jul 2013 11:23:19 +0200 (CEST) Received: from bnc1.pnet.xcon.it (bnc1.pnet.xcon.it [10.68.1.23]) by mail03.pnet.xcon.it (Postfix) with ESMTP id F10794E912 for ; Fri, 12 Jul 2013 11:23:35 +0200 (CEST) Received: from localhost (av.pnet.xcon.it [10.68.1.18]) by bnc1.pnet.xcon.it (Postfix) with ESMTP id DC9861022D9B for ; Fri, 12 Jul 2013 11:23:35 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at av Received: from bnc1.pnet.xcon.it ([10.68.1.23]) by localhost (av.pnet.xcon.it [10.68.1.18]) (amavisd-new, port 10024) with LMTP id Tcx84OgGBz2M for ; Fri, 12 Jul 2013 11:23:18 +0200 (CEST) Received: from [192.168.0.131] (unknown [83.149.163.202]) (Authenticated sender: giuseppe.broccolo@2ndquadrant.it) by bnc1.pnet.xcon.it (Postfix) with ESMTPSA id 55B071022D9A for ; Fri, 12 Jul 2013 11:23:35 +0200 (CEST) Message-ID: <51DFCB17.5050905@2ndquadrant.it> Date: Fri, 12 Jul 2013 11:23:35 +0200 From: Giuseppe Broccolo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Couldn't start postgres, got no logging, ran postgres manually for info-- help? References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------070902060101060606050509" X-Pg-Spam-Score: 0.8 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org This is a multi-part message in MIME format. --------------070902060101060606050509 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Oliver, Il 12/07/2013 04:07, Wells Oliver ha scritto: > I ran: > > pg_ctlcluster 9.1 main start > > Received: > > The PostgreSQL server failed to start. Please check the log output. > > But, hey, in /var/log/postgresql, there was absolutely no logging. > Nothing. After some googling, I tried: > > usr/lib/postgresql/9.1/bin/postgres -D /data/postgresql/9.1/main -c > config_file=/etc/postgresql/9.1/main/postgresql.conf > > From the command line, which spit out to the terminal: > > 2013-07-12 02:04:05 GMT [30091]: [1-1] FATAL: data directory > "/data/postgresql/9.1/main" has group or world access > > OK, so where the heck did this error message go when I was running > pg_ctlcluster? It would have saved me a lot of time. By default pg_ctlcluster script redirects postmaster's stderr into /var/log/postgresql/postgresql-9.1-main.log. This works only if log_destination is stderr and logging_collector is disabled, else the logs are stored where configured by log_destination, log_filename and log_directory in your postgresql.conf file. Advice is to look into your postgresql.conf how (and if) logging is configured. Regards, Giuseppe. -- Giuseppe Broccolo - 2ndQuadrant Italy PostgreSQL Training, Services and Support giuseppe.broccolo@2ndQuadrant.it | www.2ndQuadrant.it --------------070902060101060606050509 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Hi Oliver,

Il 12/07/2013 04:07, Wells Oliver ha scritto:
I ran:

pg_ctlcluster 9.1 main start

Received:

The PostgreSQL server failed to start. Please check the log output.

But, hey, in /var/log/postgresql, there was absolutely no logging. Nothing. After some googling, I tried:

usr/lib/postgresql/9.1/bin/postgres -D /data/postgresql/9.1/main -c config_file=/etc/postgresql/9.1/main/postgresql.conf 

From the command line, which spit out to the terminal:

2013-07-12 02:04:05 GMT [30091]: [1-1] FATAL:  data directory "/data/postgresql/9.1/main" has group or world access

OK, so where the heck did this error message go when I was running pg_ctlcluster? It would have saved me a lot of time.

By default pg_ctlcluster script redirects postmaster's stderr into /var/log/postgresql/postgresql-9.1-main.log.
This works only if log_destination is stderr and logging_collector is disabled, else the logs are stored where configured by log_destination, log_filename and log_directory in your postgresql.conf file.

Advice is to look into your postgresql.conf how (and if) logging is configured.

Regards,
Giuseppe.

-- 
Giuseppe Broccolo - 2ndQuadrant Italy
PostgreSQL Training, Services and Support
giuseppe.broccolo@2ndQuadrant.it | www.2ndQuadrant.it
--------------070902060101060606050509--