I've read through the docs and come up with a simple test config:
st1:
$SPLUNK_HOME/etc/deployment-apps
contains testapp
, which has defaults/inputs.conf
and defaults/outputs.conf
$SPLUNK_HOME/etc/system/local/serverclass.conf
has
[serverClass:testapp]
[serverClass:testapp:app:*]
filterType = whitelist
whitelist.0 = st2
restartSplunkd = true
splunk list deploy-clients
shows
Deployment client: ip=172.16.111.129, dns=st2, hostname=st2, mgmt=8089, build=98164, name=st2, id=connection_172.16.111.129_8089_st2_st2_st2, utsname=linux-x86_64
utsname: linux-x86_64
name: st2
ip: 172.16.111.129
hostname: st2
build: 98164
dns: st2
mgmt: 8089
phoneHomeTime: Thu May 19 09:13:22 2011
id: connection_172.16.111.129_8089_st2_st2_st2
st2:
$SPLUNK_HOME/etc/system/local/deploymentclient.conf
contains
[deployment-client]
clientName=st2
[target-broker:deploymentServer]
targetUri = st1:8089
st2 never gets testapp
deployed to it. I've had a support ticket open for 8 days on this with no luck. What did I leave out?
Thanks,
jon
Try prepending your serverclass.conf with an empty global stanza. Whitelist is the default filter type so you may omit it if you'd like:
[global]
[serverClass:testapp]
[serverClass:testapp:app:*]
whitelist.0 = st2
restartSplunkd = true
Alternate serverclass.conf...
[global]
[serverClass:testClass]
whitelist.0 = st2
restartSplunkd = true
[serverClass:testClass:app:testapp]
Try prepending your serverclass.conf with an empty global stanza. Whitelist is the default filter type so you may omit it if you'd like:
[global]
[serverClass:testapp]
[serverClass:testapp:app:*]
whitelist.0 = st2
restartSplunkd = true
Alternate serverclass.conf...
[global]
[serverClass:testClass]
whitelist.0 = st2
restartSplunkd = true
[serverClass:testClass:app:testapp]
I just noticed that the alternate code you posted above had testClass in the stanza opening. That did the trick. Yahtzee!
Nothing. Kinda frustrating. I've had a ticket open for 10 days now, with no activity since Monday. There's no step-by-step on the doc site. I guess I'm mentally deficient since others have it working, but it sure seems like I've got the min requirements. Thanks for trying.
It is interesting you're seeing the deployment client listed as phoning home via deployment server but not seeing it pick up any apps. Do you see any relevant information in splunkd.log?
Yes, and also 'splunk restart'. On both ends.
Did you perform a 'splunk reload deploy-server' after editing serverclass.conf?
typos in original post fixed.
st1: deployment-apps. st2 - yes, big typo there on my part. editing the orig. (as in, post is wrong, install is correct)
Actually - I see where you reported st2 was phoning home to st1, which answers my 2nd question.
Regarding st2: Is your deploymentclient configuration in "$SPLUNK_HOME/etc/system/local/serverclass.conf" or "$SPLUNK_HOME/etc/system/local/deploymentclient.conf". That is as equally as important as the above hyphen comment.
In the same vein, did you intend to write "$SPLUNK_HOME/etc/system/local/serverclass.conf contains" or "$SPLUNK_HOME/etc/system/local/deploymentclient.conf contains". It should be the latter and is as important as the hyphen in my above comment.
Regarding st1: Is your app literally in "$SPLUNK_HOME/etc/deploymentapps/testapp" or is it in "$SPLUNK_HOME/etc/deployment-apps/testapp"? The hyphen is important but I thought perhaps that was a typo in your initial question.
No change.