Getting Data In

How can Splunk running as local user impact DNS?

daniel333
Builder

All,

I have a deployment server on centOS7 for a few months now. Out of nowhere it could not send data via it's outputs.conf to the indexers. I am getting name resolution errors in the logs. Running Splunk as ROOT how ever gets rid of the problem. Any ideas why this might be happening?

Tags (2)
0 Karma

KARANMALHOTRA
Path Finder

I am not clear on the exact issue but it looks like a problem with the user account on the server. You may want to check the privilges with your CentOS admins.

Are you able to resolve the Indexer names to get the IPs if you run a nslookup command while logged in as that user?

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...