Resolved monitoring 2.5.9 stop working on my plesk server NEED DOWNGRADE

[nikketrikke]

Server operating system version

Ubuntu 20.04

Plesk version and microupdate number

Plesk Obsidian v18.0.49_build1800230110.16

monitoring 2.5.9 stop working on my plesk server
An unexpected error occurred
how can i downgrade to 2.5.8 version? via ssh
also grafana is updated to last version (even if i choose to not update it!!!)
thanks

 

[Maarten]

Hi,

I'm afraid that it's not possible to downgrade extensions.

Are there any related errors in /var/log/plesk/panel.log?

 

[4matltd]

I have the same problem to all my servers

Here is the last log

Apr 09 23:14:48 server.example.com grafana-server[22147]: logger=alerting.evalContext t=2023-04-09T23:14:48.87+0300 lvl=eror msg="Alert Rule Result Error" ruleId=35 name="Real memory usage" error="request handler response error {invalid status code. status: 500 Internal Server Error A <nil> [] [] 0xc000e6be30}" changingstateto=keep_state
Apr 09 23:15:01 server.example.com grafana-server[22147]: logger=alerting.evalContext t=2023-04-09T23:15:01.89+0300 lvl=eror msg="Alert Rule Result Error" ruleId=28 name="Apache & PHP-FPM memory usage" error="request handler response error {invalid status code. status: 500 Internal Server Error A <nil> [] [] 0xc001acb3b0}" changingstateto=keep_state
Apr 09 23:15:01 server.example.com grafana-server[22147]: logger=alerting.evalContext t=2023-04-09T23:15:01.89+0300 lvl=eror msg="Alert Rule Result Error" ruleId=32 name="Plesk memory usage" error="request handler response error {invalid status code. status: 500 Internal Server Error A <nil> [] [] 0xc0018374d0}" changingstateto=keep_state
Apr 09 23:15:03 server.example.com grafana-server[22147]: logger=alerting.evalContext t=2023-04-09T23:15:03.87+0300 lvl=eror msg="Alert Rule Result Error" ruleId=34 name="Partition \"/boot\" utilization" error="request handler response error {invalid status code. status: 500 Internal Server Error A <nil> [] [] 0xc0014cb2c0}" changingstateto=keep_state
Apr 09 23:15:03 server.example.com grafana-server[22147]: logger=alerting.evalContext t=2023-04-09T23:15:03.87+0300 lvl=eror msg="Alert Rule Result Error" ruleId=29 name="nginx memory usage" error="request handler response error {invalid status code. status: 500 Internal Server Error A <nil> [] [] 0xc0014cbd10}" changingstateto=keep_state
Apr 09 23:15:06 server.example.com grafana-server[22147]: logger=alerting.evalContext t=2023-04-09T23:15:06.89+0300 lvl=eror msg="Alert Rule Result Error" ruleId=30 name="Mail server memory usage" error="request handler response error {invalid status code. status: 500 Internal Server Error A <nil> [] [] 0xc001872de0}" changingstateto=keep_state
Apr 09 23:15:09 server.example.com grafana-server[22147]: logger=alerting.evalContext t=2023-04-09T23:15:09.87+0300 lvl=eror msg="Alert Rule Result Error" ruleId=31 name="MySQL memory usage" error="request handler response error {invalid status code. status: 500 Internal Server Error A <nil> [] [] 0xc000c67d40}" changingstateto=keep_state
Apr 09 23:15:11 server.example.com grafana-server[22147]: logger=alerting.evalContext t=2023-04-09T23:15:11.88+0300 lvl=eror msg="Alert Rule Result Error" ruleId=35 name="Real memory usage" error="request handler response error {invalid status code. status: 500 Internal Server Error A <nil> [] [] 0xc001130810}" changingstateto=keep_state
Apr 09 23:15:12 server.example.com grafana-server[22147]: logger=alerting.evalContext t=2023-04-09T23:15:12.87+0300 lvl=eror msg="Alert Rule Result Error" ruleId=33 name="Partition \"/\" utilization" error="request handler response error {invalid status code. status: 500 Internal Server Error A <nil> [] [] 0xc000eb9470}" changingstateto=keep_state
Apr 09 23:15:14 server.example.com grafana-server[22147]: logger=alerting.evalContext t=2023-04-09T23:15:14.87+0300 lvl=eror msg="Alert Rule Result Error" ruleId=36 name="Swap usage" error="request handler response error {invalid status code. status: 500 Internal Server Error A <nil> [] [] 0xc0010dbd10}" changingstateto=keep_state

 

