Hi richgalloway, Thank you for your reply. Below were the results I received after I followed these Instructions: systemctl status Splunkd.service" and "journalctl -xeu Splunkd.service" ┌──(root💀kali)-[/opt/splunk/bin] └─# systemctl status Splunkd.service 1 ⨯ × Splunkd.service - Systemd service file for Splunk, generated by 'splunk enable boot-start' Loaded: loaded (/etc/systemd/system/Splunkd.service; enabled; preset: disabled) Active: failed (Result: exit-code) since Mon 2022-12-12 07:06:40 EST; 28s ago Process: 2284 ExecStart=/opt/splunk/bin/splunk _internal_launch_under_systemd (code=killed, signal=INT) Process: 2285 ExecStartPost=/bin/bash -c chown -R splunk:splunk /sys/fs/cgroup/cpu/system.slice/Splunkd.service (code=exited, status=1/FAILURE) Main PID: 2284 (code=killed, signal=INT) CPU: 14ms Dec 12 07:06:40 kali systemd[1]: Splunkd.service: Scheduled restart job, restart counter is at 5. Dec 12 07:06:40 kali systemd[1]: Stopped Systemd service file for Splunk, generated by 'splunk enable boot-start'. Dec 12 07:06:40 kali systemd[1]: Splunkd.service: Start request repeated too quickly. Dec 12 07:06:40 kali systemd[1]: Splunkd.service: Failed with result 'exit-code'. Dec 12 07:06:40 kali systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. (root💀kali)-[/opt/splunk/bin] └─# journalctl -xeu Splunkd.service 3 ⨯ ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit Splunkd.service has finished with a failure. ░░ ░░ The job identifier is 2754 and the job result is failed. Dec 12 07:06:40 kali systemd[1]: Splunkd.service: Scheduled restart job, restart counter is at 5. ░░ Subject: Automatic restarting of a unit has been scheduled ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ Automatic restarting of the unit Splunkd.service has been scheduled, as the result for ░░ the configured Restart= setting for the unit. Dec 12 07:06:40 kali systemd[1]: Stopped Systemd service file for Splunk, generated by 'splunk enable boot-start'. ░░ Subject: A stop job for unit Splunkd.service has finished ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A stop job for unit Splunkd.service has finished. ░░ ░░ The job identifier is 2829 and the job result is done. Dec 12 07:06:40 kali systemd[1]: Splunkd.service: Start request repeated too quickly. Dec 12 07:06:40 kali systemd[1]: Splunkd.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit Splunkd.service has entered the 'failed' state with result 'exit-code'. Dec 12 07:06:40 kali systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. ░░ Subject: A start job for unit Splunkd.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit Splunkd.service has finished with a failure. ░░ ░░ The job identifier is 2829 and the job result is failed. lines 794-828/828 (END) I never received these kinds of results or problems when I installed Splunk before but this is new release splunk 9.02. Do you know how to solve these problems? Thank you.
... View more
