From: | Stuart Bishop <stuart(at)stuartbishop(dot)net> |
---|---|
To: | Andrew Taylor <andydtaylor(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: var/log/postgresql deletion mystery Ubuntu 12.10 |
Date: | 2013-02-12 06:56:42 |
Message-ID: | CADmi=6PmAHeVhFDUV9xx9k7prXzWwKdzY6u41UodbV-5j4eo7g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Feb 11, 2013 at 6:36 AM, Andrew Taylor <andydtaylor(at)gmail(dot)com> wrote:
> Here's what I did to fix this in Ubuntu 12.10.
>
> Now I cannot explain (a) why this problem came into being or (b) what the
> science is behind my fix. This was my first dive into Linux logs and there
> being seemingly an array of ways logging can be handled now, and was handled
> historically, with some variation across linux distributions. It's a little
> bewildering. All I can say it this works, and if someone can offer me
> insight into (postgres) logs in Ubuntu it would be appreciated. So here we
> go:
>
> Syslog seems to be one of the key processes available for logging. You can
> use this to determine what gets logged by given processes.
>
> In /etc/rsyslog.d/50-default.conf
> Add this line:
> local0.* -/var/log/postgresql/
I think that by adding this line, you now have the PostgreSQL startup
script and syslog fighting over ownership of this directory. The
Debian and Ubuntu packages pipe PostgreSQL's stderr here, and are not
configured to use syslog nor PostgreSQL's builtin log rotation.
--
Stuart Bishop <stuart(at)stuartbishop(dot)net>
http://www.stuartbishop.net/
From | Date | Subject | |
---|---|---|---|
Next Message | Silk Parrot | 2013-02-12 07:05:31 | Guidance on building Foreign Data Wrapper on Windows. |
Previous Message | Pavan Deolasee | 2013-02-12 05:50:02 | Re: cloning postgres-xc |