Reporting

Saved splunk failed to get current user context

dlaperle
Engager

I have this error in the scheduler.log, and the scheduled searches doesn't seems to run at all. I have nothing in «Recent» even if the job is scheduled correctly.

The exact line is :

04-22-2010 10:06:22.333 WARN SavedSplunker - Saved splunk failed to get current user context

I have this multiple times in the log!

thanks

Tags (1)

dlaperle
Engager

I rebooted the server (entirely not only splunk) and it worked. It was a fresh server on which i had modified some network information, so maybe there was something wrong about it and the running instance of splunk.

Rebooting fixed the problem and now i can see my things running!

thanks

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!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

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 ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...