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!

Splunk Observability as Code: From Zero to Dashboard

For the details on what Self-Service Observability and Observability as Code is, we have some awesome content ...

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...

Shape the Future of Splunk: Join the Product Research Lab!

Join the Splunk Product Research Lab and connect with us in the Slack channel #product-research-lab to get ...