Re: Systemd vs logging collector

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Andomar <andomar(at)aule(dot)net>, pgsql-general(at)postgresql(dot)org
Subject: Re: Systemd vs logging collector
Date: 2015-07-01 13:57:01
Message-ID: 5593F1AD.3050005@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 07/01/2015 05:26 AM, Andomar wrote:
>> are you just missing this parameter:
>>
>> #log_destination = 'stderr' # Valid values are
>> combinations of
>> # stderr, csvlog, syslog, and
>> eventlog,
>> # depending on platform. csvlog
>> # requires logging_collector
>> to be on.
>>
>
> Thanks for your reply, log_destination is set to "stderr". And
> logging_collector is "on".

And you have the log_directory set up?

>
> On CentOS, this results in regular Postgres log files. On Arch Linux,
> the results end up in the system journal. It looks like the Postgres
> logging collector somehow misses out on the stream of messages.

Best guess is the systemd script is catching and redirecting the output
first.

>
> Kind regards,
> Andomar
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2015-07-01 13:57:49 Re: Systemd vs logging collector
Previous Message Adrian Klaver 2015-07-01 13:46:43 Re: Systemd vs logging collector