Splunk Search

ERROR UserManagerPro - Could not get info for non-existent user="tesla"

bzsplunk54
New Member

ERROR UserManagerPro - Could not get info for non-existent user="tesla"
We have alerts setup to trigger .py scripts for some auto remediation tasks. As of today I am seeing a lot of these errors and not just for one user account and my scripts are not pulling a .gz files. Any ideas what these errors mean. I review all of the answers for other similar questions but the case doesn't match up. All of the users have active accounts and can login to the web interface. My authentication is over LDAP. Any suggestions would be greatly appreciated.

Tags (1)
0 Karma

dkeck
Influencer

Hi,
Did you delete this user and its still owning KO?

Have a look at this https://answers.splunk.com/answers/231922/after-deleting-an-old-user-how-to-troubleshoot-spl.html

0 Karma

bzsplunk54
New Member

Hello. No sir. These users are active users. One of the accounts being flagged is my own account.

0 Karma
Get Updates on the Splunk Community!

Upcoming Webinar: Unmasking Insider Threats with Slunk Enterprise Security’s UEBA

Join us on Wed, Dec 10. at 10AM PST / 1PM EST for a live webinar and demo with Splunk experts! Discover how ...

.conf25 technical session recap of Observability for Gen AI: Monitoring LLM ...

If you’re unfamiliar, .conf is Splunk’s premier event where the Splunk community, customers, partners, and ...

A Season of Skills: New Splunk Courses to Light Up Your Learning Journey

There’s something special about this time of year—maybe it’s the glow of the holidays, maybe it’s the ...