Splunk Search

Help! Summary search process stuck ?

the_wolverine
Champion

I started running the fill_summary_index.py script and my session was interrupted. The summary backfill process never completed and I'm unable to restart it. I've tried restarting Splunk but it still thinks that a fill_summary_index instance is still running:

# ./splunk cmd python fill_summary_index.py 
Please enter the app that contains the search(es): search
An instance of fill_summary_index is already running for app=search

What can I do to cancel it and restart it?

Tags (1)

the_wolverine
Champion

Per Splunk Support, there's a fsidx*.lock file in the app directory that the script was run against. In my case, the search app:

/opt/splunk/etc/apps/search/log]# ls fsidxrlKD2v.lock

After deleting the lock file I was able to relaunch the summary backfill script.

the_wolverine
Champion

Thanks, Alex 😉

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