Splunk Search

Lookup table does not exist

RicoSuave
Builder

I'm having an issue where one of my slavese is complaining about a lookup table that i have setup on my master. I get the error

[myslave] The Lookup table 'mylookuptable' does not exist. It is reference by configuration 'source::mysource'.

it seems like the slave is trying to locate the table locally, but i have never run into this issue before and i have many other lookups configured just on the master alone. I double checked all of my props.conf files in all the apps to make sure a configuration didn't accidentally exist. Any ideas?

Tags (1)

Ledion_Bitincka
Splunk Employee
Splunk Employee

We replicate the search head's search time configs (including lookup tables) to the search peers via a process called bundle replication. This happens at most every minute, so if this is a lookup table that you have just configured the error message should go away within a couple of minutes as the search heads configs are synced with those of the search peers. If this is happening for an existing lookup table then I would suggest you look in $SPLUNK_HOME/var/run/searchpeers//apps//lookups to see whether the file in question is there.

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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...