Deployment Architecture

Splunk Trooubleshooting indexer-segfault and perf.

muizash
Path Finder

I have 20 indexers and I have getting this error while running dmesg from one particular indexer:

[8459645.678270] perf: interrupt took too long (6226 > 6166), lowering kernel.perf_event_max_sample_rate to 32000
[18576493.545850] splunkd[130756]: segfault at 1a0 ip 00007fe66184ec80 sp 00007fe65a3fc828 error 4 in libpthread-2.17.so[7fe661845000+17000]
[18576793.065389] splunkd[177354]: segfault at 1a0 ip 00007fe66184ec80 sp 00007fe65c7fc828 error 4 in libpthread-2.17.so[7fe661845000+17000]
[18577124.490990] splunkd[27910]: segfault at 1a0 ip 00007fe66184ec80 sp 00007fe65c7fc828 error 4 in libpthread-2.17.so[7fe661845000+17000]

What could be the reason for this?

0 Karma

skalliger
Motivator

I'd suggest to open a support case about this and attach a diag. Hard to take a guess here without further information.

Skalli

0 Karma
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

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