Please I need help on something seems quite common but I cannot find immediate online documentation even though I have tried different solutions.
I have installed enterprise server with this command working fine up an running:
-p 9997:9997 -p 8000:8000 -p 8088:8088
-e "SPLUNKSTARTARGS=--accept-license" --env "SPLUNKENABLELISTEN=9997"
Then I installed universalforwarder with this command working fine (no error and healthy):
The problem I have is that my enterprise server cannot see any forwarders, showing:
"There are currently no forwarders configured as deployment clients to this instance."
I have spent a day and tried different solutions i.e. editing the forwarder's outputs.conf file manually, but apparently the problem is that forwarders should be configured as deployment clients??
You need to configure deploymentclient.conf on your forwarder docker. Please find below doc for the same:
Thanks @p_gurav ,
I now added a new deploymentclient.conf to my forwarder container (didn't exist one before here /opt/splunkforwarder/etc/apps/SplunkUniversalForwarder/default/deploymentclient.conf)
Then restarted my forwarder and enterprise, unfortunately still no sign of forwarder on the front end.
I forgot to mention that my deploymentclient.conf file looks like this:
targetUri = splunkenterprise:8089
I tried also supplying SPLUNKDEPLOYMENTSERVER in the forwarder startup command, but forwarder on standing up gets fatal error like this:
"msg": "Status code was -1 and not : Request failed:
The question is that by default it uses 'https' which is not correct.
how do I fix this?
Ok, I am updating this for future if anyone visits this question:
The issue is resolved by changing the forwarder docker run command as below:
The fix is that the -e SPLUNKDEPLOYMENTSERVER='splunkenterprise' doesn't need the default port 8089 to be supplied.