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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...