Splunk Search

Lookup table errors after 6.0 upgrade

vathanal
New Member

Hi, after upgrading our search head from 4.3 to 6.0, we are getting error messages when doing custom searches.
The errors are reported from all the search peers (ex: awssplunkindex.yp1.ca). The search peers are enabled and replication is successful. The search peers are version 5.0 or 4.3.

[awssplunkindex.yp1.ca] The lookup table 'http_status_lookup' does not exist. It is referenced by configuration 'apache'.
[awssplunkindex.yp1.ca] The lookup table 'logMapping_mobile' does not exist. It is referenced by configuration '24hrPC-cgi'.
[awssplunkindex.yp1.ca] The lookup table 'logMapping_mobile' does not exist. It is referenced by configuration '24hrPC-telus'.

I tried disabling/enabling the search peers and restarting them, without success.

Thank you for your help

Tags (3)
0 Karma

bmas10
Explorer

I am having the same issue. I suspect you followed the advice on http://answers.splunk.com/answers/35267/very-large-lookup-tables-exceeding-2gb-bundle-size
which removes the lookups from your replication bundle. This is the desired behavior, but then automatic lookups fail. I am trying to find out how to enable automatic lookups only on Search Heads and not get the search error messages.

0 Karma
Get Updates on the Splunk Community!

Observability | Use Synthetic Monitoring for Website Metadata Verification

If you are on Splunk Observability Cloud, you may already have Synthetic Monitoringin your observability ...

More Ways To Control Your Costs With Archived Metrics | Register for Tech Talk

Tuesday, May 14, 2024  |  11AM PT / 2PM ET Register to Attend Join us for this Tech Talk and learn how to ...

.conf24 | Personalize your .conf experience with Learning Paths!

Personalize your .conf24 Experience Learning paths allow you to level up your skill sets and dive deeper ...