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

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
Influencer

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

I hope this helps, if any reply helps you, you could add your upvote/karma points to that reply, thanks.
0 Karma
Get Updates on the Splunk Community!

Index This | How many sides does a circle have?

  March 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this ...

New This Month - Splunk Observability updates and improvements for faster ...

What’s New? This month, we’re delivering several enhancements across Splunk Observability Cloud for faster and ...

What's New in Splunk Cloud Platform 9.3.2411?

Hey Splunky People! We are excited to share the latest updates in Splunk Cloud Platform 9.3.2411. This release ...