Installation

What would cause longer time span queries to auto close after data is migrated to a new host?

brianhunter99
New Member

We've had a standalone Splunk Enterprise 7.2.7 running for some time. There was a need to retire the old hosting server. So, we provisioned another RHEL6 server, the same as the existing server, installed Splunk Enterprise 7.2.7 and copied the Splunk install directory from the old server over the top of the install location on the new server. The basic application functionality appears to be ok, but queries spanning anything but a short length of time are auto-closing. I can't say that queries don't work at all, as described in the following examples.

Basic Example:
In the Splunk Enterprise - Resource Usage - Historical Charts - Memory, I can get a chart to display for 15 minutes and 60 minutes, but for a time range of the last four hours no data is displayed and it indicates auto close.

Another Example:
If I do a search for all events occurring the current month, it seems to start, but then stops on the first day, and there's the indication that it was auto-closed. The query results section of the display indicates that a couple thousand events were found to match, but it doesn't go any further.

Tags (2)
0 Karma
Get Updates on the Splunk Community!

Webinar Recap | Revolutionizing IT Operations: The Transformative Power of AI and ML ...

The Transformative Power of AI and ML in Enhancing Observability   In the realm of IT operations, the ...

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...