![]() We tried other combinations of -user and -systemd-managed, none worked. Now the service name is called rvice instead of splunk, but we have to live with that. Because on OL8 we only managed to get it working using /splunk enable boot-start -accept-license -answer-yes -auto-ports -no-prompt The -user and -systemd-managed parameters seems to have some effect on the final result. ![]() Reason for going with init.d over systemd was to be compatible with a lot of other stuff after the rename of the splunk service back in 7.2. Up until 8.2.6 we used these parameters before first run: /splunk enable boot-start -user splunk -systemd-managed 0 -accept-license -answer-yes -auto-ports -no-prompt Not to mention (i know it is a known error): Warning: Attempting to revert the SPLUNK_HOME ownership Warning: Executing "chown -R splunk /opt/splunkforwarder" Several: stop/restart of the forwarder service takes forever. OL7: forwarder will not start due to being non-rootĪll: Invalid key in stanza in /opt/splunkforwarder/etc/system/default/alert_nf, line 229: enable_allowlist (value: false). OL8: forwarder starts but cannot read outside of splunkhome Here are some of the cases that we have discovered so far: Upgrade goes well but after start i get different results depending on OS and how i started the forwarder. I am aware that upgrading to 9.0 is only possible from 8.1 or higher. Are anybody else having issues with the upgrade to univsersal forwarder 9.0 on linux? This is the first time i had this many issues - not counting the rename of the service back in 7.2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |