topic Re: No events ingested via HEC from Syslog Connector for Splunk (SC4S) in Getting Data In

No events ingested via HEC from Syslog Connector for Splunk (SC4S)

corti77 — Fri, 28 Jul 2023 11:42:07 GMT

Hi,

I had Splunk 9.05 and Syslog Conector for Splunk (SC4S) 1.110 running and working for months. I just realized that there are not events ingested via HEC since two weeks ago.

Both servers are in the same subnet, no firewall in between.

- Local firewall of the server has a rule for the incoming TCP 8088 traffic. (screenshot attached)

- HEC enabled (global settings screenshot attached)

- HEC token is correct. It is the same in the SC4S and Splunk.

- netstat in the Splunk server shows listening in the port 8088. (attached)

- ping from SC4S to Splunk and curl on port splunk:80 works fine, if I do port splunk:8088 it throws a timeout. (attached)

- local firewall in SC4S

firewall-cmd --list-all
drop (active)
target: DROP
icmp-block-inversion: yes
interfaces: eth0
sources:
services: ssh syslog syslog-tls
ports: 514/tcp 601/tcp
protocols:
forward: no
masquerade: no
forward-ports:
source-ports:
icmp-blocks: echo-reply echo-request port-unreachable time-exceeded
rich rules:

any idea what else I could check?

many thanks

Re: No events ingested via HEC from Syslog Connector for Splunk (SC4S)

corti77 — Fri, 28 Jul 2023 11:53:22 GMT

I also add a tcpdump taken from the SC4S, I forced pings and curls to 443, those seem to work.

all the other lines are the attempts to connect to 8088 , called radan-http (?)

Re: No events ingested via HEC from Syslog Connector for Splunk (SC4S)

corti77 — Fri, 28 Jul 2023 12:07:10 GMT

I attach the pcap from the splunk server. Clearly, they don't manage to establish the TCP handshake but I don't understand why... if there are no firewall rules involved, everything points to Splunk misconfiguration but I cannot see where.

Re: No events ingested via HEC from Syslog Connector for Splunk (SC4S)

corti77 — Fri, 28 Jul 2023 13:19:51 GMT

this is the output from the SC4S container. I created a new token to be sure, still the same issue.

/opt/sc4s$ docker logs SC4S
curl: (7) Failed to connect to splunk.xx.yy port 8088: Connection timed out
SC4S_ENV_CHECK_HEC: Invalid Splunk HEC URL, invalid token, or other HEC connectivity issue index=main. sourcetype=sc4s:fallback
Startup will continue to prevent data loss if this is a transient failure.

syslog-ng checking config
sc4s version=1.110.1
sc4s versions <2.0.0 are depreated please review and follow upgrade docs
starting goss
starting syslog-ng