syslog-ng issue after update to syslog-ng-3.12.1

Arhat · 2017-11-15 09:10:49

After updating to syslog-ng-3.12.1 the syslog-ng.service file has disappeared.

sudo systemctl status syslog-ng
Failed to start syslog-ng.service: Unit syslog-ng.service not found.

sudo systemctl list-units --all
syslog-ng.service                                                                         not-found i
syslog.service                                                                            not-found i

Scimmia · 2017-11-15 09:12:40

So look at the file list, see what's in the package.

loqs · 2017-11-15 09:48:17

https://github.com/balabit/syslog-ng/co … 7266814436

Arhat · 2017-11-15 10:51:38

Scimmia wrote:

So look at the file list, see what's in the package.

So what are you saying? If users spot an issue that they can fix themselves, they shouldn't bother reporting it?

loqs wrote:

https://github.com/balabit/syslog-ng/co … 7266814436

Thank you. I did a quick search on the balabit page but failed to pick that up.

I suspect there is a problem with the syslog-ng@.service file.

Reverting back to the old service file entry:

ExecStart=/usr/bin/syslog-ng -F $SYSLOGNG_OPTS

instead of the new

ExecStart=/usr/bin/syslog-ng -F $OTHER_OPTIONS —cfgfile $CONFIG_FILE —control $CONTROL_FILE —persist-file $PERSIST_FILE —pidfile $PID_FILE

got syslog-ng running.

Last edited by Arhat (2017-11-15 11:22:16)

hwm · 2017-11-15 11:19:25

loqs wrote:

https://github.com/balabit/syslog-ng/co … 7266814436

Thanks for the pointer, I couldn't find that post and searched for the problem by looking at the sources yesterday. What is missing from the Arch package is the parameter file /etc/default/syslog-ng@default (from the source's contrib/systemd directory)

* parameter files have to be installed to /etc/default or /etc/sysconfig
* parameter file have to be named like: syslog-ng@instancename

With the file /etc/default/syslog-ng@default in place you can start and enable syslog-ng@default.service

Scimmia · 2017-11-15 15:29:53

Arhat wrote:

Scimmia wrote:
So look at the file list, see what's in the package.
So what are you saying? If users spot an issue that they can fix themselves, they shouldn't bother reporting it?

I'm saying there is no issue.

ghen · 2017-11-16 10:03:43

Except no /etc/default/syslog-ng@default is installed, and there is no indication whatsoever that the user should disable syslog-ng and enable syslog-ng@default after this upgrade. It leaves a broken system.

cmorgenstern · 2017-11-16 19:24:42

A quick scan of the file list for syslog-ng 3.12.1-3 shows no /etc/default/syslog-ng@default. Using the GitHub link as a guide, here is what I came up with based on my system for syslog-ng@default:

CONFIG_FILE=/etc/syslog-ng/syslog-ng.conf
PERSIST_FILE=/var/lib/syslog-ng/syslog-ng.persist
CONTROL_FILE=/var/run/syslog-ng.ctl
PID_FILE=/var/run/syslog-ng.pid
OTHER_OPTIONS="--enable-core"

I'm inclined to call this an issue - either syslog-ng@default should be included, or it should be made clear that the file needs to be created to define the variables called within the systemd unit file that ships with syslog-ng at the moment.

ghen · 2017-11-16 20:08:18

I created a bug report for this: https://bugs.archlinux.org/task/56355

kokoko3k · 2017-11-16 21:46:38

cmorgenstern wrote:

either syslog-ng@default should be included, or it should be made clear that the file needs to be created

https://fedoramagazine.org/systemd-template-unit-files/

Last edited by kokoko3k (2017-11-16 21:50:17)

eschwartz · 2017-11-17 03:10:23

My question is, why does upstream install a template unit with their build system, but not also install the /etc/default/ file that came with the same commit?

ghen · 2017-11-17 07:38:10

Yes, + the templating seems overkill for a generic server or desktop. :-)

But even if an /etc/default file were installed by upstream or by the package, action is still required from the user and in a very specific order, to disable the old and enable the new unit while it (still) exists according to systemctl:
yum update ; systemctl disable syslog-ng ; systemctl stop syslog-ng ; systemctl daemon-reload ; systemctl start syslog-ng@default ; systemctl enable syslog-ng@default

Another order will yield errors because systemctl does not know anymore / or does not know yet the old resp. new unit.

Arch Linux

#1 2017-11-15 09:10:49

syslog-ng issue after update to syslog-ng-3.12.1

#2 2017-11-15 09:12:40

Re: syslog-ng issue after update to syslog-ng-3.12.1

#3 2017-11-15 09:48:17

Re: syslog-ng issue after update to syslog-ng-3.12.1

#4 2017-11-15 10:51:38

Re: syslog-ng issue after update to syslog-ng-3.12.1

#5 2017-11-15 11:19:25

Re: syslog-ng issue after update to syslog-ng-3.12.1

#6 2017-11-15 15:29:53

Re: syslog-ng issue after update to syslog-ng-3.12.1

#7 2017-11-16 10:03:43

Re: syslog-ng issue after update to syslog-ng-3.12.1

#8 2017-11-16 19:24:42

Re: syslog-ng issue after update to syslog-ng-3.12.1

#9 2017-11-16 20:08:18

Re: syslog-ng issue after update to syslog-ng-3.12.1

#10 2017-11-16 21:46:38

Re: syslog-ng issue after update to syslog-ng-3.12.1

#11 2017-11-17 03:10:23

Re: syslog-ng issue after update to syslog-ng-3.12.1

#12 2017-11-17 07:38:10

Re: syslog-ng issue after update to syslog-ng-3.12.1

Board footer