• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Grafana installed does not match extension version of Grafana

theunknownstuntman

New Pleskian
Server operating system version
Ubuntu 20.04.6 LTS
Plesk version and microupdate number
18.0.54 Update #4
Hi,

I have Plesk 18.0.54 Update #4 installed on a Ubuntu 20.04.6 LTS server, that was handed over to me. (I do not know its complete history).

I just saw in the Plesk Changelog Change Log for Plesk Obsidian
that Grafana was updated.

The extension seems to have been updated (1.4.9-291 = Grafana version 8.5.26), but when I open the application through
the extension, I see that version 9.4.3 of Grafana is running.

According to Grafana security release for CVE-2023-3128 this version is vulnerable.

Now my question. How does it come, that extension and application do not fit together? On my server only /usr/share/grafana/bin/grafana
is installed and reports to be version 9.4.3.

Can I update Grafana via apt, or do I risk to break the monitoring? A more recent version of the extension is not available, as it seems.

Final question: Where is grafana 8.5.26, that was allegedly installed? There is none on my machine :)
 
Grafana that comes with Plesk is version 8.5.26. If you have another version, it was self-maintained before.
 
Does the installation of the grafana extension include it's own version of grafana? On another server, where everything is working fine, it is shown as

grafana/stable,now 8.5.26 amd64 [installed]

where on the discussed server it says

grafana/now 9.4.3 amd64 [installed,local]

when I run "apt list grafana".

May I uninstall grafana via apt and reinstall the extension from Plesk to fix the issue? I appreciate any help. Thanks.
 
Yes, you can install Grafana via Plesk. It is an extension that can be installed from the "Extensions" menu.
 
Here a funny update to this issue. The server which refused to update Grafana, has now silently updated grafana to the latest version 10.1.5.

Another server has received the grafana extension update to version 1.5.1-1289 in Plesk, that should install grafana Version 10.1.5.
But when I open the Grafana application via the Plesk extension it still says version 8.5.26.

So it is the opposite. I do not understand what is going on here.... This server had the right version of Grafana, when I created the post....
 
I remember a case where some of these data were cached, and a few days later the correct data was shown. Could this also be the case here?
 
In between, nothing has changed on the server regarding the Grafana version. The only thing, that makes me wonder, is, that Plesk has not been updated automatically, since the last update failed in the end of october. In the beginning of november I updated the Plesk Panel manually to Obsidian 18.0.56. System updates are running fine.
 
Another server has received the grafana extension update to version 1.5.1-1289 in Plesk, [...]
Strange. Could you please also write OS version and Plesk version?

Here is an example from my Ubuntu 22 server,
Code:
# cat /etc/apt/sources.list.d/plesk-ext-grafana.list
deb [signed-by=/etc/apt/keyrings/plesk-ext-grafana.gpg] https://autoinstall.plesk.com/grafana/deb stable main
In other words, OS is also responsible for Grafana package update. If you open Index of /grafana/deb/pool ("deb" because of my example server), you will find Grafana 9.x and 10.x packages.

