Thanks I'll look through that and see what changes I may need to make.

I may have found the problem but I'm still waiting on a build to finish is that my java command was broken when I check to see if I could see some of the Kafka streams to confirm it could access the cluster.

I had based mine on the service file listed in GitHub for rhel package and on one that and one I worked up for consul.

Ronald Fenner
Network Architect
Game Circus LLC.


On May 16, 2019, at 11:30 AM, Evan Rempel <erempel@uvic.ca> wrote:

I think you are just missing the forground flag (-F) in the ExecStart command

You can see a discussion of the systemd service unit file at

https://github.com/balabit/syslog-ng/issues/2667

and a proposed service file.

On 5/16/19 8:27 AM, Ronald Fenner wrote:
I'm trying to switch from an init.d script to a system service and having problems getting the service to run.
The syslog-ng service gets timed out and never starts up.

My service looks like this:
[Unit]
Description="Syslog-ng an enhanced syslog"
Documentation=man:syslog-ng(8)
After=network.target
ConditionFileNotEmpty=/opt/syslog-ng/etc/syslog-ng.conf

[Service]
Type=notify
ExecStart=/opt/syslog-ng/sbin/syslog-ng --no-caps -p /var/run/syslogd.pid -rdvt
ExecReload=/bin/kill -HUP $MAINPID
StandardOutput=journal
StandardError=journal
Restart=on-failure
Environment=LD_LIBRARY_PATH=/usr/lib/jvm/java/jre/lib/amd64/server:$LD_LIBRARY_PATH

[Install]
WantedBy=multi-user.target


______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq