Closed tod-uma closed 6 months ago
can you share more about the environment you face this error?
Yes, I'm using the Ansible scripts to install the universal forwarder on a new OEL9 VM. It uses the Splunk provided RPM to install.
we released new updates for 9.1.x to support unix domain socket files. that should resolve this issue. feel free to comment if you still run into errors
we released new updates for 9.1.x to support unix domain socket files. that should resolve this issue. feel free to comment if you still run into errors
unix sockets code seems to work, but I'm having other issues with that update. Specifically the calls to splunk_api. They seem to be in the library/ directory, but when you bring splunk-ansible in as a role or collection to a different ansible project, it does not look in that library/ directory for modules. I'm looking at how hard it would be to structure as a proper ansible collection so that the module imports correctly.
I have gotten it to work in my environment with the development branch. Thank you for the fix.
when using this to install a universal forwarder 9.1.2, the scripts fail on "Wait for splunkd management port". This is because now by default the forwarder doesn't actually listen on a tcp managment port on linux, it uses a socket file instead. By default the mgmtMode is set to auto, which means it does not listen on a tcp port. The scripts need to be updated to find a different way to know when the splunkd is up.
See mgmtMode in: https://docs.splunk.com/Documentation/Splunk/9.1.2/Admin/Serverconf
Error when running:
TASK [splunk_common : Wait for splunkd management port] *** fatal: [test-forwarder.test.test]: FAILED! => changed=false elapsed: 300 msg: Timeout when waiting for 127.0.0.1:8089