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!

Wondering How to Build Resiliency in the Cloud?

IT leaders are choosing Splunk Cloud as an ideal cloud transformation platform to drive business resilience,  ...

Updated Data Management and AWS GDI Inventory in Splunk Observability

We’re making some changes to Data Management and Infrastructure Inventory for AWS. The Data Management page, ...

Introducing the Splunk Community Dashboard Challenge!

Welcome to Splunk Community Dashboard Challenge! This is your chance to showcase your skills in creating ...