Comments (6)
kreeuwijk
commented on June 30, 2024
This is new behavior in Splunk Forwarder 7.1 and above. Downgrading to a 7.0.x version will work as a temporary workaround.
from puppet-splunk.
ralfbosz
commented on June 30, 2024
The platform/posix.pp exec's need " --no-prompt".
from puppet-splunk.
ralfbosz
commented on June 30, 2024
Sorry for the many pushes, a work-around can be done by using a user-seed.conf where you define a NEW password. That way the --no-prompt is not needed. Only tested on RedHat 7.
Also good way to set the password...
from puppet-splunk.
juanlittledevil
commented on June 30, 2024
This did not actually solve the issue. Also, I don't see any support for user-seed.conf in the module. A simpler solution would be simply add --seed-passwd changeme instead of --no-prompt. As this makes splunk behave like it did prior to 7.1.x
from puppet-splunk.
zhasaan
commented on June 30, 2024
I am using splunkforwarder version 7.2.2 and seeing following behaviour in my local acceptance testing
==================================================================
Notice: /Stage[main]/Splunk::Forwarder/File[/opt/splunkforwarder/etc/system/local/server.conf]/ensure: created
Debug: /Stage[main]/Splunk::Forwarder/File[/opt/splunkforwarder/etc/system/local/server.conf]: The container Class[Splunk::Forwarder] will propagate my refresh event
Debug: Class[Splunk::Forwarder]: The container Stage[main] will propagate my refresh event
Debug: Execlicense_splunkforwarder: Executing check '/usr/bin/test -f /opt/splunkforwarder/ftr'
Debug: Executing with uid=splunk: '/usr/bin/test -f /opt/splunkforwarder/ftr'
Debug: Execlicense_splunkforwarder: Executing 'splunk ftr --accept-license --answer-yes --no-prompt'
Debug: Executing with uid=splunk: 'splunk ftr --accept-license --answer-yes --no-prompt'
Notice: /Stage[main]/Splunk::Platform::Posix/Exec[license_splunkforwarder]/returns: executed successfully
Info: /Stage[main]/Splunk::Platform::Posix/Exec[license_splunkforwarder]: Scheduling refresh of Service[splunk]
Debug: /Stage[main]/Splunk::Platform::Posix/Exec[license_splunkforwarder]: The container Class[Splunk::Platform::Posix] will propagate my refresh event
Debug: Execenable_splunkforwarder: Executing '/opt/splunkforwarder/bin/splunk enable boot-start -user splunk'
Debug: Executing: '/opt/splunkforwarder/bin/splunk enable boot-start -user splunk'
Notice: /Stage[main]/Splunk::Platform::Posix/Exec[enable_splunkforwarder]/returns: executed successfully
Info: /Stage[main]/Splunk::Platform::Posix/Exec[enable_splunkforwarder]: Scheduling refresh of Service[splunk]
Debug: /Stage[main]/Splunk::Platform::Posix/Exec[enable_splunkforwarder]: The container Class[Splunk::Platform::Posix] will propagate my refresh event
Debug: Class[Splunk::Platform::Posix]: The container Stage[main] will propagate my refresh event
Debug: Executing: '/usr/bin/systemctl is-active splunk'
Debug: Executing: '/usr/bin/systemctl is-enabled splunk'
Debug: Executing: '/usr/bin/systemctl unmask splunk'
Debug: Executing: '/usr/bin/systemctl start splunk'
Debug: Runing journalctl command to get logs for systemd start failure: journalctl -n 50 --since '5 minutes ago' -u splunk --no-pager
Debug: Executing: 'journalctl -n 50 --since '5 minutes ago' -u splunk --no-pager'
Debug: Executing: '/usr/bin/systemctl is-active splunk'
Error: Systemd start for splunk failed!
journalctl log for splunk:
-- No entries --
Error: /Stage[main]/Splunk::Virtual/Service[splunk]/ensure: change from stopped to running failed: Systemd start for splunk failed!
journalctl log for splunk:
-- No entries --
Debug: /Stage[main]/Splunk::Virtual/Service[splunk]: Skipping restart; service is not running
Notice: /Stage[main]/Splunk::Virtual/Service[splunk]: Triggered 'refresh' from 6 events
Debug: /Stage[main]/Splunk::Virtual/Service[splunk]: The container Class[Splunk::Virtual] will propagate my refresh event
Debug: Class[Splunk::Virtual]: Resource is being skipped, unscheduling all events
Info: Class[Splunk::Virtual]: Unscheduling all events on Class[Splunk::Virtual]
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [default] host]/value: value changed '[redacted sensitive information]' to '[redacted sensitive information]'
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [default] host]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/audit/audit.log] disabled]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/audit/audit.log] disabled]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/audit/audit.log] followTail]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/audit/audit.log] followTail]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/audit/audit.log] index]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/audit/audit.log] index]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/audit/audit.log] sourcetype]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/audit/audit.log] sourcetype]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/audit/audit.log] crcSalt]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/audit/audit.log] crcSalt]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/auth.log] disabled]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/auth.log] disabled]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/auth.log] followTail]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/auth.log] followTail]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/auth.log] index]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/auth.log] index]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/auth.log] sourcetype]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/auth.log] sourcetype]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/auth.log] crcSalt]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/auth.log] crcSalt]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/messages] disabled]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/messages] disabled]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/messages] followTail]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/messages] followTail]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/messages] index]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/messages] index]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/messages] sourcetype]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/messages] sourcetype]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/messages] crcSalt]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [monitor:///var/log/messages] crcSalt]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/outputs.conf [tcpout] defaultGroup]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/outputs.conf [tcpout] defaultGroup]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/outputs.conf [tcpout] disabled]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/outputs.conf [tcpout] disabled]: The container Class[Pumasplunk::Config] will propagate my refresh event
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/outputs.conf [tcpout:Production] server]/ensure: created
Debug: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/outputs.conf [tcpout:Production] server]: The container Class[Pumasplunk::Config] will propagate my refresh event
Debug: Class[Pumasplunk::Config]: The container Stage[main] will propagate my refresh event
Debug: Class[Pumasplunk::Config]: The container Class[Pumasplunk] will propagate my refresh event
Debug: Class[Pumasplunk]: The container Stage[main] will propagate my refresh event
Debug: Stage[main]: Resource is being skipped, unscheduling all events
Info: Stage[main]: Unscheduling all events on Stage[main]
Debug: Finishing transaction 29608740
Debug: Storing state
Info: Creating state file /opt/puppetlabs/puppet/cache/state/state.yaml
Debug: Stored state in 0.01 seconds
Notice: Applied catalog in 139.19 seconds
Debug: Applying settings catalog for sections reporting, metrics
Debug: Finishing transaction 27656040
Debug: Received report to process from centos-7-x64.core.dir.telstra.com
Debug: Evicting cache entry for environment 'production'
Debug: Caching environment 'production' (ttl = 0 sec)
Debug: Processing report from centos-7-x64.core.dir.telstra.com with processor Puppet::Reports::Store
# /home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-3.22.0/lib/beaker/host.rb:375:in `exec'
# /home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-3.22.0/lib/beaker/dsl/helpers/host_helpers.rb:83:in `block in on'
# /home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-3.22.0/lib/beaker/shared/host_manager.rb:127:in `run_block_on'
# /home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-3.22.0/lib/beaker/dsl/patterns.rb:37:in `block_on'
# /home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-3.22.0/lib/beaker/dsl/helpers/host_helpers.rb:63:in `on'
# /home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-puppet-0.17.1/lib/beaker-puppet/helpers/puppet_helpers.rb:521:in `block in apply_manifest_on'
# /home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-3.22.0/lib/beaker/shared/host_manager.rb:127:in `run_block_on'
# /home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-3.22.0/lib/beaker/dsl/patterns.rb:37:in `block_on'
# /home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-puppet-0.17.1/lib/beaker-puppet/helpers/puppet_helpers.rb:450:in `apply_manifest_on'
# /home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-puppet-0.17.1/lib/beaker-puppet/helpers/puppet_helpers.rb:528:in `apply_manifest'
# ./spec/acceptance/pumasplunk_spec.rb:23:in `block (3 levels) in <top (required)>'
# /home/vagrant/.rvm/gems/ruby-2.2.10/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:123:in `block in run'
# /home/vagrant/.rvm/gems/ruby-2.2.10/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `loop'
# /home/vagrant/.rvm/gems/ruby-2.2.10/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `run'
# /home/vagrant/.rvm/gems/ruby-2.2.10/gems/rspec-retry-0.6.1/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
# /home/vagrant/.rvm/gems/ruby-2.2.10/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:37:in `block (2 levels) in setup'
-
pumasplunk install with default parameters is idempotent
Failure/Error: result = apply_manifest(pp, catch_changes: true)
Beaker::Host::CommandFailure:
Host 'centos-7-x64' exited with 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest.pp.v7sESR
Last 200 lines of output were:
2019-04-11 13:29:30.475607 WARN puppetlabs.facter - locale environment variables were bad; continuing with LANG=C LC_ALL=C
Info: Loading facts
Info: Loading facts
Warning: /etc/puppetlabs/puppet/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
(in /etc/puppetlabs/puppet/hiera.yaml)
Notice: Compiled catalog for centos-7-x64.core.dir.telstra.com in environment production in 0.77 seconds
Info: Applying configuration version '1554989374'
Notice: /Stage[main]/Splunk::Forwarder/Splunkforwarder_input[default_host]/value: value changed 'myfqdn' to 'centos-7-x64.core.dir.telstra.com'
Info: /Stage[main]/Splunk::Forwarder/Splunkforwarder_input[default_host]: Scheduling refresh of Service[splunk]
Notice: /Stage[main]/Splunk::Platform::Posix/Exec[enable_splunkforwarder]/returns: Unable to create symlink='/etc/systemd/system/multi-user.target.wants/SplunkForwarder.service'
Notice: /Stage[main]/Splunk::Platform::Posix/Exec[enable_splunkforwarder]/returns: : File exists
Error: '/opt/splunkforwarder/bin/splunk enable boot-start -user splunk' returned 8 instead of one of [0]
Error: /Stage[main]/Splunk::Platform::Posix/Exec[enable_splunkforwarder]/returns: change from notrun to 0 failed: '/opt/splunkforwarder/bin/splunk enable boot-start -user splunk' returned 8 instead of one of [0]
Notice: /Stage[main]/Splunk::Virtual/Service[splunk]: Dependency Exec[enable_splunkforwarder] has failures: true
Info: /Stage[main]/Splunk::Virtual/Service[splunk]: Unscheduling all events on Service[splunk]
Warning: /Stage[main]/Splunk::Virtual/Service[splunk]: Skipping because of failed dependencies
Notice: /Stage[main]/Pumasplunk::Config/Ini_setting[/opt/splunkforwarder/etc/system/local/inputs.conf [default] host]/value: value changed '[redacted sensitive information]' to '[redacted sensitive information]'
Info: Stage[main]: Unscheduling all events on Stage[main]
Notice: Applied catalog in 0.27 seconds/home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-3.22.0/lib/beaker/host.rb:375:in `exec'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-3.22.0/lib/beaker/dsl/helpers/host_helpers.rb:83:in `block in on'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-3.22.0/lib/beaker/shared/host_manager.rb:127:in `run_block_on'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-3.22.0/lib/beaker/dsl/patterns.rb:37:in `block_on'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-3.22.0/lib/beaker/dsl/helpers/host_helpers.rb:63:in `on'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-puppet-0.17.1/lib/beaker-puppet/helpers/puppet_helpers.rb:521:in `block in apply_manifest_on'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-3.22.0/lib/beaker/shared/host_manager.rb:127:in `run_block_on'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-3.22.0/lib/beaker/dsl/patterns.rb:37:in `block_on'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-puppet-0.17.1/lib/beaker-puppet/helpers/puppet_helpers.rb:450:in `apply_manifest_on'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/beaker-puppet-0.17.1/lib/beaker-puppet/helpers/puppet_helpers.rb:528:in `apply_manifest'
./spec/acceptance/pumasplunk_spec.rb:27:in `block (3 levels) in <top (required)>'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:123:in `block in run'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `loop'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `run'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/rspec-retry-0.6.1/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:37:in `block (2 levels) in setup'
-
pumasplunk install with default parameters Service "SplunkForwarder" should be running
Failure/Error: it { is_expected.to be_running }
expected Service "SplunkForwarder" to be running./spec/acceptance/pumasplunk_spec.rb:41:in `block (4 levels) in <top (required)>'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:123:in `block in run'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `loop'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `run'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/rspec-retry-0.6.1/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
/home/vagrant/.rvm/gems/ruby-2.2.10/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:37:in `block (2 levels) in setup'
Finished in 3 minutes 45 seconds (files took 11.63 seconds to load)
6 examples, 3 failures
Failed examples:
rspec ./spec/acceptance/pumasplunk_spec.rb:22 # pumasplunk install with default parameters applies with no errors
rspec ./spec/acceptance/pumasplunk_spec.rb:26 # pumasplunk install with default parameters is idempotent
rspec ./spec/acceptance/pumasplunk_spec.rb:41 # pumasplunk install with default parameters Service "SplunkForwarder" should be running
Since I am testing Puppet code inside a local docker/container , following what I can see inside container when splunkforwarer package installation gets completed
[root@centos-7-x64 /]# ls -l /etc/systemd/system/SplunkForwarder.service;cat /etc/systemd/system/SplunkForwarder.service;ls -l /etc/systemd/system/multi-user.target.wants/;ps -ef |grep systemctl
-rwx------. 1 root root 793 Apr 11 13:29 /etc/systemd/system/SplunkForwarder.service
#This unit file replaces the traditional start-up script for systemd
#configurations, and is used when enabling boot-start for Splunk on
#systemd-based Linux distributions.
[Unit]
Description=Systemd service file for Splunk, generated by 'splunk enable boot-start'
After=network.target
[Service]
Type=simple
Restart=always
ExecStart=/opt/splunkforwarder/bin/splunk _internal_launch_under_systemd
LimitNOFILE=65536
SuccessExitStatus=51 52
RestartPreventExitStatus=51
RestartForceExitStatus=52
User=splunk
Delegate=true
MemoryLimit=100G
CPUShares=1024
PermissionsStartOnly=true
ExecStartPost=/bin/bash -c "chown -R splunk:splunk /sys/fs/cgroup/cpu/system.slice/%n"
ExecStartPost=/bin/bash -c "chown -R splunk:splunk /sys/fs/cgroup/memory/system.slice/%n"
[Install]
WantedBy=multi-user.target
total 0
lrwxrwxrwx. 1 root root 37 Mar 5 04:19 crond.service -> /usr/lib/systemd/system/crond.service
lrwxrwxrwx. 1 root root 46 Mar 5 04:19 rhel-configure.service -> /usr/lib/systemd/system/rhel-configure.service
lrwxrwxrwx. 1 root root 43 Apr 11 13:29 SplunkForwarder.service -> /etc/systemd/system/SplunkForwarder.service
lrwxrwxrwx. 1 root root 36 Apr 3 01:49 sshd.service -> /usr/lib/systemd/system/sshd.service
root 2517 1905 0 13:29 ? 00:00:00 grep --color=auto systemctl
Any idea as why "systemctl start splunk" is failing ?
from puppet-splunk.
alexjfisher
commented on June 30, 2024
@zhasaan A large refactoring to support splunk 7.2 has just been merged
It's not in a release yet, but if you want to test the version from the master branch, hopefully this will work better for you.
from puppet-splunk.
Related Issues (20)
- Facter splunk version HOT 2
- pass4SymmKey not read properly HOT 1
- puppet will create outputs.conf and delete it immediately which causes splunk to restart every puppet run
- child class splunk::forwarder::password::seed has a typo in the fact HOT 1
- net-tools 'installed' over and over, but is really installing splunkforwarder HOT 4
- Forwarder service won't start due to incorrect permissions HOT 2
- Corrupt MSI installer HOT 3
- Unable to disable archive creation in splunk::forwarder.
- default location of splunk.secret is wrong? HOT 2
- seed_password seems to ignore the enforced order, causing installation to fail. HOT 1
- Can you promote a new version to puppet forge? HOT 2
- splunk::enterprise - "has no parameter" manage_net_tools HOT 2
- Support for Splunk 8.x and RHEL 8 HOT 2
- Warning: Secrets file NOT found HOT 1
- `purge_inputs => true` leaves artifacts in `inputs.conf` HOT 3
- SPLUNK_OS_USER is being sets a splunk regardless of $splunk_user value HOT 1
- Splunk 9.0.5+ Package Not Found on RedHat x86_64
- Question on monitoring journald HOT 2
- Wrong Splunk Forwarder user on Windows HOT 1
- adding a section without any settings does not work, this is needed for the replication port
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from puppet-splunk.