Dashboard cpu&ram empty

the cpu&ram graphics announced in the plexcerpt mailing just displays an empty graph.

Are you using app.plex.tv ?

Also server needs to be at least 1.15.2 or higher

i’m using plex.tv/web and app.plex.tv. server is 1.15.4.919.

Which model of Synology NAS do you have?
Are you running Plex natively or did you stick it into a Docker?

Same error for me with this configuration:

  • Plex Web 3.95.1 with https://app.plex.tv
  • Server version: 1.15.4.919
  • Synology native package, Intel 64 bit
  • Synology model 216+II

At first version CPU&Ram feature, 1.15.2 (I don’t remember) it’s work for Synology after the next update it never worked again.

native on ds3617xs

There is another related thread here:

We have sent some logs to @Moussa

still not visible with the just released 1.15.4.993 version

Same here
PLEX Version 1.15.5.994
Synology RS2416+ with DSM 6.2.1-23824 Update 6

CPU and RAM graphs don’t show for me either.

NAS: DS3617xs
DSM: 6.2.1-23824 Update 6
PMS 1.15.4.993
Plex web: 3.97.4

I’ve included the logs after going to the dashboard.Plex Media Server Logs_2019-05-03_16-40-49.zip (6.8 MB)

I’m seeing the same thing since I updated my NAS to the 6.2.x-x branch (it was fine on 6.2-x):
PMS: 1.15.5.994
NAS: DS3615xs (NB. not actual DS3615xs; XPEnology on HP Gen8 Microserver)
DSM: 6.2.2-24922

PMS: 1.15.4.994 (native for DSM)
App: 3.95.2
NAS: RS3614xs+
DSM: 6.2.1-23824 Update 6

No CPU or RAM stats.

Same here:

PMS: 1.15.4.994 (native for DSM)
App: 3.99.2 (via app.plex.tv)
NAS: DS916+
DSM: DSM 6.2.2-24922

Not fixed in PMS 1.15.6.1079

There was reply from @trumpy81 here:

In this post:

2 Likes

Thanks for that :+1:

Yet another situation where public visibility of the bug tracker/ticket system would have saved me testing and replying to a duplicate thread :roll_eyes:

Yep :wink: I have no idea why that information was not provided in either of the other threads on the same subject that have been around for a while…

Thank you for the reports. We are tracking this internally and will have a release notes entry when we have a fix.

3 Likes

This is not fixed in 1.15.8.1198