Probably, on your server exists an issue with PGP key (and it wasn't fixed automatically), if yes, there is a KB article with info how to fix it manually, https://support.plesk.com/hc/en-us/...h-message-NOKEY-Importing-GPG-key-0x2CF3C0C6-
 
Product version: Plesk Obsidian 18.0.56.4
OS version: Ubuntu 20.04 x86_64

I updated Grafana now manually by running "apt install grafana" to v10.1.5. No key was expired.

grafana/stable 10.1.5 amd64 [upgradable from: 8.5.26]

Strange, that this was not resolved automatically. What wonders me, is that the update was not flagged as a "focal-security" update.
 
Arrgh. After updating Grafana via apt, it can not be opened anymore.... what a mess.

grafana.log

logger=settings t=2023-12-12T14:59:44.35437133+01:00 level=warn msg="[Deprecated] The oauth_auto_login configuration setting is deprecated. Please use auto_login inside auth provider section instead."
logger=plugin.loader t=2023-12-12T14:59:44.542556921+01:00 level=warn msg="Plugin missing module.js" pluginID=input warning="Missing module.js, If you loaded this plugin from git, make sure to compile i
t."
logger=plugin.loader t=2023-12-12T14:59:44.543850762+01:00 level=warn msg="Skipping loading plugin due to problem with signature" pluginID=plesk-json-backend-datasource status=unsigned
logger=authn.service t=2023-12-12T14:59:50.009022345+01:00 level=warn msg="Failed to authenticate request" client=auth.client.generic_oauth error="[auth.oauth.state.missing] missing state cookie"
logger=user.sync t=2023-12-12T14:59:50.664139296+01:00 level=error msg="Failed to create user" error="user already exists" auth_module=oauth_generic_oauth auth_id=admin_viewer
logger=authn.service t=2023-12-12T14:59:50.664222003+01:00 level=warn msg="Failed to run post auth hook" client=auth.client.generic_oauth id= error="[user.sync.internal] unable to create user"
logger=user.sync t=2023-12-12T14:59:51.282886356+01:00 level=error msg="Failed to create user" error="user already exists" auth_module=oauth_generic_oauth auth_id=admin_viewer
logger=authn.service t=2023-12-12T14:59:51.282968722+01:00 level=warn msg="Failed to run post auth hook" client=auth.client.generic_oauth id= error="[user.sync.internal] unable to create user"
logger=user.sync t=2023-12-12T14:59:51.954835154+01:00 level=error msg="Failed to create user" error="user already exists" auth_module=oauth_generic_oauth auth_id=admin_viewer
logger=authn.service t=2023-12-12T14:59:51.955183757+01:00 level=warn msg="Failed to run post auth hook" client=auth.client.generic_oauth id= error="[user.sync.internal] unable to create user"
logger=user.sync t=2023-12-12T14:59:52.593225728+01:00 level=error msg="Failed to create user" error="user already exists" auth_module=oauth_generic_oauth auth_id=admin_viewer
logger=authn.service t=2023-12-12T14:59:52.593328664+01:00 level=warn msg="Failed to run post auth hook" client=auth.client.generic_oauth id= error="[user.sync.internal] unable to create user"
logger=user.sync t=2023-12-12T14:59:53.199174203+01:00 level=error msg="Failed to create user" error="user already exists" auth_module=oauth_generic_oauth auth_id=admin_viewer
logger=authn.service t=2023-12-12T14:59:53.199279053+01:00 level=warn msg="Failed to run post auth hook" client=auth.client.generic_oauth id= error="[user.sync.internal] unable to create user"
logger=user.sync t=2023-12-12T14:59:56.797950147+01:00 level=error msg="Failed to create user" error="user already exists" auth_module=oauth_generic_oauth auth_id=admin_viewer
logger=authn.service t=2023-12-12T14:59:56.798041482+01:00 level=warn msg="Failed to run post auth hook" client=auth.client.generic_oauth id= error="[user.sync.internal] unable to create user"
logger=user.sync t=2023-12-12T14:59:57.404212589+01:00 level=error msg="Failed to create user" error="user already exists" auth_module=oauth_generic_oauth auth_id=admin_viewer
logger=authn.service t=2023-12-12T14:59:57.404338127+01:00 level=warn msg="Failed to run post auth hook" client=auth.client.generic_oauth id= error="[user.sync.internal] unable to create user"
logger=user.sync t=2023-12-12T14:59:58.062602936+01:00 level=error msg="Failed to create user" error="user already exists" auth_module=oauth_generic_oauth auth_id=admin_viewer
logger=authn.service t=2023-12-12T14:59:58.062671036+01:00 level=warn msg="Failed to run post auth hook" client=auth.client.generic_oauth id= error="[user.sync.internal] unable to create user"
logger=user.sync t=2023-12-12T14:59:58.69865302+01:00 level=error msg="Failed to create user" error="user already exists" auth_module=oauth_generic_oauth auth_id=admin_viewer
logger=authn.service t=2023-12-12T14:59:58.698740877+01:00 level=warn msg="Failed to run post auth hook" client=auth.client.generic_oauth id= error="[user.sync.internal] unable to create user"
logger=user.sync t=2023-12-12T14:59:59.353257045+01:00 level=error msg="Failed to create user" error="user already exists" auth_module=oauth_generic_oauth auth_id=admin_viewer
logger=authn.service t=2023-12-12T14:59:59.353468257+01:00 level=warn msg="Failed to run post auth hook" client=auth.client.generic_oauth id= error="[user.sync.internal] unable to create user"
logger=alerting.evalContext t=2023-12-12T15:00:01.002980854+01:00 level=error msg="Alert Rule Result Error" ruleId=1 name="Apache & PHP-FPM memory usage" error="request handler error: plugin not found"
changingstateto=keep_state
logger=alerting.evalContext t=2023-12-12T15:00:03.00286217+01:00 level=error msg="Alert Rule Result Error" ruleId=2 name="nginx memory usage" error="request handler error: plugin not found" changingstat
eto=keep_state
logger=alerting.evalContext t=2023-12-12T15:00:06.003488609+01:00 level=error msg="Alert Rule Result Error" ruleId=3 name="Mail server memory usage" error="request handler error: plugin not found" chang
ingstateto=keep_state
logger=alerting.evalContext t=2023-12-12T15:00:07.003229512+01:00 level=error msg="Alert Rule Result Error" ruleId=7 name="Partition \"/boot\" utilization" error="request handler error: plugin not found
" changingstateto=keep_state
 

Attachments

  • Screenshot 2023-12-12 at 15.07.29.png
    Screenshot 2023-12-12 at 15.07.29.png
    82.6 KB · Views: 2
Back
Top