Question Small Plesk Errors in the logs - Config Related - Local or Plesk or OS?

[learning_curve]

Server operating system version

Ubuntu 24.04.1 LTS

Plesk version and microupdate number

18.0.65 #1

As per the the thread title. No visible traces of any of these and no performance penalties observed, but obviously, there's a mis-config (or two) somewhere.
Anybody whose had the same, but resolved them and / or anybody from Plesk care to comment?

The first one appears to be panel related, but only appears (in the logs) after server re-boots:

DB query failed: SQLSTATE[HY000] [2002] No such file or directory:
0: /opt/psa/admin/plib/Db/Adapter/Pdo/Mysql.php:79
Db_Adapter_Pdo_Mysql->query(string 'SET sql_mode = ''')
1: /opt/psa/admin/plib/CommonPanel/Application/Abstract.php:113
CommonPanel_Application_Abstract::initDbAdapter()
2: /opt/psa/admin/plib/Session/Helper.php:176
Plesk\Session\Helper::initStorage()
3: /opt/psa/admin/plib/auth.php:275
AutoPrepend->initUserSession()
4: /opt/psa/admin/plib/auth.php:188
AutoPrepend->run()
5: /opt/psa/admin/plib/auth.php:582

The second one, again appears to be panel related (FileManager) but it's daily, so cron generated (probably):

'/opt/psa/admin/bin/filemng' 'root' 'exec' '/' 'bash' '-c' 'timeout 5 /usr/bin/pro status --format json' '--allow-root' failed with code 124.
stdout:
stderr:

The third is directly related to the second, but is util_exec derived i.e. access to in this case.

proc_close() failed ['/opt/psa/admin/bin/filemng' 'root' 'exec' '/' 'bash' '-c' 'timeout 5 /usr/bin/pro status --format json' '--allow-root'] with exit code [124]

We have many things buttoned right down, in terms of access / rights etc hence these errors maybe collateral damage from our own config somehwere else, unrelated.
The fact that there's no visible evidence (other than these log entries) could easily make this a diminishing returns exercise, hence this post, just in case there's a short cut!
FWIW - The last two only started recently after updates for both Plesk and Ubuntu.

 

[learning_curve]

~~

'/opt/psa/admin/bin/filemng' 'root' 'exec' '/' 'bash' '-c' 'timeout 5 /usr/bin/pro status --format json' '--allow-root' failed with code 124.
stdout:
stderr:

~~

proc_close() failed ['/opt/psa/admin/bin/filemng' 'root' 'exec' '/' 'bash' '-c' 'timeout 5 /usr/bin/pro status --format json' '--allow-root'] with exit code [124]

These last 2 ^ are related to Ubuntu Advantage (as it was named previously) or Ubuntu Pro (as it is named now). Not sure that filemanager is anything but a messenger here, just relaying the issue and then its conclusion with a timeout code 124, that then prevents any further efforts. Utilising cli, it's really quite simple to: # /usr/bin/pro status --format json when SSH'd in as root, although usr/bin/pro is just a symlink to /usr/bin/ubuntu-advantage anyway & this can also be # /usr/bin/ubuntu-advantage status --format json when SSH'd in as root. Both, provide exactly the same values, without errors or warnings. There's no access rights or group permissions that could / would prevent access to any of the services or checks related to Ubuntu Advantage / Ubuntu Pro, so the current supposition, is that there's a variable (but one that can be altered) within: /lib/systemd/system/ua-reboot-cmds.service that's causing these errors/warnings, as these 2, are also only appearing in the logs now, after a specific time following re-boots. Not looked at the 1st one yet, but will do, pretty soon.

 

[FISHeR]

Hi. Thanks for reporting the problems. The last 2 errors are related. The bug ID is PPP-66830. Probably will be fixed in the upcoming version.