Changing management port problems on Splunkforwarder 4.3

[biciunas]

I've installed Splunkforwarder 4.3 on a CentOS server, using rpm -i command. I've changed the indexing receiver port using the Splunk CLI
./splunk add forward-server 10.0.0.100:7002 -auth admin:changeme
which works and is reflected in /opt/splunk/etc/system/local/outputs.comf
I also changed the management port
./splunk set deploy-poll 10.0.0.100:7089
which is reflected in opt/splunk/etc/system/local/deploymentclient.conf
[target-broker:deploymentServer]
targetUri = 10.0.0.100:7089
However, when I start the splunkforwarder, the splunkd.log contains
02-06-2012 16:51:48.684 +0000 INFO loader - Arguments are: "splunkd" "-p" "8089" "start" "splunkd"
...
02-06-2012 16:51:48.730 +0000 WARN DeploymentClient - Unable to send handshake message to deployment server. Error status is: not_connected

Anyone with clues? I can telnet to the deployment server on port 7089, so I know traffic will flow, and the connection to port 7002 is successfully initialized. Any and all help will be appreciated.

[Brian_Osburn · Accepted solution]

That WARN message is normal, nothing to be worried about.

With regards to the splunkd arguments, the local forwarder always listens on 8089 for administrative communication. That's normal as well.

What problems are you having? not seeing taffic flow?

[biciunas]

Thanks for the information regarding the WARN message.
Traffic was able to flow, and I verified that when I added an local/inputs.conf file which specified which log files to monitor.