topic Re: Universal Forwarder not connecting to indexer in Getting Data In

Universal Forwarder not connecting to indexer

ciandro — Sat, 03 Nov 2012 06:25:55 GMT

OS=Windows Server 2008 SP1 64-bit, Forwarder version = 5.0, Indexer version = 5.0

Windows Firewall = OFF

Scenario = Win VM on same network as Linux VM running the indexer

Errors:
TcpOutputProc - Cooked connection to ip=192.168.1.10:9997 timed out

CMConfig - A splunktcp forwarder port is not configured in inputs.conf

outputs.conf

[tcpout]

defaultGroup = default-autolb-group

[tcpout:default-autolb-group]

server = 192.168.1.10:9997

[tcpout-server://192.168.1.10:9997]

inputs.conf

[default]

host = PIZZA

I don't think i have to configure any port in the inputs.conf file. I already researched that the CMConfig error is a known bug.

Answers?

Re: Universal Forwarder not connecting to indexer

lguinn2 — Sat, 03 Nov 2012 07:46:22 GMT

On the indexer(s), you must configure a receiving port in inputs.conf

On the forwarder(s), you must configure the same port in outputs.conf. Also on the forwarder(s), you will need to have inputs.conf to collect the data that will be sent to the indexer(s).

There are more details in the manual at Set up forwarding and receiving.

Re: Universal Forwarder not connecting to indexer

dwaddle — Sun, 04 Nov 2012 01:10:22 GMT

Also, you need to make sure nothing is blocking your ability to get there on the indexer side. I would recommend from the Windows machine trying to telnet 192.168.1.10 9997 and see if you can connect with that. It is likely there is a iptables firewall on the linux host blocking your connection.

Re: Universal Forwarder not connecting to indexer

realdridgespl — Thu, 08 Nov 2012 21:01:00 GMT

I am receiving the same error.
This is on a Universal Forwarder.

CMConfig - A splunktcp forwarder port is not configured in inputs.conf

Re: Universal Forwarder not connecting to indexer

realdridgespl — Thu, 08 Nov 2012 21:04:29 GMT

Seems like it is a "known issue" with 5.0 but not sure if it affects the functionality of the Forwarder.

http://docs.splunk.com/Documentation/Splunk/5.0/ReleaseNotes/Knownissues

"A splunktcp forwarder port is not configured in inputs.conf" error message appears on forwarder/search head/master when it should only appear on the affected slave. (SPL-56019)

Re: Universal Forwarder not connecting to indexer

conner9 — Thu, 29 Nov 2012 19:09:12 GMT

Any chance anyone knows a work around for this, before I uninstall 5.0.1?

Re: Universal Forwarder not connecting to indexer

mship — Thu, 31 Jan 2013 20:21:12 GMT

Before rolling back from 5.0.1 put the following entry in the inputs.conf file of your indexer and restart splunk...

[splunktcp://9997]
Connection_host = none