[MCOL-1946] Our syslog-ng is broken Created: 2018-11-15  Updated: 2022-11-05  Resolved: 2022-11-05

Status: Closed
Project: MariaDB ColumnStore
Component/s: N/A
Affects Version/s: None
Fix Version/s: Icebox

Type: Bug Priority: Major
Reporter: Andrew Hutchings (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by MCOL-4305 syslog-ng logging didnt work after 1.... Closed
Relates
relates to MCOL-1730 Support for syslog-ng version 3.13 Closed

 Description   

I think we should consider removing our syslog-ng support and stick with rsyslog. Our syslog-ng scripts aren't compatible with Ubuntu 18.04, they destroy the system's only config and just don't work even when patched.

Every OS we support has rsyslog.

 Comments   
Comment by John Dutchover [ 2018-11-20 ]

I recently encountered issue with syslog-ng 3.5.6 (repo: epel/x86_64) on CentOS 7. This is an old post but possibly worth looking into instead of dropping support.

While troubleshooting (eventually reverting to rsyslog) I found a couple of steps effective with syslog-ng 3.5.6:
1. vim /usr/lib/systemd/system/syslog-ng.service -add "After" line-
[Unit]
Description=System Logger Daemon
Documentation=man:syslog-ng(8)
After=network.target
...

2. vim /etc/syslog-ng/syslog-ng.conf
Comment-out this line:
unix-stream("/dev/log");
...and replace with this:
unix-dgram("/dev/log");

The second item here is related to the "systemd" socket type behavior and/or treatment of syslog-ng.

Comment by Andrew Hutchings (Inactive) [ 2018-11-20 ]

Many thanks jdutch. Definitely something we should consider.

Comment by Sasha V [ 2018-12-31 ]

I was unable to setup rsyslog on docker Ubuntu 16, while syslog-ng worked for me there.

Comment by John Dutchover [ 2019-01-01 ]

The issue appeared on CentOS [7], not Ubuntu.

Comment by Todd Stoffel (Inactive) [ 2022-11-05 ]

Item is out of date. Closing due to inactivity. If you feel this was done in error please open a new ticket.

Generated at Thu Feb 08 02:32:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.