Cron <psaadm@....> /opt/psa/admin/bin/php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/wp-toolkit/scripts/maintenance.php' > /dev/null

[theunknownstuntman]

Server operating system version

Ubuntu 20.04 x86_64

Plesk version and microupdate number

Plesk Obsidian 18.0.51.1

Since yesterday, I receive on all my Plesk servers, the following error message. They are running different ubuntu flavors (Ubuntu 20.04 LTS, Ubuntu 16.04 LTS).
For the 20.04 Ubuntu Servers, the most recent version of Plesk is installed.
Product version: Plesk Obsidian 18.0.51.1
OS version: Ubuntu 20.04 x86_64
Build date: 2023/04/04 10:00
Revision: 5f28ac65ab7698d3411bcb7b25e11dabc0d59dd9

I use WP-Toolkit 6.1.3-7115, which is part of the Plesk installation.

Error message:

[2023-04-06 14:32:01.998] ERR [extension/wp-toolkit] An error occurred during update of vulnerability database: Vulnerability changes does not contain
[2023-04-06 14:32:02.001] ERR [extension/wp-toolkit] Could not update vulnerabilities database: Vulnerability changes does not contain

I have searched on my server, and can only find the following references:

/var/log/plesk/panel.log:[2023-04-06 04:38:01.753] 2266853:642e30896dec5 ERR [extension/wp-toolkit] Could not update vulnerabilities database: Vulnerability changes does not contain
/var/log/plesk/panel.log:[2023-04-06 05:38:02.501] 2279034:642e3e9a1c7f3 ERR [extension/wp-toolkit] Could not update vulnerabilities database: Vulnerability changes does not contain
/var/log/plesk/panel.log:[2023-04-06 06:38:02.957] 2300045:642e4caa133c4 ERR [extension/wp-toolkit] Could not update vulnerabilities database: Vulnerability changes does not contain
/var/log/plesk/panel.log:[2023-04-06 07:38:02.254] 2312327:642e5ab9c6d9c ERR [extension/wp-toolkit] Could not update vulnerabilities database: Vulnerability changes does not contain

Has anyone experienced the same? And found a solution? Thanks.

 

[woocommerce-premium]

Same Problem here with Almalinux. The most recent version of Plesk is installed, too.

 

[mitchellvanbijleveld]

Seeing the same message. I don't have a solution for you (yet).

 

[Peter Debik]

@custer Question for you?

 

[theunknownstuntman]

Unfortunately the error still exists. In Plesk Log browser I see the following message.



There seems to be an network issue, as tracepath says "Too many hops: pmtu 1500"
Does this help to resolve the issue?

tracepath vdb.wp-toolkit.plesk.com
 1?: [LOCALHOST]                        0.008ms pmtu 1500
 1:  ..................................                                    0.391ms
 1:  ....................................                                  0.297ms
 2:  2a00:11c0:47:3::fa                                    0.519ms asymm  4
 3:  nug-b2-link.ip.twelve99.net                           0.403ms asymm  5
 4:  ffm-bb1-v6.ip.twelve99.net                            3.859ms asymm  8
 5:  datacamp-ic357608-ffm-b5.ip.twelve99-cust.net         3.606ms asymm  8
 6:  datacamp-ic337377-ffm-b5.ip.twelve99-cust.net         3.691ms asymm  8
 7:  vl224.fra-eq8-dist-2.cdn77.com                        3.940ms asymm  9
 8:  no reply
 9:  no reply
10:  no reply
11:  no reply
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
18:  no reply
19:  no reply
20:  no reply
21:  no reply
22:  no reply
23:  no reply
24:  no reply
25:  no reply
26:  no reply
27:  no reply
28:  no reply
29:  no reply
30:  no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500

 

[Peter Debik]

Please contact support on it, maybe they can find out more directly on your server. To sign-in to support please go to https://support.plesk.com

If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-

 

[theunknownstuntman]

This issue has resolved itself without any doings on my side on all affected servers.