Splunk Search

Indexer not responding.. Replication status is 'Failed'

nairri
New Member

A reboot cured the above issue( In title), which is far from ideal.

See the below lines logged in 'Splunkd.log' on the indexer before reboot of the server.

03-11-2013 17:31:04.383 +0000 WARN AggregatorMiningProcessor - Breaking event because limit of 256 has been exceeded
03-11-2013 17:31:12.973 +0000 ERROR ExecProcessor - message from "python /opt/splunk_uat/etc/apps/SplunkDeploymentMonitor-old1/bin/scripted_inputs/dm_backfill_factory.py" Traceback (most recent call last):
03-11-2013 17:31:12.973 +0000 ERROR ExecProcessor - message from "python /opt/splunk_uat/etc/apps/SplunkDeploymentMonitor-old1/bin/scripted_inputs/dm_backfill_factory.py" File "/opt/splunk_uat/etc/apps/SplunkDeploymentMonitor-old1/bin/scripted_inputs/dm_backfill_factory.py", line 161, in
03-11-2013 17:31:12.973 +0000 ERROR ExecProcessor - message from "python /opt/splunk_uat/etc/apps/SplunkDeploymentMonitor-old1/bin/scripted_inputs/dm_backfill_factory.py" next(token)
03-11-2013 17:31:12.973 +0000 ERROR ExecProcessor - message from "python /opt/splunk_uat/etc/apps/SplunkDeploymentMonitor-old1/bin/scripted_inputs/dm_backfill_factory.py" File "/opt/splunk_uat/etc/apps/SplunkDeploymentMonitor-old1/bin/scripted_inputs/dm_backfill_factory.py", line 67, in next
03-11-2013 17:31:12.973 +0000 ERROR ExecProcessor - message from "python /opt/splunk_uat/etc/apps/SplunkDeploymentMonitor-old1/bin/scripted_inputs/dm_backfill_factory.py" en = search(token, srch='status=1')

And a snippet after reboot

03-12-2013 13:47:22.800 +0000 ERROR ExecProcessor - message from "python /opt/splunk_uat/etc/apps/SplunkDeploymentMonitor-old1/bin/scripted_inputs/dm_backfill_factory.py" splunk.ResourceNotFound: [HTTP 404] https://127.0.0.1:8089/servicesNS/nobody/SplunkDeploymentMonitor/backfill/dm_backfill?sort_key=seed&...; [{'text': 'Application is disabled: SplunkDeploymentMonitor', 'code': None, 'type': 'ERROR'}]

Does anyone know whether the above errors can cause Indexer to slow down and replication status move to 'failed' state?
Thanks

Tags (1)
0 Karma

sivapuvvada
Path Finder

If you have huge csv's in the apps , you will see these kind of issues .
you need to disable search peers and enable back , If you still see the issue need to disable few apps on the SH .

0 Karma

pongc
Engager

Updating this thread with as I had the same issue. There was a large csv file located in the lookup folder in one of my apps, which was causing the replication bundle to balloon. Removing this file resolved the issue.

0 Karma

hugo_vazquez
Explorer

I had the same issue but instead of rebooting I just disabled the search peer and reenabled it, after that I got a successful replciation. Other than that I don't know what cause the issue.

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...