Installing universal forwarder is failing because it cannot bind to TCP 8089.
My understanding of TCP communications is this:
Client reaches out to destination server via a dynamic TCP Port to a destination TCP port which is static. (server is listening on static port 8089)
If that is accurate:
When installing the universal forwarder on a client and using the deployment server option hostname:port (8089), why is the install failing because a process already has the 8089 port in use (on the client).
If my understanding is correct, then the client shouldn't care if it already has a process listening on TCP 8089 because when it reaches out to the indexer hostname:8089 it will be sourcing from a dynamic tcp port.
Bottom line, I cannot get the universal forwarder because w3wp.exe is already using 8089 on my client and I cannot change it.
Thanks in advance for any help.
FROM SPLUNKD.LOG
06-16-2016 15:37:27.372 -0500 FATAL HTTPServer - Could not bind to port 8089
↧