Quantcast
Channel: Questions in topic: "splunk-enterprise"
Viewing all articles
Browse latest Browse all 47296

How to troubleshoot why a Universal Forwarder is not sending data to the Deployment Server?

$
0
0
I installed a Splunk Universal Forwarder on a Windows Server 2012R2 using following command: msiexec.exe /i splunkforwarder-6.3.2-aaff59bb082c-x64-release.msi LOGON_USERNAME="domain\account" LOGON_PASSWORD="password" DEPLOYMENT_SERVER="MyDeploymentServerHost:8089" AGREETOLICENSE=Yes /quiet and I can see that the client (BLD76) is connected, listed in Forwarder Management, one app (Splunk_TA_Windows) has been deployed successfully and it's phoning home: ![alt text][1] However, there's no data being forwarded as my searches don't return any data based on the host name (bld76). Looking at Splunkd.log on bld76, I can see following error when restarting Forwarder: 05-10-2016 16:17:58.809 +0100 ERROR TcpOutputProc - LightWeightForwarder/UniversalForwarder not configured. Please configure outputs.conf. The install process explained above doesn't create an outputs.conf under etc\system\local, but I have deploymentclient.conf with following content there: [target-broker:deploymentServer] targetUri = MyDeploymentServerHost:8089 Could someone please help me diagnose what's missing? I should also add that there's no issues with other universal forwarders sending data (bld10, bld02 & bld73) [1]: /storage/temp/127251-splunk-forwarder.png

Viewing all articles
Browse latest Browse all 47296

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>