- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just created a test app for my environment to be pushed to a single workstation. It does not successfully deploy from this server shown in the forwarder management GUI. The error message in the splunkd.log is
01-14-2014 08:13:51.367 -0500 WARN ClientSessionsManager - ip=10.237.1.63 name=ANT-andDESK Updating record for sc=Global Win x64 Client app=fwd_to_splunkprod: action=Install result=Fail
and
01-14-2014 08:13:51.367 -0500 WARN ClientSessionsManager - ip=10.237.1.63 name=ANT-DESK Updating record for sc=Global Win x64 Client app=fwd_to_splunkprod: action=Download result=Fail
Not sure what to look at next to troubleshoot this issue. The forwarder creates the folder, but does not transfer the app.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This should help with verifying your configuration, and troubleshooting.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This should help with verifying your configuration, and troubleshooting.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Using the Forward Management GUI I entered a server class of Global Win x86 Client. The debug said Global didn't exist. Used _ instead of spaces and the problem cleared up right away.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

You might want to turn up debugging on the client and server in $SPLUNK_HOME/etc/log.cfg. I would set the following components to debug on the server:
category.DeployedApplication=DEBUG
category.DeployedServerclass=DEBUG
category.DC:UpdateServerclassHandler=DEBUG
category.DeploymentServer=DEBUG
On the client, in the same file, I would set:
category.DC:DeploymentClient=DEBUG
Restart, then hopefully you'll find some meaningful messages in the server and/or client in splunkd.log
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The splunkd process is running as root on the deployment server.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you made sure Splunk DeploymentServer has permissions to the files it's trying to transfer?
