Deployment Architecture

ERROR IntrospectionGenerator:resource_usage - RU - pid=5070 procname='splunkd' Failed to read=as: Error 0

zugji
Path Finder

Hello
I see a lot of following error:
ERROR IntrospectionGenerator:resource_usage - RU - pid=5070 procname='splunkd' Failed to read=as: Error 0

Splunk Version: 6.1.4

Platform information:
SunOS 5.10 Generic_147441-12 i86pc i386 i86pc

Anybody any idea about this error?

Regards,
Christian

Tags (2)

jcrabb_splunk
Splunk Employee
Splunk Employee

Christian - This is a bug (SPL-83819) which has been fixed in Splunk 6.2. The error can be ignored.

Jacob
Sr. Technical Support Engineer

zugji
Path Finder

No, not yet. What I've just recognized is the fact that on thursday and monday we do have much more of these events,

0 Karma

snannapa
New Member

DId you even find out why this was happening? I see it in our implementation as well. Noticeably after enabling SSL for receiving.

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 ...

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...