Facebook
Twitter-
We value your experience with Plesk during 2024
Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
Please take this short survey:
https://pt-research.typeform.com/to/AmZvSXkx -
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
-
We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.
Issue Problem with [Grafana] Update
- Thread starter groove21
- Start date
What kind of update is being attempted? Updating Grafana only? The operating system? Plesk?
Regarding Grafana it seems that there was recently a repository update going on. It is thinkable that the symptoms described here are caused by that. The update however is through, so it should work correctly now if that was the root cause. Could you please check it on your end and report back here?
Actually in this case I recommend to open a support ticket, because it is unclear what the root cause is. It will need to be checked on the server. When opening the ticket, please mention the URL to this thread in it and please also IDs [EXTPLESK-4461] and [PPS-14129], because this here could be linked to another, similar issue.
support.plesk.com
How to get support directly from Plesk?
Question How to get support directly from Plesk? Answer Lease-type Plesk licenses purchased directly from Plesk running on supported Plesk version include full free support. Perpetual-type license...
support.plesk.com
I´m unable to open a ticket because the form says my license isn´t accepted:
Use Plesk License Key (e.g. PLSK.XXXXXXXX.XXXX) or Extension License Key purchased from Plesk online store (e.g. EXT.XXXXXXXX.XXXX). You can find your License Key using the following guide
Invalid Entry. Only alphanumeric characters and dots are allowed.
I bought the license from Hetzner.
Is there a need to open a ticket and to pay for it?
Use Plesk License Key (e.g. PLSK.XXXXXXXX.XXXX) or Extension License Key purchased from Plesk online store (e.g. EXT.XXXXXXXX.XXXX). You can find your License Key using the following guide
Invalid Entry. Only alphanumeric characters and dots are allowed.
I bought the license from Hetzner.
Is there a need to open a ticket and to pay for it?
Btw: Solutions from Issue - Updating packages is giving a apt error (File has unexpected size) and Question - update failed are not working.
You have a free 30 day trial period, and, yes, reseller licences are cheaper then then real thing, but then the reseller should also provide support. In licenses obtained from Plesk, support is included. For users who would like to have Plesk support, but have a reseller license, the support subscription is available.
ChristophRo
Regular Pleskian
Seems like they uploaded an incomplete/broken Grafana package into their Debian 11 repository yesterday, causing servers to fail when performing updates.
I've got plenty of these mails as well from our servers.
Plesk seems to have updated normally at 6:35 as usual, but a manual Recheck now resulted in "The System Updates tool is already installing updates in automatic mode. Please try later." which is at least misleading.
apt-get update shows a message similar to OP's but with the 1298 on the other side:
Code:
Get:12 https://autoinstall.plesk.com/grafana/deb stable/main amd64 Packages [1,089 B]
Err:12 https://autoinstall.plesk.com/grafana/deb stable/main amd64 Packages
File has unexpected size (1298 != 1089). Mirror sync in progress? [IP: 2a02:6ea0:c700::11 443]HOWEVER:
apt-get upgrade shows a lot of updates:
Code:
# apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
libpng12-0
Use 'apt autoremove' to remove it.
The following packages have been kept back:
linux-image-amd64
The following packages will be upgraded:
apache2 apache2-bin apache2-data apache2-utils bind9 bind9-dnsutils bind9-host bind9-libs bind9-utils bind9utils
curl dnsutils git git-man grub-common grub-pc grub-pc-bin grub2-common imagemagick-6-common imagemagick-common
libapache2-mod-php7.4 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap libcurl3-gnutls libcurl4
libde265-0 libexpat1 libgnutls-openssl27 libgnutls30 libgssapi-krb5-2 libk5crypto3 libkrb5-3 libkrb5support0
libksba8 libmagickcore-6.q16-6 libmagickwand-6.q16-6 libpixman-1-0 libssl1.1 libtiff5 libvarnishapi2 libxml2
linux-libc-dev openssl php7.4-cgi php7.4-cli php7.4-common php7.4-curl php7.4-fpm php7.4-gd php7.4-json
php7.4-mbstring php7.4-mysql php7.4-opcache php7.4-phpdbg php7.4-readline php7.4-sqlite3 varnish
59 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 39.7 MB of archives.
After this operation, 82.9 kB disk space will be freed.whereas pum finds nothing:
Code:
# plesk sbin pum --update
2023-03-23 11:56:40 INFO: pum is called with arguments: ['--update']
2023-03-23 11:56:46 INFO: no packages to update
2023-03-23 11:56:47 INFO: pum completed successfullyThis is a security disaster. There are at least two important security updates in there (apache and ssl).
There is a problem with the update of grafana
From plesk interface there were 6 package to update
Selecting the others without grafana the update is ok
Updating only grafana the update fails:
2023-03-23 13:14:11 INFO: pum is called with arguments: ['--update', '--json', '--', 'grafana']
2023-03-23 13:14:12 INFO: updating packages: grafana
warning: /var/cache/yum/x86_64/7/plesk-ext-grafana/packages/grafana-8.5.21-1.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 2cf3c0c6: NOKEY
...
From : https://autoinstall.plesk.com/grafana/rpm/gpg.key
2023-03-23 13:14:13 ERROR: Didn't install any keys
2023-03-23 13:14:13 ERROR: Exited with returncode 1.
From plesk interface there were 6 package to update
Selecting the others without grafana the update is ok
Updating only grafana the update fails:
2023-03-23 13:14:11 INFO: pum is called with arguments: ['--update', '--json', '--', 'grafana']
2023-03-23 13:14:12 INFO: updating packages: grafana
warning: /var/cache/yum/x86_64/7/plesk-ext-grafana/packages/grafana-8.5.21-1.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 2cf3c0c6: NOKEY
...
From : https://autoinstall.plesk.com/grafana/rpm/gpg.key
2023-03-23 13:14:13 ERROR: Didn't install any keys
2023-03-23 13:14:13 ERROR: Exited with returncode 1.
The issue is only with the keys that needed time to sync. According to engineers syncing is completed and the issue should no longer occur.
Thank you for the feedback. I have forwarded this to the staff who was working on the fix so that they can look into it again.
Grafana issue is still not solved. It seems that some support engineers were not able to reproduce it while others said they reproduced and fixed it. We're still looking into the GPG key issue.
Here's the final status: Users who yesterday imported the "old" GPG key and updated Grafana manually will probably have seen the update notification again today. These users will need to import the latest GPG key once manually
# rpm --import https://autoinstall.plesk.com/grafana/rpm/gpg.key
then install the update again.
All others who saw the Grafana key issue yesterday but did not proceed should be able to update without further action since last night, because for them the matching key was already provided.
I am not sure whether the key issue yesterday is the cause for the intial post of this thread, so I'll leave this thread as not resolved.
# rpm --import https://autoinstall.plesk.com/grafana/rpm/gpg.key
then install the update again.
All others who saw the Grafana key issue yesterday but did not proceed should be able to update without further action since last night, because for them the matching key was already provided.
I am not sure whether the key issue yesterday is the cause for the intial post of this thread, so I'll leave this thread as not resolved.
Sergio Manzi
Regular Pleskian
Hello @Peter Debik !
I'm using Centos 7.9 and as of now I'm still getting the error:
Cheers!
I'm using Centos 7.9 and as of now I'm still getting the error:
Code:
Update failed.
Update utility stdout:
Loading mirror speeds from cached hostfile
* base: mirror.nl.datapacket.com
* epel: mirror.nl.leaseweb.net
* extras: mirror.nl.datapacket.com
* updates: mirror.wd6.net
Retrieving key from https://autoinstall.plesk.com/grafana/rpm/gpg.key
Update utility stderr:
2023-03-26 06:43:07 INFO: pum is called with arguments: ['--update', '--json', '--', 'grafana']
2023-03-26 06:43:13 INFO: updating packages: grafana
warning: /var/cache/yum/x86_64/7/plesk-ext-grafana/packages/grafana-8.5.21-1.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 2cf3c0c6: NOKEY
Importing GPG key 0x2CF3C0C6:
Userid : "Grafana Labs <[email protected]>"
Fingerprint: 0e22 eb88 e39e 1227 7a77 60ae 9e43 9b10 2cf3 c0c6
From : https://autoinstall.plesk.com/grafana/rpm/gpg.key
2023-03-26 06:43:15 ERROR: Didn't install any keys
2023-03-26 06:43:15 ERROR: Exited with returncode 1.Cheers!
Sergio Manzi
Regular Pleskian
OK: I've now manually updated the grafana rpm gpg key and then the upgrade worked!
That's odd, anyway, as in the above log you can clearly see:
That's odd, anyway, as in the above log you can clearly see:
Similar threads
