BUG #17228: Adding 'syslog' to log_destination causes postgres service throw an error when restarted.

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: sivaram(dot)subramani(at)signify(dot)com
Subject: BUG #17228: Adding 'syslog' to log_destination causes postgres service throw an error when restarted.
Date: 2021-10-13 13:11:15
Message-ID: 17228-398f9949774b7c4e@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 17228
Logged by: Sivaram Vasudevan
Email address: sivaram(dot)subramani(at)signify(dot)com
PostgreSQL version: 12.0
Operating system: Windows 2019 Server
Description:

Hi,

I am trying to harden the postgresql 12 installation using the benchmark
provided by https://www.cisecurity.org.
One of the test case is "Ensure the correct syslog facility is selected". By
default log_destination is 'stderr'. When I add 'syslog' to log_destination
in postgresql.conf, and restart psotgres service, the service fails to
start. In windows event viewer, we see error stating that postgresql.conf
file contains errors.
Kindly guide me how to enable syslog for postgres and use LOCAL1 as the
facility.

Thanks and Regards,
Sivaram

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2021-10-13 13:59:06 Re: BUG #17227: segmentation fault with jsonb_to_recordset
Previous Message PG Bug reporting form 2021-10-13 09:16:08 BUG #17227: segmentation fault with jsonb_to_recordset