splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'rocky9-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120124377.pp.siVrGN Last 10 lines of output were: Mar 18 12:01:44 rocky9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:24: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 18 12:01:44 rocky9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:23: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 18 12:01:44 rocky9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:24: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 18 12:01:44 rocky9-64-puppet8.example.com systemd[1]: Starting Systemd service file for Splunk, generated by 'splunk enable boot-start'... �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 18.22 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'rocky9-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120459648.pp.vssN7r Last 10 lines of output were: Mar 18 12:05:03 rocky9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited, status=1/FAILURE Mar 18 12:05:03 rocky9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 8010 (splunkd) with signal SIGKILL. Mar 18 12:05:03 rocky9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:05:03 rocky9-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 1.55 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos9-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120125198.pp.D1T0PU Last 10 lines of output were: Mar 18 12:01:45 centos9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:24: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 18 12:01:45 centos9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:23: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 18 12:01:45 centos9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:24: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 18 12:01:45 centos9-64-puppet7.example.com systemd[1]: Starting Systemd service file for Splunk, generated by 'splunk enable boot-start'... �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 18.30 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos9-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120501126.pp.S8lKwi Last 10 lines of output were: Mar 18 12:05:04 centos9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited, status=1/FAILURE Mar 18 12:05:04 centos9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 7387 (splunkd) with signal SIGKILL. Mar 18 12:05:04 centos9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:05:04 centos9-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 1.56 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos8-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120141708.pp.UpK9SY Last 10 lines of output were: Mar 18 12:01:58 centos8-64-puppet7.example.com systemd[1]: Splunkd.service: Control process exited, code=exited status=1 Mar 18 12:01:58 centos8-64-puppet7.example.com systemd[1]: Splunkd.service: Killing process 2352 (splunkd) with signal SIGKILL. Mar 18 12:01:58 centos8-64-puppet7.example.com systemd[1]: Splunkd.service: Failed with result 'exit-code'. Mar 18 12:01:58 centos8-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 15.17 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos8-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120510424.pp.yCqMYN Last 10 lines of output were: Mar 18 12:05:13 centos8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited status=1 Mar 18 12:05:13 centos8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 7923 (splunkd) with signal SIGKILL. Mar 18 12:05:13 centos8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:05:13 centos8-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 1.57 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'rocky9-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120133879.pp.hlERFh Last 10 lines of output were: Mar 18 12:01:53 rocky9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:24: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 18 12:01:54 rocky9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:23: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 18 12:01:54 rocky9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:24: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 18 12:01:54 rocky9-64-puppet7.example.com systemd[1]: Starting Systemd service file for Splunk, generated by 'splunk enable boot-start'... �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 18.39 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'rocky9-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120511111.pp.uZAebb Last 10 lines of output were: Mar 18 12:05:14 rocky9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited, status=1/FAILURE Mar 18 12:05:14 rocky9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 7966 (splunkd) with signal SIGKILL. Mar 18 12:05:14 rocky9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:05:14 rocky9-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 1.60 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos7-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120134272.pp.In0HoF Last 10 lines of output were: Mar 18 12:01:53 centos7-64-puppet7.example.com systemd[1]: Splunkd.service: control process exited, code=exited status=1 Mar 18 12:01:53 centos7-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 18 12:01:53 centos7-64-puppet7.example.com systemd[1]: Unit Splunkd.service entered failed state. Mar 18 12:01:53 centos7-64-puppet7.example.com systemd[1]: Splunkd.service failed. �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 17.69 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos7-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120511200.pp.eRbZdk Last 10 lines of output were: Mar 18 12:05:14 centos7-64-puppet7.example.com systemd[1]: SplunkForwarder.service: control process exited, code=exited status=1 Mar 18 12:05:14 centos7-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 18 12:05:14 centos7-64-puppet7.example.com systemd[1]: Unit SplunkForwarder.service entered failed state. Mar 18 12:05:14 centos7-64-puppet7.example.com systemd[1]: SplunkForwarder.service failed. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 1.77 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'almalinux9-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120130131.pp.34Bc8p Last 10 lines of output were: Mar 18 12:01:51 almalinux9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:24: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 18 12:01:51 almalinux9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:23: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 18 12:01:51 almalinux9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:24: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 18 12:01:51 almalinux9-64-puppet7.example.com systemd[1]: Starting Systemd service file for Splunk, generated by 'splunk enable boot-start'... �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 19.43 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'almalinux9-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120515558.pp.0SWEdc Last 10 lines of output were: Mar 18 12:05:19 almalinux9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited, status=1/FAILURE Mar 18 12:05:19 almalinux9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 8336 (splunkd) with signal SIGKILL. Mar 18 12:05:19 almalinux9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:05:19 almalinux9-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 1.91 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos8-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120142303.pp.aikqF0 Last 10 lines of output were: Mar 18 12:02:00 centos8-64-puppet8.example.com systemd[1]: Splunkd.service: Control process exited, code=exited status=1 Mar 18 12:02:00 centos8-64-puppet8.example.com systemd[1]: Splunkd.service: Killing process 2316 (splunkd) with signal SIGKILL. Mar 18 12:02:00 centos8-64-puppet8.example.com systemd[1]: Splunkd.service: Failed with result 'exit-code'. Mar 18 12:02:00 centos8-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 16.63 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos8-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120519326.pp.6IMVE1 Last 10 lines of output were: Mar 18 12:05:23 centos8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited status=1 Mar 18 12:05:23 centos8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 7931 (splunkd) with signal SIGKILL. Mar 18 12:05:23 centos8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:05:23 centos8-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 1.84 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'almalinux9-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120128635.pp.KxmNPM Last 10 lines of output were: Mar 18 12:01:52 almalinux9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:24: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 18 12:01:52 almalinux9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:23: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 18 12:01:52 almalinux9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:24: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 18 12:01:52 almalinux9-64-puppet8.example.com systemd[1]: Starting Systemd service file for Splunk, generated by 'splunk enable boot-start'... �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 22.02 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'almalinux9-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120519475.pp.C6H9rv Last 10 lines of output were: Mar 18 12:05:23 almalinux9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited, status=1/FAILURE Mar 18 12:05:23 almalinux9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 8304 (splunkd) with signal SIGKILL. Mar 18 12:05:23 almalinux9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:05:23 almalinux9-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 1.73 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos9-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120145522.pp.6lWjBV Last 10 lines of output were: Mar 18 12:02:05 centos9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:24: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 18 12:02:05 centos9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:23: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 18 12:02:05 centos9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:24: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 18 12:02:05 centos9-64-puppet8.example.com systemd[1]: Starting Systemd service file for Splunk, generated by 'splunk enable boot-start'... �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 18.19 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos9-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120524202.pp.mK2aiP Last 10 lines of output were: Mar 18 12:05:27 centos9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited, status=1/FAILURE Mar 18 12:05:27 centos9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 7392 (splunkd) with signal SIGKILL. Mar 18 12:05:27 centos9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:05:27 centos9-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 1.58 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos7-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120137973.pp.wonZNM Last 10 lines of output were: Mar 18 12:02:01 centos7-64-puppet8.example.com systemd[1]: Splunkd.service: control process exited, code=exited status=1 Mar 18 12:02:01 centos7-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 18 12:02:01 centos7-64-puppet8.example.com systemd[1]: Unit Splunkd.service entered failed state. Mar 18 12:02:01 centos7-64-puppet8.example.com systemd[1]: Splunkd.service failed. �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 21.03 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos7-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120520778.pp.i7x0M8 Last 10 lines of output were: Mar 18 12:05:24 centos7-64-puppet8.example.com systemd[1]: SplunkForwarder.service: control process exited, code=exited status=1 Mar 18 12:05:24 centos7-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 18 12:05:24 centos7-64-puppet8.example.com systemd[1]: Unit SplunkForwarder.service entered failed state. Mar 18 12:05:24 centos7-64-puppet8.example.com systemd[1]: SplunkForwarder.service failed. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 1.78 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2204-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120144493.pp.RUWJxe Last 10 lines of output were: Mar 18 12:02:14 ubuntu2204-64-puppet8.example.com systemd[1]: Splunkd.service: Killing process 1700 (sh) with signal SIGKILL. Mar 18 12:02:14 ubuntu2204-64-puppet8.example.com systemd[1]: Splunkd.service: Killing process 1701 (splunkd) with signal SIGKILL. Mar 18 12:02:14 ubuntu2204-64-puppet8.example.com systemd[1]: Splunkd.service: Failed with result 'exit-code'. Mar 18 12:02:14 ubuntu2204-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 27.94 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2204-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120609201.pp.ZNHF6K Last 10 lines of output were: Mar 18 12:06:13 ubuntu2204-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 27229 (sh) with signal SIGKILL. Mar 18 12:06:13 ubuntu2204-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 27230 (splunkd) with signal SIGKILL. Mar 18 12:06:13 ubuntu2204-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:06:13 ubuntu2204-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 2.26 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'almalinux8-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120256542.pp.wR58Xf Last 10 lines of output were: Mar 18 12:03:13 almalinux8-64-puppet7.example.com systemd[1]: Splunkd.service: Control process exited, code=exited status=1 Mar 18 12:03:13 almalinux8-64-puppet7.example.com systemd[1]: Splunkd.service: Killing process 2231 (splunkd) with signal SIGKILL. Mar 18 12:03:13 almalinux8-64-puppet7.example.com systemd[1]: Splunkd.service: Failed with result 'exit-code'. Mar 18 12:03:13 almalinux8-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 16.10 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'almalinux8-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120627138.pp.czvMSo Last 10 lines of output were: Mar 18 12:06:30 almalinux8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited status=1 Mar 18 12:06:30 almalinux8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 7762 (splunkd) with signal SIGKILL. Mar 18 12:06:30 almalinux8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:06:30 almalinux8-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 1.51 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2204-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120147899.pp.AwkPL6 Last 10 lines of output were: Mar 18 12:02:17 ubuntu2204-64-puppet7.example.com systemd[1]: Splunkd.service: Killing process 1691 (sh) with signal SIGKILL. Mar 18 12:02:17 ubuntu2204-64-puppet7.example.com systemd[1]: Splunkd.service: Killing process 1692 (splunkd) with signal SIGKILL. Mar 18 12:02:17 ubuntu2204-64-puppet7.example.com systemd[1]: Splunkd.service: Failed with result 'exit-code'. Mar 18 12:02:17 ubuntu2204-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 28.21 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2204-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120624200.pp.VDembw Last 10 lines of output were: Mar 18 12:06:28 ubuntu2204-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 27190 (sh) with signal SIGKILL. Mar 18 12:06:28 ubuntu2204-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 27191 (splunkd) with signal SIGKILL. Mar 18 12:06:28 ubuntu2204-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:06:28 ubuntu2204-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 2.36 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'debian10-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120148161.pp.P5RWZY Last 10 lines of output were: Mar 18 12:02:18 debian10-64-puppet7.example.com systemd[1]: Splunkd.service: Killing process 2104 (sh) with signal SIGKILL. Mar 18 12:02:18 debian10-64-puppet7.example.com systemd[1]: Splunkd.service: Killing process 2105 (splunkd) with signal SIGKILL. Mar 18 12:02:18 debian10-64-puppet7.example.com systemd[1]: Splunkd.service: Failed with result 'exit-code'. Mar 18 12:02:18 debian10-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 28.55 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'debian10-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120622161.pp.CP1Sto Last 10 lines of output were: Mar 18 12:06:26 debian10-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 27573 (sh) with signal SIGKILL. Mar 18 12:06:26 debian10-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 27574 (splunkd) with signal SIGKILL. Mar 18 12:06:26 debian10-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:06:26 debian10-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 2.42 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120151684.pp.coadZo Last 10 lines of output were: Mar 18 12:02:21 ubuntu2004-64-puppet8.example.com systemd[1]: Splunkd.service: Killing process 1734 (sh) with signal SIGKILL. Mar 18 12:02:21 ubuntu2004-64-puppet8.example.com systemd[1]: Splunkd.service: Killing process 1735 (splunkd) with signal SIGKILL. Mar 18 12:02:21 ubuntu2004-64-puppet8.example.com systemd[1]: Splunkd.service: Failed with result 'exit-code'. Mar 18 12:02:21 ubuntu2004-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 28.06 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120624796.pp.wsv0aj Last 10 lines of output were: Mar 18 12:06:29 ubuntu2004-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 27267 (sh) with signal SIGKILL. Mar 18 12:06:29 ubuntu2004-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 27268 (splunkd) with signal SIGKILL. Mar 18 12:06:29 ubuntu2004-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:06:29 ubuntu2004-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 2.39 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'debian10-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120150717.pp.eWmoR5 Last 10 lines of output were: Mar 18 12:02:22 debian10-64-puppet8.example.com systemd[1]: Splunkd.service: Killing process 2110 (sh) with signal SIGKILL. Mar 18 12:02:22 debian10-64-puppet8.example.com systemd[1]: Splunkd.service: Killing process 2111 (splunkd) with signal SIGKILL. Mar 18 12:02:22 debian10-64-puppet8.example.com systemd[1]: Splunkd.service: Failed with result 'exit-code'. Mar 18 12:02:22 debian10-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 30.13 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'debian10-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120628485.pp.gKcPed Last 10 lines of output were: Mar 18 12:06:33 debian10-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 27610 (sh) with signal SIGKILL. Mar 18 12:06:33 debian10-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 27611 (splunkd) with signal SIGKILL. Mar 18 12:06:33 debian10-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:06:33 debian10-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 3.27 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'almalinux8-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120257981.pp.QeRshA Last 10 lines of output were: Mar 18 12:03:18 almalinux8-64-puppet8.example.com systemd[1]: Splunkd.service: Control process exited, code=exited status=1 Mar 18 12:03:18 almalinux8-64-puppet8.example.com systemd[1]: Splunkd.service: Killing process 2176 (splunkd) with signal SIGKILL. Mar 18 12:03:18 almalinux8-64-puppet8.example.com systemd[1]: Splunkd.service: Failed with result 'exit-code'. Mar 18 12:03:18 almalinux8-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 18.82 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'almalinux8-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120636592.pp.7IjWFG Last 10 lines of output were: Mar 18 12:06:40 almalinux8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited status=1 Mar 18 12:06:40 almalinux8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 7741 (splunkd) with signal SIGKILL. Mar 18 12:06:40 almalinux8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:06:40 almalinux8-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 1.61 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120202200.pp.5OGGlr Last 10 lines of output were: Mar 18 12:02:32 ubuntu2004-64-puppet7.example.com systemd[1]: Splunkd.service: Killing process 1725 (sh) with signal SIGKILL. Mar 18 12:02:32 ubuntu2004-64-puppet7.example.com systemd[1]: Splunkd.service: Killing process 1726 (splunkd) with signal SIGKILL. Mar 18 12:02:32 ubuntu2004-64-puppet7.example.com systemd[1]: Splunkd.service: Failed with result 'exit-code'. Mar 18 12:02:32 ubuntu2004-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 28.75 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120634800.pp.EQyYX9 Last 10 lines of output were: Mar 18 12:06:38 ubuntu2004-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 27215 (sh) with signal SIGKILL. Mar 18 12:06:38 ubuntu2004-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 27216 (splunkd) with signal SIGKILL. Mar 18 12:06:38 ubuntu2004-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:06:38 ubuntu2004-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 2.31 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'rocky8-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120309085.pp.ZyEqnQ Last 10 lines of output were: Mar 18 12:03:29 rocky8-64-puppet7.example.com systemd[1]: Splunkd.service: Control process exited, code=exited status=1 Mar 18 12:03:29 rocky8-64-puppet7.example.com systemd[1]: Splunkd.service: Killing process 2117 (splunkd) with signal SIGKILL. Mar 18 12:03:29 rocky8-64-puppet7.example.com systemd[1]: Splunkd.service: Failed with result 'exit-code'. Mar 18 12:03:29 rocky8-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 18.21 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'rocky8-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120646448.pp.owCKyS Last 10 lines of output were: Mar 18 12:06:49 rocky8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited status=1 Mar 18 12:06:49 rocky8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 7370 (splunkd) with signal SIGKILL. Mar 18 12:06:49 rocky8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:06:49 rocky8-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 1.58 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running

Process completed with exit code 1.

splunk enterprise class Splunk version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'rocky8-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_120302833.pp.dSLHq2 Last 10 lines of output were: -- Logs begin at Mon 2024-03-18 12:00:47 UTC, end at Mon 2024-03-18 12:09:22 UTC. -- Mar 18 12:09:22 rocky8-64-puppet8.example.com systemd[1]: Splunkd.service: Processes still around after final SIGKILL. Entering failed mode. Mar 18 12:09:22 rocky8-64-puppet8.example.com systemd[1]: Splunkd.service: Failed with result 'exit-code'. Mar 18 12:09:22 rocky8-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 377.90 seconds

splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.9 works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'rocky8-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_121245001.pp.zUrWP0 Last 10 lines of output were: -- Logs begin at Mon 2024-03-18 12:00:47 UTC, end at Mon 2024-03-18 12:18:48 UTC. -- Mar 18 12:18:48 rocky8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Processes still around after final SIGKILL. Entering failed mode. Mar 18 12:18:48 rocky8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 12:18:48 rocky8-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 361.75 seconds

splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running