Question Incorrect total memory on Home dashboard after recovery

[Kaspar]

Server operating system version

Alma 9

Plesk version and microupdate number

Plesk 18.0.81

I recovered a backup to a different VM with different resources than the initial VM. All went well, expect that on the Home dashboard the total memory displays the memory of the older VM, rather than the actual memory available on the current VM (which is 16GB). It's a minor, cosmetic, issue of course. But I am still curious if this is solvable.

 

[LRLD]

Hi Kaspar,

this also happens when you adjust a VM's memory...



It would be nice to have the correct total.
Regards

LD

 

[tessa67]

Hi Kaspar, hi LRLD,

this is a known bug in the Monitoring extension: EXTPLESK-7999, described in this KB article:

https://support.plesk.com/hc/en-us/articles/30115973995799-Monitoring-widget-on-Plesk-server-s-home-page-does-not-detect-hardware-changes

Symptom there is the same as yours: after a hardware change the widget on the home page still shows the old RAM size, and the command that is supposed to detect hardware changes doesn't fix it. The suggested workaround is to delete the Monitoring cache folder (it's only a cache, Monitoring rebuilds it):

rm -rf /usr/local/psa/var/modules/monitoring/cache

Then reload the Plesk home page (a hard refresh, Ctrl+F5, so the browser doesn't show old data). If the number is still wrong, you can try the detection command from the KB once more and look again:

plesk ext monitoring --installation --detect-hardware-changes

Two more things:
- In the screenshot the graph itself already seems to scale to the real memory, only the "Total memory" label is stale. That fits a cached hardware value and not a problem with the collected data. That's my guess from the picture, though.
- A comment under the KB article says the bug still exists in Monitoring 2.10.1, so the workaround may not work for everybody, and you may have to repeat it after every hardware change. You can check your version with:

plesk bin extension --list | grep -i monitoring

If the cache deletion doesn't help, post your Monitoring version here and mention EXTPLESK-7999 when you report it, so it ends up on the right ticket.

Regards
Tessa