Security

Seeing errors related to Unix (*NIX) app's interfaces.sh

asleeis
Path Finder

Anyone know what this is? When I run the interfaces.sh script manually, I do not get any errors. But I'm seeing current and regular errors when looking at the "_internal" index for "ERROR" log_level.

"could not lookup DNS configuration info service: (ipc/send) invalid destination port"

That's the error message... pretty much 2 every minute.

Anyone know what this is and how to stop it. I don't know what this may be affecting in the reports, etc. But things seem to work. Not entirely sure. But I don't like seeing errors in stuff.

Thanks, -Alex

Tags (1)
0 Karma

rcarragher
New Member

Did anyone move past this? I'm on Mac OSX Server 10.6.8 and having the same exact problem as described above.

0 Karma

V_at_Splunk
Splunk Employee
Splunk Employee

Alex, please file a support issue, and provide the following information:

  • UNIX flavor (little birdie tells me it's Mac OS X), and version (on Mac, find with sw_vers).
  • does error happen if you run script in background? in background in a loop? I.e., for dummy in /usr/bin/*; do /v-p4/current/cfg/bundles/unix/bin/interfaces.sh; done &
  • run script with --debug option; a file like debug--interfaces.sh--Fri_Jan__7_16-08-14_PST_2011 will appear in directory where script is found. Please attach this file.
  • tell them to assign issue to Vainstein

Thank you.

0 Karma
Get Updates on the Splunk Community!

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

🔐 Trust at Every Hop: How mTLS in Splunk Enterprise 10.0 Makes Security Simpler

From Idea to Implementation: Why Splunk Built mTLS into Splunk Enterprise 10.0  mTLS wasn’t just a checkbox ...