Installation

Cannot delete, move, or clone Saved Searches after upgrade to 5.0

slierninja
Communicator

We just upgraded to Splunk 5.0 and all of our upgraded saved searches and reports can no longer be deleted or moved via SplunkWeb. Why do we have to remove or move them manually from the server?

We also cannot clone our existing saved searches or reports (as an admin we receive: `Encountered the following error while trying to clone: [HTTP 404] Viewstate object not found; view= viewstate=oflqsidy`*).

If we create a new saved search or report - we have access to delete/move and can properly clone without any issues. This seems to be an upgrade issue.

1 Solution

slierninja
Communicator

Turns out that this issue has nothing to do with upgrading - I couldn't delete or move because these searches were imported via an application package (*.spl) and were located in the /default directory instead of the /local directory. Once I moved the saved search config from the /default path to /local/savedsearches.conf I was then able to delete them via Splunk Web - this is just my lack of understanding of what is user-manageable versus system-manageable.

The clone problem exists because the Viewstate ID (vsid) wasn't present in the viewstates.conf. You can either add an empty viewstate or copy the source state by doing the following:

viewstates.conf

#...
[*:oflqsidy]
#...

Once I added the vsid to the viewstates.conf in the /local path, I was able to properly clone.

View solution in original post

carmackd
Communicator

another option is to simply go into the savedsearches.conf for the search in question and delete the vsid attribute.

slierninja
Communicator

Turns out that this issue has nothing to do with upgrading - I couldn't delete or move because these searches were imported via an application package (*.spl) and were located in the /default directory instead of the /local directory. Once I moved the saved search config from the /default path to /local/savedsearches.conf I was then able to delete them via Splunk Web - this is just my lack of understanding of what is user-manageable versus system-manageable.

The clone problem exists because the Viewstate ID (vsid) wasn't present in the viewstates.conf. You can either add an empty viewstate or copy the source state by doing the following:

viewstates.conf

#...
[*:oflqsidy]
#...

Once I added the vsid to the viewstates.conf in the /local path, I was able to properly clone.

Get Updates on the Splunk Community!

Optimize Cloud Monitoring

  TECH TALKS Optimize Cloud Monitoring Tuesday, August 13, 2024  |  11:00AM–12:00PM PST   Register to ...

What's New in Splunk Cloud Platform 9.2.2403?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.2.2403! Analysts can ...

Stay Connected: Your Guide to July and August Tech Talks, Office Hours, and Webinars!

Dive into our sizzling summer lineup for July and August Community Office Hours and Tech Talks. Scroll down to ...