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_222030731.pp.4zMMVb Last 10 lines of output were: Mar 17 22:20:15 almalinux9-64-puppet8.example.com splunk[1169]: ----- Mar 17 22:20:15 almalinux9-64-puppet8.example.com splunk[1170]: Signature ok �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 18.28 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_222408358.pp.Lc0VlR Last 10 lines of output were: Mar 17 22:24:11 almalinux9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited, status=1/FAILURE Mar 17 22:24:11 almalinux9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 8459 (splunkd) with signal SIGKILL. Mar 17 22:24:11 almalinux9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:24:11 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.52 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_222046601.pp.gpfTXy Last 10 lines of output were: Mar 17 22:20:32 centos9-64-puppet7.example.com splunk[1006]: ----- Mar 17 22:20:32 centos9-64-puppet7.example.com splunk[1007]: Signature ok �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 18.36 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_222426250.pp.6kn2kH Last 10 lines of output were: Mar 17 22:24:29 centos9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited, status=1/FAILURE Mar 17 22:24:29 centos9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 7469 (splunkd) with signal SIGKILL. Mar 17 22:24:29 centos9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:24:29 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.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 'rocky9-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222037422.pp.9DzIio Last 10 lines of output were: Mar 17 22:20:22 rocky9-64-puppet7.example.com splunk[1104]: ----- Mar 17 22:20:22 rocky9-64-puppet7.example.com splunk[1107]: Signature ok �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 19.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 'rocky9-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222431994.pp.GIdYvw Last 10 lines of output were: Mar 17 22:24:35 rocky9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited, status=1/FAILURE Mar 17 22:24:35 rocky9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 8043 (splunkd) with signal SIGKILL. Mar 17 22:24:35 rocky9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:24:35 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.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 'rocky9-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222033822.pp.hyuj2J Last 10 lines of output were: Mar 17 22:20:18 rocky9-64-puppet8.example.com splunk[1101]: ----- Mar 17 22:20:18 rocky9-64-puppet8.example.com splunk[1110]: Signature ok �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 23.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 'rocky9-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222431790.pp.ks0mW6 Last 10 lines of output were: Mar 17 22:24:35 rocky9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited, status=1/FAILURE Mar 17 22:24:35 rocky9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 8089 (splunkd) with signal SIGKILL. Mar 17 22:24:35 rocky9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:24:35 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.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 'centos7-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222041438.pp.IG6MkF Last 10 lines of output were: Mar 17 22:20:26 centos7-64-puppet7.example.com splunk[583]: Getting CA Private Key Mar 17 22:20:26 centos7-64-puppet7.example.com splunk[583]: unable to write 'random state' �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Info: Stage[main]: Unscheduling all events on Stage[main] Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies �[mNotice: Applied catalog in 17.83 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_222431802.pp.TvbESI Last 10 lines of output were: Mar 17 22:24:35 centos7-64-puppet7.example.com systemd[1]: SplunkForwarder.service: control process exited, code=exited status=1 Mar 17 22:24:35 centos7-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 17 22:24:35 centos7-64-puppet7.example.com systemd[1]: Unit SplunkForwarder.service entered failed state. Mar 17 22:24:35 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.92 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_222046201.pp.XfEEmf Last 10 lines of output were: Mar 17 22:20:30 centos7-64-puppet8.example.com splunk[582]: Getting CA Private Key Mar 17 22:20:30 centos7-64-puppet8.example.com splunk[582]: unable to write 'random state' �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Info: Stage[main]: Unscheduling all events on Stage[main] Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies �[mNotice: Applied catalog in 17.51 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_222427577.pp.8n9M8X Last 10 lines of output were: Mar 17 22:24:31 centos7-64-puppet8.example.com systemd[1]: SplunkForwarder.service: control process exited, code=exited status=1 Mar 17 22:24:31 centos7-64-puppet8.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 17 22:24:31 centos7-64-puppet8.example.com systemd[1]: Unit SplunkForwarder.service entered failed state. Mar 17 22:24:31 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.90 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_222044897.pp.hosDgF Last 10 lines of output were: Mar 17 22:20:29 centos9-64-puppet8.example.com splunk[995]: ----- Mar 17 22:20:29 centos9-64-puppet8.example.com splunk[996]: Signature ok �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 18.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 'centos9-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222431814.pp.OmkSmE Last 10 lines of output were: Mar 17 22:24:35 centos9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited, status=1/FAILURE Mar 17 22:24:35 centos9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 7521 (splunkd) with signal SIGKILL. Mar 17 22:24:35 centos9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:24:35 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 2.19 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_222107044.pp.43lOVH Last 10 lines of output were: Mar 17 22:20:52 almalinux9-64-puppet7.example.com splunk[1162]: ----- Mar 17 22:20:52 almalinux9-64-puppet7.example.com splunk[1165]: Signature ok �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 18.48 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_222448972.pp.EapXzO Last 10 lines of output were: Mar 17 22:24:52 almalinux9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited, status=1/FAILURE Mar 17 22:24:52 almalinux9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 8404 (splunkd) with signal SIGKILL. Mar 17 22:24:52 almalinux9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:24:52 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.70 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_222135190.pp.EolJqd Last 10 lines of output were: Mar 17 22:21:20 centos8-64-puppet7.example.com splunk[1191]: Getting CA Private Key Mar 17 22:21:20 centos8-64-puppet7.example.com splunk[1191]: unable to write 'random state' �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 15.24 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_222507025.pp.eQuX2q Last 10 lines of output were: Mar 17 22:25:10 centos8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited status=1 Mar 17 22:25:10 centos8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 8015 (splunkd) with signal SIGKILL. Mar 17 22:25:10 centos8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:25:10 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 'centos8-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222145564.pp.LjL6mb Last 10 lines of output were: Mar 17 22:21:31 centos8-64-puppet8.example.com splunk[1196]: Getting CA Private Key Mar 17 22:21:31 centos8-64-puppet8.example.com splunk[1196]: unable to write 'random state' �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 15.45 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_222520960.pp.rMtOLw Last 10 lines of output were: Mar 17 22:25:24 centos8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited status=1 Mar 17 22:25:24 centos8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 8013 (splunkd) with signal SIGKILL. Mar 17 22:25:24 centos8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:25:24 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.45 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_222100455.pp.lu5f8W Last 10 lines of output were: Mar 17 22:20:44 ubuntu2204-64-puppet7.example.com splunk[1179]: unable to write 'random state' Mar 17 22:20:44 ubuntu2204-64-puppet7.example.com splunk[1180]: writing RSA key �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 28.04 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_222531960.pp.6Y1uR1 Last 10 lines of output were: Mar 17 22:25:35 ubuntu2204-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 27304 (sh) with signal SIGKILL. Mar 17 22:25:35 ubuntu2204-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 27305 (splunkd) with signal SIGKILL. Mar 17 22:25:35 ubuntu2204-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:25:35 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.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 'debian10-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222051960.pp.8Nqba1 Last 10 lines of output were: Mar 17 22:20:35 debian10-64-puppet8.example.com splunk[1475]: Getting CA Private Key Mar 17 22:20:35 debian10-64-puppet8.example.com splunk[1475]: unable to write 'random state' �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 32.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 'debian10-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222534884.pp.ijGZG1 Last 10 lines of output were: Mar 17 22:25:39 debian10-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 27732 (sh) with signal SIGKILL. Mar 17 22:25:39 debian10-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 27733 (splunkd) with signal SIGKILL. Mar 17 22:25:39 debian10-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:25:39 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 2.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 'almalinux8-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222207034.pp.TMkGyA Last 10 lines of output were: Mar 17 22:20:22 almalinux8-64-puppet8.example.com splunk[1054]: Getting CA Private Key Mar 17 22:20:22 almalinux8-64-puppet8.example.com splunk[1054]: unable to write 'random state' �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 16.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 'almalinux8-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222541822.pp.JPHBsD Last 10 lines of output were: Mar 17 22:25:45 almalinux8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited status=1 Mar 17 22:25:45 almalinux8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 7889 (splunkd) with signal SIGKILL. Mar 17 22:25:45 almalinux8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:25:45 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.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-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222056629.pp.0X1Ah2 Last 10 lines of output were: Mar 17 22:20:40 debian10-64-puppet7.example.com splunk[1474]: Getting CA Private Key Mar 17 22:20:40 debian10-64-puppet7.example.com splunk[1474]: unable to write 'random state' �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 32.23 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_222541780.pp.y3ZnNe Last 10 lines of output were: Mar 17 22:25:46 debian10-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 27697 (sh) with signal SIGKILL. Mar 17 22:25:46 debian10-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 27698 (splunkd) with signal SIGKILL. Mar 17 22:25:46 debian10-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:25:46 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.66 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_222212387.pp.rue9nC Last 10 lines of output were: Mar 17 22:20:28 rocky8-64-puppet7.example.com splunk[995]: Getting CA Private Key Mar 17 22:20:28 rocky8-64-puppet7.example.com splunk[995]: unable to write 'random state' �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 16.44 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_222549907.pp.0hkVSW Last 10 lines of output were: Mar 17 22:25:53 rocky8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited status=1 Mar 17 22:25:53 rocky8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 7444 (splunkd) with signal SIGKILL. Mar 17 22:25:53 rocky8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:25:53 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.88 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_222117554.pp.sFKgii Last 10 lines of output were: Mar 17 22:21:00 ubuntu2004-64-puppet7.example.com splunk[1213]: unable to write 'random state' Mar 17 22:21:00 ubuntu2004-64-puppet7.example.com splunk[1214]: writing RSA key �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 29.66 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_222557926.pp.Wwi9v8 Last 10 lines of output were: Mar 17 22:26:02 ubuntu2004-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 27338 (sh) with signal SIGKILL. Mar 17 22:26:02 ubuntu2004-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 27339 (splunkd) with signal SIGKILL. Mar 17 22:26:02 ubuntu2004-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:26:02 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.48 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_222348748.pp.50YDNa Last 10 lines of output were: Mar 17 22:23:31 ubuntu2004-64-puppet8.example.com splunk[1212]: unable to write 'random state' Mar 17 22:23:31 ubuntu2004-64-puppet8.example.com splunk[1213]: writing RSA key �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Info: Stage[main]: Unscheduling all events on Stage[main] Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies �[mNotice: Applied catalog in 28.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 'ubuntu2004-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222819620.pp.tFsc0a Last 10 lines of output were: Mar 17 22:28:23 ubuntu2004-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 27384 (sh) with signal SIGKILL. Mar 17 22:28:23 ubuntu2004-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 27385 (splunkd) with signal SIGKILL. Mar 17 22:28:23 ubuntu2004-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:28:23 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.43 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_222353643.pp.2QlJXq Last 10 lines of output were: Mar 17 22:23:36 ubuntu2204-64-puppet8.example.com splunk[1183]: unable to write 'random state' Mar 17 22:23:36 ubuntu2204-64-puppet8.example.com splunk[1184]: writing RSA key �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 29.97 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_222834523.pp.DXYT81 Last 10 lines of output were: Mar 17 22:28:39 ubuntu2204-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 27350 (sh) with signal SIGKILL. Mar 17 22:28:39 ubuntu2204-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 27351 (splunkd) with signal SIGKILL. Mar 17 22:28:39 ubuntu2204-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:28:39 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.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 'almalinux8-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222209579.pp.u3gnLw Last 10 lines of output were: Mar 17 22:20:25 almalinux8-64-puppet7.example.com splunk[1075]: Getting CA Private Key Mar 17 22:20:25 almalinux8-64-puppet7.example.com splunk[1075]: unable to write 'random state' �[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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 20.37 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_222548999.pp.O7D2JL Last 10 lines of output were: -- Logs begin at Sun 2024-03-17 22:19:49 UTC, end at Sun 2024-03-17 22:31:52 UTC. -- Mar 17 22:31:52 almalinux8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Processes still around after final SIGKILL. Entering failed mode. Mar 17 22:31:52 almalinux8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:31:52 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 361.74 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_222217422.pp.UNK7Yr Last 10 lines of output were: Mar 17 22:28:36 rocky8-64-puppet8.example.com systemd[1]: Splunkd.service: Failed with result 'exit-code'. Mar 17 22:28:36 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] �[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 377.44 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_223155654.pp.4X2fU0 Last 10 lines of output were: Mar 17 22:31:59 rocky8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited status=1 Mar 17 22:31:59 rocky8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 7494 (splunkd) with signal SIGKILL. Mar 17 22:31:59 rocky8-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 17 22:31:59 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 1.69 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