[MartinT]

Hi,

I had a similar problem. My solution was to update to Plesk v18.0.51. At the change log is at the bug-fix for monitoring something about empty databaselines, on MariaDB with empty lines.

Was fighting for two days about this issue, a backup a couple of hours and afterwards the update, gave the solution. I think the update at its own would hlep.

 

[4matltd]

Thank you! the solution is to update to Plesk v18.0.51

 

[Deleted member 209767]

We have 5 servers and 2 of them are still having this issue because we're running CentOS and Plesk update is not available... The 3 others were able to update because we're on AlmaLinux. Any solution besides updating Plesk? Yes I know CentOS is EOL

Monitoring was working perfectly last week, then it suddenly stopped working. But now Plesk monitoring is broken, it shows a white page with the message "An unexpected error occurred"

There are no errors in /var/log/plesk/panel.log

 

[AYamshanov]

Hi everyone,
Could you please post OS, Plesk, Monitoring and Grafana (an as extension and as a software) versions from the server(s) with issue?

An example from my server (but without the issue):

# plesk version
Product version: Plesk Obsidian 18.0.51.1
OS version: Ubuntu 22.04 aarch64
Build date: 2023/04/04 10:00
Revision: 5f28ac65ab7698d3411bcb7b25e11dabc0d59dd9

# cd /usr/local/psa/admin/plib/modules/; grep '<version' monitoring/meta.xml grafana/meta.xml
monitoring/meta.xml: <version>2.5.9</version>
grafana/meta.xml: <version>1.4.3</version>

# grafana-server -v
Version 8.5.21 (commit: f5c82deccc, branch: HEAD)

 

[Ohya]

Same here monitoring stop working in

18.0.49
With debug enabled just get this line in log:

plesk starting: filter 86, stdin:


In my case upgrade all solve the issue.

 

[Deleted member 209767]

Hi everyone,
Could you please post OS, Plesk, Monitoring and Grafana (an as extension and as a software) versions from the server(s) with issue?

[root ~]# plesk version
Product version: Plesk Obsidian 18.0.41.1
OS version: CentOS 8.5.2111 x86_64
Build date: 2022/02/07 23:00
Revision: 8cecdf6536124408249dd8ea2063e3e6f632ba5b

[root ~]# cd /usr/local/psa/admin/plib/modules/; grep '<version' monitoring/meta.xml grafana/meta.xml
monitoring/meta.xml: <version>2.5.9</version>
grafana/meta.xml: <version>1.3.7</version>

[root modules]# grafana-server -v
Version 8.5.21 (commit: f5c82deccc, branch: HEAD)

 

[nikketrikke]

YES upgrading Plesk mate the motinoring works again !!!!!

 

[AYamshanov]

Product version: Plesk Obsidian 18.0.41.1
OS version: CentOS 8.5.2111 x86_64
[...]

Thank you, @ungov! These versions of the components should work to each other without issues. I will try to reproduce the issue to report it to the team.

 

[JVG]

Can confirm the issue also present on Debian 9.13 Plesk 18.0.44.3 (same monitoring and grafana version as @ungov).

Everything ok on Debian 10.13 Plesk 18.0.51.1.

 

[Peter Debik]

These two articles will help:

https://support.plesk.com/hc/en-us/articles/13303695941783

and
https://support.plesk.com/hc/en-us/articles/13786411637655

 

[AYamshanov]

Yep, the Plesk Support got ahead of me, the quite similar issue is described in the KB article; confirmed as a bug EXTPLESK-4511.

 

[Hangover2]

For us an upgrade to 18.0.51.1 is no option yet because this version has serious bugs that we cannot burden onto our clients.
All our live servers on version 18.0.49.2 lost monitoring out of nowhere.

Whatever the reason is (external or extension) please fix it ASAP. Just telling the clients to upgrade to the latest unstable version of Plesk cannot be the answer.

 

[Maarten]

There is an update available for the Monitoring extension:

Monitoring 2.5.10 (13 April 2023)

• [-] On Plesk 18.0.49 and earlier, the extension no longer crashes with the "An unexpected error occurred" error. (EXTPLESK-4511)

 

[JVG]

Confirmed everything back to normal on Debian 9.13 Plesk Plesk 18.0.44.3:

monitoring/meta.xml: <version>2.5.10</version>
grafana/meta.xml: <version>1.3.7</version>

 

[Deleted member 209767]

Issue fixed on all servers now, thanks