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

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

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...