You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Affected Puppet, Ruby, OS and module versions/distributions
Distribution: Ubuntu
Module version: 7.3.0
Splunk version: 7.3.0
Description
With Splunk 7.2.2 there was introduced a new parameter to configure boot-start either with initd or systemd. At first, the default was systemd, with 7.3.0 and above it is initd again.
Please add a configuration for -systemd-managed 0|1 between boot-start and -user in manifests/forwarder/service/nix.pp (if Splunk version >= 7.2.2)
Affected Puppet, Ruby, OS and module versions/distributions
Description
With Splunk 7.2.2 there was introduced a new parameter to configure boot-start either with initd or systemd. At first, the default was systemd, with 7.3.0 and above it is initd again.
Please add a configuration for
-systemd-managed 0|1
betweenboot-start
and-user
inmanifests/forwarder/service/nix.pp
(if Splunk version >= 7.2.2)https://docs.splunk.com/Documentation/Splunk/7.3.0/Admin/RunSplunkassystemdservice
On e.g. Ubuntu Systems you have to correct the generated Systemd Service file
/etc/systemd/system/SplunkForwarder.service
or.../Splunkd.service
:Delete the
init.scope/
in following lines (betweencpu/memory
andsystem.slice
):The text was updated successfully, but these errors were encountered: