Join the Conversation
- Find Answers
- :
- Using Splunk
- :
- Other Using Splunk
- :
- Reporting
- :
- SavedSplunker - Max alive instance count=1 reached...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
We are running Splunk v. 7.0.1
We are getting the following warning on our search heads
"Max alive instance_count=1 reached for saved savedsearch_id="user;search;SearchName"
What does it mean and how to correct this issue?
Thank you!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This error is generated when you have a saved search that is scheduled to run on a recurring basis and Splunk tries to start the search on schedule but discovers that a previous instance of this search is still running. For example, let's say you were to save a query that takes an hour to complete and schedule it to run every ten minutes. Splunk would start the first iteration and then try to start another iteration ten minutes later, but it would see that the first iteration was still running - so it would generate this error message and not start the second iteration. It will generate one of these messages every time it tries to start the saved search and discovers that a previous instance is still running.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This error is generated when you have a saved search that is scheduled to run on a recurring basis and Splunk tries to start the search on schedule but discovers that a previous instance of this search is still running. For example, let's say you were to save a query that takes an hour to complete and schedule it to run every ten minutes. Splunk would start the first iteration and then try to start another iteration ten minutes later, but it would see that the first iteration was still running - so it would generate this error message and not start the second iteration. It will generate one of these messages every time it tries to start the saved search and discovers that a previous instance is still running.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@elliotproebstel, thank you so much for the explanation.
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Announcing Modern Navigation: A New Era of Splunk User Experience
Observability Simplified: Combining User Experience, Application Performance & ...
Event Series May & June: From Network Visibility to Service Intelligence
