Monitoring Splunk

ERROR UserManagerPro user=“nobody” had no roles

paleewawa
Explorer

I'm seeing hundreds of these errors in the internal splunkd logs

01-16-2025 12:05:00.584 -0600 ERROR UserManagerPro [721361 SchedulerThread] - user="nobody" had no roles

Is this a known bug? I'm guessing knowledge objects with no owner defined is causing this. It's annoying because it fills the internal logs with noise. Is there an easy workaround without having to re-assign all objects without a valid owner/?

Labels (1)
0 Karma

joao_amorim
Communicator
0 Karma

Alex_S
New Member

We're seeing this error as well. Appears to have started after an upgrade from 9.1.6 to 9.2.4. Did you find any resolution or root cause? Does seem to be a bug as it started directly at upgrade time.

0 Karma

kiran_panchavat
Champion

@paleewawa  Better to assign the knowledge object to a user that has a role and give that role the quota it needs. 

Check this one for work around: https://community.splunk.com/t5/Security/ERROR-UserManagerPro-user-quot-system-quot-had-no-roles/m-p... 

Did this help? If yes, please consider giving kudos, marking it as the solution, or commenting for clarification — your feedback keeps the community going!
0 Karma
Get Updates on the Splunk Community!

.conf25 Community Recap

Hello Splunkers, And just like that, .conf25 is in the books! What an incredible few days — full of learning, ...

Splunk App Developers | .conf25 Recap & What’s Next

If you stopped by the Builder Bar at .conf25 this year, thank you! The retro tech beer garden vibes were ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...