Getting Data In

Unable to backfill a summary index

anthonycopus
Path Finder

Hi,

I've been having no issues summary indexing previously, but suddenly when trying to do this (from the command line) I'm receiving the error:

"An instance of fill_summary_index is already running for app=nxtomo_jobs"

However, there is nothing in the splunk jobs which is running.
So, I checked using "ps aux | grep fill_summary_index" in the command line, and it DOES show something is running.

Therefore there is a lock file in nxtomo_jobs/log but how can I safely end whatever process is running here so I can continue to run my summary indexing backfilling? Other answers I've found say to delete the lock file, but this is in situations where nothing shows from the ps aux command.

Anyone know the best solution here?

0 Karma
1 Solution

anthonycopus
Path Finder

My own error, terminated the previous search from the command line therefore splunk didn't recognise it had ended. Deleted the lock file.

View solution in original post

0 Karma

anthonycopus
Path Finder

My own error, terminated the previous search from the command line therefore splunk didn't recognise it had ended. Deleted the lock file.

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!

Monitoring AI Agents with Splunk Observability Cloud

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...

[Puzzles] Solve, Learn, Repeat: Tiling

This puzzle (first published here) is based on finding groups of tessellated tiles (inspired by floor tiles I ...

SOK it to Me: Top 3 Benefits of Using Splunk Operator on Kubernetes that’ll Make ...

    Thursday, July 9, 2026  |  11:00AM–12:00PM PDT Duration: 1 hour (includes Q&A) Managing can feel like a ...