Splunk Search

Could not load lookup = lookup_table Indexer Instance

erlindemberg
Explorer

Hello, I would like to request help.

All searches that I do in my indexer, whether through search reporting or some dashboard, show the message "Could not load lookup = lookup_table".

The search is still being performed and this error only occurs in my indexer instance.

How can I be solving this problem?

Tags (1)
0 Karma

nickhills
Ultra Champion

Is this a distributed deployment (ie seperate search heads and indexers) or a single server deployment (combined search & index server)

The way you have phrased it makes it sound like its distributed, in which case you should not be using your indexers for searching.

This message often occurs because a lookup is missing, (or is permissioned wrong).

-OR-

If you mean that you are running this search on a SH, but the indexers are reporting the error it could well be because the lookup is too big, and is not being distributed in the search bundle.

Look for errors in _internal which contain "ERROR DistributedBundleReplicationManager "

If my comment helps, please give it a thumbs up!
0 Karma

erlindemberg
Explorer

My instances are separate search / indexer / heavy.

0 Karma

nickhills
Ultra Champion

So where do you see the error?
When Searching from the SH?

If my comment helps, please give it a thumbs up!
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 ...