• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Nightly errors logged in panel.log - "Struct keys must be all strings"

Christopher McBride

Basic Pleskian
TITLE:
Nightly errors logged in panel.log - "Struct keys must be all strings"​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
OS ‪CentOS 6.10 (Final)‬
Product Plesk Onyx
Version 17.0.17 Update #55
​
PROBLEM DESCRIPTION:
I'm receiving nightly errors in my panel.log as follows.

There are no other lines before or after to explain what it is referring to, or where it is coming from. I suspect WP Toolkit?

[2018-09-01 03:26:59] ERR [1] error: Struct keys must be all strings
[2018-09-01 03:46:42] ERR [1] error: Struct keys must be all strings
[2018-09-02 03:45:57] ERR [1] error: Struct keys must be all strings
[2018-09-02 04:05:03] ERR [1] error: Struct keys must be all strings
[2018-09-03 03:51:55] ERR [1] error: Struct keys must be all strings
[2018-09-03 04:11:12] ERR [1] error: Struct keys must be all strings
[2018-09-04 03:43:27] ERR [1] error: Struct keys must be all strings
[2018-09-04 04:04:09] ERR [1] error: Struct keys must be all strings
[2018-09-05 03:27:04] ERR [1] error: Struct keys must be all strings
[2018-09-05 03:48:26] ERR [1] error: Struct keys must be all strings​
STEPS TO REPRODUCE:
Happens automatically each night​
ACTUAL RESULT:
Above errors logged​
EXPECTED RESULT:
No errors​
ANY ADDITIONAL INFORMATION:
​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Help with sorting out​
 
Looks like the issue is related to Mysql. I would suggest you try to repair Plesk database with:

# plesk repair db
# plesk repair installation
 
This is happening on two separate servers - one of which had the above commands run last week due to a MU causing a corrupt mysql.user table.

Any other suggestions?
 
Thanks - my licence is via a third party hosting company, so I cannot contact Plesk Support Team directly.

I'll try to raise a ticket at my side.
 
Back
Top