Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Systemd Splunk 7.3.0 #246

Open
s9p1 opened this issue Jul 25, 2019 · 0 comments
Open

Systemd Splunk 7.3.0 #246

s9p1 opened this issue Jul 25, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@s9p1
Copy link

s9p1 commented Jul 25, 2019

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)

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 (between cpu/memory and system.slice):

ExecStartPost=/bin/bash -c "chown -R <uid>:<gid> /sys/fs/cgroup/cpu/system.slice/%n"
ExecStartPost=/bin/bash -c "chown -R <uid>:<gid> /sys/fs/cgroup/memory/system.slice/%n"
@juniorsysadmin juniorsysadmin added the enhancement New feature or request label Aug 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants