From: Wells Oliver <wellsoliver@gmail.com>
To: Giuseppe Broccolo <giuseppe.broccolo@2ndquadrant.it>
Cc: pgsql-admin@postgresql.org
Subject: Re: Couldn't start postgres, got no logging, ran postgres manually for info-- help?
Date: Fri, 12 Jul 2013 10:29:00 -0700
Message-ID: <58263C4A-0786-4FA1-9AA3-C176A9C0ED35@gmail.com> (raw)
In-Reply-To: <51DFCB17.5050905@2ndquadrant.it>
References: <CAOC+FBXTnv4rro4Z26ZtaG35gTqO9vviRgH937ubD1BL9d4ZaA@mail.gmail.com>
<51DFCB17.5050905@2ndquadrant.it>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Alright but what's odd to me is that it's a standard out of the box ubuntu configuration, meaning:
log_destination is 'stderr'
logging_collector is on
log_directory is /var/log/postgresql/
log_filename is postgresql-%Y-%m-%d_%H%M%S.log
When I ran pg_ctlcluster start, I only received "please check the log output", but there were no errors logged. There are definitely log items when the server was running normally.
When I ran postgres manually, I saw the permissions issue. My question then is where was this error sent when running pg_ctlcliuster, or why was it squashed? It would have been helpful to have that from the start.
--
Wells Oliver
wellsoliver@gmail.com
On Jul 12, 2013, at 2:23 AM, Giuseppe Broccolo <giuseppe.broccolo@2ndquadrant.it> wrote:
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: wellsoliver@gmail.com, giuseppe.broccolo@2ndquadrant.it
Subject: Re: Couldn't start postgres, got no logging, ran postgres manually for info-- help?
In-Reply-To: <58263C4A-0786-4FA1-9AA3-C176A9C0ED35@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox