'Cpanel::MysqlUtils::Unprivileged' entries showing in db log

[morrow95]

Can someone explain these entries? Reason for showing, why, etc? I did find something here from cpanel, but it is listed as a note (not warning) and doesn't really go into details why it is happening. For what it is worth, I am using a remote db server with WHM... WHM is installed on one vm and the db server on another vm - not sure if that has something to do with it or not. Came across these while doing something else that required viewing the log and just want some clarification on them.

2023-03-01 20:30:05 5193590 [Warning] Access denied for user 'Cpanel::MysqlUtils::Unprivileged'@'xxx.xxx.xx.x' (using password: NO)

 

[cPRex]

Hey there! I think the link you found covers this pretty well - the format of "Cpanel::thing::thing" is an internal cPanel Perl module, so this is a cPane processing running against MySQL to check the version or status of the database system. It does seem odd that yours is a Warning instead of a Note, but since the module and output is the same, it's not something I'd be worried about.

 

[morrow95]

So could this have something to do with the fact I use a remote db server? Like this check is only checking locally rather than using the remote db profile to check?

 

[cPRex]

I suppose that's possible, although I'm not able to reproduce that on my end when setting up a remote MySQL server.

Could you run this command and let me know if there is any output?

rpm -qa | grep -i cpanel-mysql

If you're on version 106, I would not normally expect there to be any output from that command.

 

[morrow95]

No output - just goes back to the prompt. Yes, version 106.0.18 as of right now.

 

[cPRex]

I'm not completely sure where that would be coming from. Could you open a ticket with our team so we can check this out directly on the system?

 

[morrow95]

I'm okay with doing that, but always a little weary of doing so since this is 'in use' and by customers at that. From my experience in the past support has done more harm than good (downtime especially) when allowing access to everything. Any way to address this to a specific person that would understand the problem at hand?

 

[cPRex]

We don't really have a way to do that on our end. Our team would never do anything that would cause an outage for the server or a particular service. If we did find work that needed to be performed that may impact your users, we'd be sure to schedule that with you before performing any changes on the machine.