[PLUGIN] GPU Statistics

November 25, 20223 yr

16 minutes ago, b3rs3rk said:

@Joker169 @Slycooper

I just edited the support requirements in the first post of this thread. Of particular interest to me in both of your cases is your gpustat.cfg file. Look at Item 4 in the list for more info. Send it to me when you have the chance and I can review.

Thanks.

I appreciate you looking into this so quickly. Attached file contents, as requested. Going to be busy most of the day, but will check back periodically.

gpustat.cfg

Quote

1

November 26, 20223 yr

I'm having the N/A issue. Running 'cd /usr/local/emhttp/plugins/gpustat/ && php ./gpustatus.php' gave a fatal error. Running 6.11.5, latest Nvidia and GPU Stat plugin. Plugin was working fine since it came out. While running the commands i've attached, there was an Emby transcoding going on.

gpustat.txt gpustatus.txt nvidia-smi.xml

Quote

1

November 26, 20223 yr

Good day, plugin also stopped working for me.

root@Unraid:/usr/local/emhttp/plugins/gpustat# cd /usr/local/emhttp/plugins/gpustat/ && php ./gpustatus.php

Fatal error: Uncaught TypeError: Argument 1 passed to gpustat\lib\Main::getParentCommand() must be of the type int, string given, called in /usr/local/emhttp/plugins/gpustat/lib/Nvidia.php on line 90 and defined in /usr/local/emhttp/plugins/gpustat/lib/Main.php:161
Stack trace:
#0 /usr/local/emhttp/plugins/gpustat/lib/Nvidia.php(90): gpustat\lib\Main->getParentCommand('ffmpeg\x00-hide_ba...')
#1 /usr/local/emhttp/plugins/gpustat/lib/Nvidia.php(355): gpustat\lib\Nvidia->detectApplication(Object(SimpleXMLElement))
#2 /usr/local/emhttp/plugins/gpustat/lib/Nvidia.php(250): gpustat\lib\Nvidia->parseStatistics()
#3 /usr/local/emhttp/plugins/gpustat/gpustatus.php(63): gpustat\lib\Nvidia->getStatistics()
#4 {main}
  thrown in /usr/local/emhttp/plugins/gpustat/lib/Main.php on line 161
root@Unraid:/usr/local/emhttp/plugins/gpustat#

While the issue is resolved to revert to previous release, just delete the plugin and reinstall manually with below:

https://raw.githubusercontent.com/b3rs3rk/gpustat-unraid/6cf1b1e96bc8cd5c1cf7ac8fefea1271d8891e26/gpustat.plg

Edited November 26, 20223 yr by juan11perez

Quote

1
4

November 27, 20223 yr

I'm thinking of adding a GPU in my server, can this plugin work with 2 GPU's? (intel CPU and NVIDIA card)

thanks

Quote

November 27, 20223 yr

Just now, Nexius2 said:

I'm thinking of adding a GPU in my server, can this plugin work with 2 GPU's? (intel CPU and NVIDIA card)

No.

Quote

1

November 28, 20223 yr

Same thing here for me using rtx3060. Reverted back to previous release.

Quote

November 28, 20223 yr

8 hours ago, morpheus302 said:

Same thing here for me using rtx3060. Reverted back to previous release.

How did you rollback?

Quote

November 28, 20223 yr

1 hour ago, paulodell said:

How did you rollback?

1. Remove the current plugin

2. go to Plugins section > Install Plugins

3. Enter the below URL and Press "Install"

https://raw.githubusercontent.com/b3rs3rk/gpustat-unraid/6cf1b1e96bc8cd5c1cf7ac8fefea1271d8891e26/gpustat.plg

Quote

November 29, 20223 yr

Another one with the blank stats issue, if I stop my frigate docker container, the stats page works correctly, starting the docker container again makes it go blank. Reverting to the feb release as a work around is working.

Edited November 29, 20223 yr by Endolf

Quote

November 29, 20223 yr

Author

I see the issue, dumb mistake on my part. Will push a new release shortly that should fix the problem.

EDIT: Released, sorry!

Edited November 29, 20223 yr by b3rs3rk
New release

Quote

2

November 29, 20223 yr

Author

On 11/25/2022 at 11:11 AM, Joker169 said:

I appreciate you looking into this so quickly. Attached file contents, as requested. Going to be busy most of the day, but will check back periodically.

gpustat.cfg 563 B · 2 downloads

The only thing I'm missing is number 2 from that same list in the first post. I need to see what is getting spit out when the data collection actually runs.

Quote

November 29, 20223 yr

3 hours ago, b3rs3rk said:

I see the issue, dumb mistake on my part. Will push a new release shortly that should fix the problem.

EDIT: Released, sorry!

Fixed for me. Thank you!

Quote

1

November 30, 20223 yr

11 hours ago, b3rs3rk said:

The only thing I'm missing is number 2 from that same list in the first post. I need to see what is getting spit out when the data collection actually runs.

Sure thing:

{"clock":"442","fan":"N\/A","memclock":"715","memutil":"0%","memused":"0","power":"27W","powermax":"250","rxutil":"2","txutil":"0","temp":"32 \u00b0C","tempmax":"85 \u00b0C","util":"1%","vendor":"NVIDIA","name":"Tesla P100-PCIE-16GB","clockmax":"1328","memclockmax":"715","memtotal":"16384","encutil":"0%","decutil":"0%","pciemax":16000,"perfstate":"P0","throttled":"No","thrtlrsn":"","pciegen":3,"pciegenmax":3,"pciewidth":16,"pciewidthmax":16,"sessions":0,"uuid":"GPU-5ab1abde-31a8-eaa3-d02a-d75ad238d36d","plexusing":false,"plexmem":0,"plexcount":0,"jellyfinusing":false,"jellyfinmem":0,"jellyfincount":0,"handbrakeusing":false,"handbrakemem":0,"handbrakecount":0,"embyusing":false,"embymem":0,"embycount":0,"tdarrusing":false,"tdarrmem":0,"tdarrcount":0,"unmanicusing":false,"unmanicmem":0,"unmaniccount":0,"dizquetvusing":false,"dizquetvmem":0,"dizquetvcount":0,"ersatztvusing":false,"ersatztvmem":0,"ersatztvcount":0,"fileflowsusing":false,"fileflowsmem":0,"fileflowscount":0,"frigateusing":false,"frigatemem":0,"frigatecount":0,"deepstackusing":false,"deepstackmem":0,"deepstackcount":0,"nsfminerusing":false,"nsfminermem":0,"nsfminercount":0,"shinobiprousing":false,"shinobipromem":0,"shinobiprocount":0,"foldinghomeusing":false,"foldinghomemem":0,"foldinghomecount":0,"appssupp":["plex","jellyfin","handbrake","emby","tdarr","unmanic","dizquetv","ersatztv","fileflows","frigate","deepstack","nsfminer","shinobipro","foldinghome"]}

Quote

November 30, 20223 yr

Author

11 hours ago, Joker169 said:

Sure thing:

{"clock":"442","fan":"N\/A","memclock":"715","memutil":"0%","memused":"0","power":"27W","powermax":"250","rxutil":"2","txutil":"0","temp":"32 \u00b0C","tempmax":"85 \u00b0C","util":"1%","vendor":"NVIDIA","name":"Tesla P100-PCIE-16GB","clockmax":"1328","memclockmax":"715","memtotal":"16384","encutil":"0%","decutil":"0%","pciemax":16000,"perfstate":"P0","throttled":"No","thrtlrsn":"","pciegen":3,"pciegenmax":3,"pciewidth":16,"pciewidthmax":16,"sessions":0,"uuid":"GPU-5ab1abde-31a8-eaa3-d02a-d75ad238d36d","plexusing":false,"plexmem":0,"plexcount":0,"jellyfinusing":false,"jellyfinmem":0,"jellyfincount":0,"handbrakeusing":false,"handbrakemem":0,"handbrakecount":0,"embyusing":false,"embymem":0,"embycount":0,"tdarrusing":false,"tdarrmem":0,"tdarrcount":0,"unmanicusing":false,"unmanicmem":0,"unmaniccount":0,"dizquetvusing":false,"dizquetvmem":0,"dizquetvcount":0,"ersatztvusing":false,"ersatztvmem":0,"ersatztvcount":0,"fileflowsusing":false,"fileflowsmem":0,"fileflowscount":0,"frigateusing":false,"frigatemem":0,"frigatecount":0,"deepstackusing":false,"deepstackmem":0,"deepstackcount":0,"nsfminerusing":false,"nsfminermem":0,"nsfminercount":0,"shinobiprousing":false,"shinobipromem":0,"shinobiprocount":0,"foldinghomeusing":false,"foldinghomemem":0,"foldinghomecount":0,"appssupp":["plex","jellyfin","handbrake","emby","tdarr","unmanic","dizquetv","ersatztv","fileflows","frigate","deepstack","nsfminer","shinobipro","foldinghome"]}

If you look at the Dashboard page and open the Developer console of your browser are you getting any errors? Anything coming up in the UnRAID system log when accessing that page? Your diagnostics upload from before didn't show anything but I just want to be sure. Near as I can tell with all the information you gave me there really shouldn't be an issue.

Quote

November 30, 20223 yr

2 hours ago, b3rs3rk said:

If you look at the Dashboard page and open the Developer console of your browser are you getting any errors? Anything coming up in the UnRAID system log when accessing that page? Your diagnostics upload from before didn't show anything but I just want to be sure. Near as I can tell with all the information you gave me there really shouldn't be an issue.

The only errors in console tab were these:

[UPC_ENV] ✨ local Dashboard:539:27
Result: CA Background Scan Dashboard:753:11
This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see https://firefox-source-docs.mozilla.org/performance/scroll-linked_effects.html for further details and to join the discussion on related tools and features! Dashboard
Scroll anchoring was disabled in a scroll container because of too many consecutive adjustments (10) with too little total distance (0 px average, 0 px total). jquery.apexcharts.js:6:6213
Scroll anchoring was disabled in a scroll container because of too many consecutive adjustments (10) with too little total distance (0 px average, 0 px total). jquery.apexcharts.js:6:6213

Didn't seem anywhere related to the plugin

As far as the accessing page, this is from this morning from sys log:

Nov 30 02:04:55 Media  emhttpd: read SMART /dev/sdg
Nov 30 02:05:05 Media  emhttpd: read SMART /dev/sdj
Nov 30 02:05:25 Media  emhttpd: read SMART /dev/sdl
Nov 30 02:05:39 Media  emhttpd: read SMART /dev/sdd
Nov 30 02:06:13 Media  emhttpd: read SMART /dev/sdf
Nov 30 02:07:27 Media  emhttpd: read SMART /dev/sdi
Nov 30 02:07:51 Media  emhttpd: read SMART /dev/sdc
Nov 30 02:14:43 Media  emhttpd: read SMART /dev/sdn
Nov 30 02:35:16 Media  emhttpd: read SMART /dev/sdk
Nov 30 02:35:34 Media kernel: mdcmd (38): set md_write_method 1
Nov 30 02:35:34 Media kernel: 
Nov 30 03:27:13 Media  emhttpd: spinning down /dev/sdj
Nov 30 03:35:27 Media  emhttpd: spinning down /dev/sdn
Nov 30 03:35:34 Media kernel: mdcmd (39): set md_write_method 0
Nov 30 03:35:34 Media kernel: 
Nov 30 03:45:50 Media  emhttpd: read SMART /dev/sdn
Nov 30 03:50:35 Media kernel: mdcmd (40): set md_write_method 1
Nov 30 03:50:35 Media kernel: 
Nov 30 04:02:10 Media  emhttpd: read SMART /dev/sdj
Nov 30 04:21:59 Media  emhttpd: spinning down /dev/sdk
Nov 30 04:25:35 Media kernel: mdcmd (41): set md_write_method 0
Nov 30 04:25:35 Media kernel: 
Nov 30 05:23:55 Media  emhttpd: spinning down /dev/sdc
Nov 30 05:24:38 Media  emhttpd: spinning down /dev/sdn
Nov 30 05:25:27 Media  emhttpd: spinning down /dev/sdg
Nov 30 05:40:41 Media  emhttpd: spinning down /dev/sdj
Nov 30 05:53:48 Media  emhttpd: spinning down /dev/sdf
Nov 30 05:54:57 Media  emhttpd: spinning down /dev/sdl
Nov 30 06:00:59 Media  emhttpd: spinning down /dev/sdi
Nov 30 06:01:19 Media  emhttpd: spinning down /dev/sdd
Nov 30 08:00:03 Media  emhttpd: read SMART /dev/sdj
Nov 30 08:00:10 Media kernel: sd 1:0:8:0: [sdj] tag#7275 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Nov 30 08:00:10 Media kernel: sd 1:0:8:0: [sdj] tag#7275 Sense Key : 0x5 [current] 
Nov 30 08:00:10 Media kernel: sd 1:0:8:0: [sdj] tag#7275 ASC=0x21 ASCQ=0x0 
Nov 30 08:00:10 Media kernel: sd 1:0:8:0: [sdj] tag#7275 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Nov 30 08:00:10 Media kernel: critical target error, dev sdj, sector 3905203848 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Nov 30 08:00:10 Media kernel: BTRFS warning (device sdj1): failed to trim 1 device(s), last error -121
Nov 30 08:03:22 Media root: /var/lib/docker: 56 GiB (60147957760 bytes) trimmed on /dev/loop2
Nov 30 08:03:22 Media root: /mnt/cache: 282.4 GiB (303181410304 bytes) trimmed on /dev/mapper/nvme0n1p1
Nov 30 08:03:22 Media  sSMTP[40750]: Creating SSL connection to host
Nov 30 08:03:22 Media  sSMTP[40750]: SSL connection using TLS_AES_256_GCM_SHA384
Nov 30 08:03:22 Media  sSMTP[40750]: Authorization failed (535 5.7.8  https://support.google.com/mail/?p=BadCredentials e20-20020ac845d4000000b003a582090530sm862914qto.83 - gsmtp)
Nov 30 09:00:04 Media  emhttpd: spinning down /dev/sdj
Nov 30 09:53:08 Media  emhttpd: read SMART /dev/sdc
Nov 30 09:53:18 Media  emhttpd: read SMART /dev/sdd
Nov 30 09:53:40 Media  emhttpd: read SMART /dev/sdn
Nov 30 09:53:49 Media  emhttpd: read SMART /dev/sdl
Nov 30 09:53:58 Media  emhttpd: read SMART /dev/sdi
Nov 30 09:55:06 Media  emhttpd: read SMART /dev/sdg
Nov 30 09:55:23 Media  emhttpd: read SMART /dev/sdf
Nov 30 11:07:05 Media  emhttpd: spinning down /dev/sdl
Nov 30 11:07:11 Media  emhttpd: spinning down /dev/sdg
Nov 30 11:07:11 Media  emhttpd: spinning down /dev/sdd
Nov 30 11:07:11 Media  emhttpd: spinning down /dev/sdn
Nov 30 11:07:11 Media  emhttpd: spinning down /dev/sdi
Nov 30 11:07:14 Media  emhttpd: spinning down /dev/sdf
Nov 30 11:07:17 Media  emhttpd: spinning down /dev/sdc

Edited November 30, 20223 yr by Joker169
Didn't paste all needed

Quote

December 1, 20223 yr

Author

21 hours ago, Joker169 said:

The only errors in console tab were these:

[UPC_ENV] ✨ local Dashboard:539:27
Result: CA Background Scan Dashboard:753:11
This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see https://firefox-source-docs.mozilla.org/performance/scroll-linked_effects.html for further details and to join the discussion on related tools and features! Dashboard
Scroll anchoring was disabled in a scroll container because of too many consecutive adjustments (10) with too little total distance (0 px average, 0 px total). jquery.apexcharts.js:6:6213
Scroll anchoring was disabled in a scroll container because of too many consecutive adjustments (10) with too little total distance (0 px average, 0 px total). jquery.apexcharts.js:6:6213

Didn't seem anywhere related to the plugin

As far as the accessing page, this is from this morning from sys log:

Nov 30 02:04:55 Media  emhttpd: read SMART /dev/sdg
Nov 30 02:05:05 Media  emhttpd: read SMART /dev/sdj
Nov 30 02:05:25 Media  emhttpd: read SMART /dev/sdl
Nov 30 02:05:39 Media  emhttpd: read SMART /dev/sdd
Nov 30 02:06:13 Media  emhttpd: read SMART /dev/sdf
Nov 30 02:07:27 Media  emhttpd: read SMART /dev/sdi
Nov 30 02:07:51 Media  emhttpd: read SMART /dev/sdc
Nov 30 02:14:43 Media  emhttpd: read SMART /dev/sdn
Nov 30 02:35:16 Media  emhttpd: read SMART /dev/sdk
Nov 30 02:35:34 Media kernel: mdcmd (38): set md_write_method 1
Nov 30 02:35:34 Media kernel: 
Nov 30 03:27:13 Media  emhttpd: spinning down /dev/sdj
Nov 30 03:35:27 Media  emhttpd: spinning down /dev/sdn
Nov 30 03:35:34 Media kernel: mdcmd (39): set md_write_method 0
Nov 30 03:35:34 Media kernel: 
Nov 30 03:45:50 Media  emhttpd: read SMART /dev/sdn
Nov 30 03:50:35 Media kernel: mdcmd (40): set md_write_method 1
Nov 30 03:50:35 Media kernel: 
Nov 30 04:02:10 Media  emhttpd: read SMART /dev/sdj
Nov 30 04:21:59 Media  emhttpd: spinning down /dev/sdk
Nov 30 04:25:35 Media kernel: mdcmd (41): set md_write_method 0
Nov 30 04:25:35 Media kernel: 
Nov 30 05:23:55 Media  emhttpd: spinning down /dev/sdc
Nov 30 05:24:38 Media  emhttpd: spinning down /dev/sdn
Nov 30 05:25:27 Media  emhttpd: spinning down /dev/sdg
Nov 30 05:40:41 Media  emhttpd: spinning down /dev/sdj
Nov 30 05:53:48 Media  emhttpd: spinning down /dev/sdf
Nov 30 05:54:57 Media  emhttpd: spinning down /dev/sdl
Nov 30 06:00:59 Media  emhttpd: spinning down /dev/sdi
Nov 30 06:01:19 Media  emhttpd: spinning down /dev/sdd
Nov 30 08:00:03 Media  emhttpd: read SMART /dev/sdj
Nov 30 08:00:10 Media kernel: sd 1:0:8:0: [sdj] tag#7275 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Nov 30 08:00:10 Media kernel: sd 1:0:8:0: [sdj] tag#7275 Sense Key : 0x5 [current] 
Nov 30 08:00:10 Media kernel: sd 1:0:8:0: [sdj] tag#7275 ASC=0x21 ASCQ=0x0 
Nov 30 08:00:10 Media kernel: sd 1:0:8:0: [sdj] tag#7275 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Nov 30 08:00:10 Media kernel: critical target error, dev sdj, sector 3905203848 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Nov 30 08:00:10 Media kernel: BTRFS warning (device sdj1): failed to trim 1 device(s), last error -121
Nov 30 08:03:22 Media root: /var/lib/docker: 56 GiB (60147957760 bytes) trimmed on /dev/loop2
Nov 30 08:03:22 Media root: /mnt/cache: 282.4 GiB (303181410304 bytes) trimmed on /dev/mapper/nvme0n1p1
Nov 30 08:03:22 Media  sSMTP[40750]: Creating SSL connection to host
Nov 30 08:03:22 Media  sSMTP[40750]: SSL connection using TLS_AES_256_GCM_SHA384
Nov 30 08:03:22 Media  sSMTP[40750]: Authorization failed (535 5.7.8  https://support.google.com/mail/?p=BadCredentials e20-20020ac845d4000000b003a582090530sm862914qto.83 - gsmtp)
Nov 30 09:00:04 Media  emhttpd: spinning down /dev/sdj
Nov 30 09:53:08 Media  emhttpd: read SMART /dev/sdc
Nov 30 09:53:18 Media  emhttpd: read SMART /dev/sdd
Nov 30 09:53:40 Media  emhttpd: read SMART /dev/sdn
Nov 30 09:53:49 Media  emhttpd: read SMART /dev/sdl
Nov 30 09:53:58 Media  emhttpd: read SMART /dev/sdi
Nov 30 09:55:06 Media  emhttpd: read SMART /dev/sdg
Nov 30 09:55:23 Media  emhttpd: read SMART /dev/sdf
Nov 30 11:07:05 Media  emhttpd: spinning down /dev/sdl
Nov 30 11:07:11 Media  emhttpd: spinning down /dev/sdg
Nov 30 11:07:11 Media  emhttpd: spinning down /dev/sdd
Nov 30 11:07:11 Media  emhttpd: spinning down /dev/sdn
Nov 30 11:07:11 Media  emhttpd: spinning down /dev/sdi
Nov 30 11:07:14 Media  emhttpd: spinning down /dev/sdf
Nov 30 11:07:17 Media  emhttpd: spinning down /dev/sdc

When watching the Network tab of the Developer console and sitting on the Dashboard, do you see repeated calls to gpustatus.php? To me it looks like your dashboard isn't even attempting the Javascript-based calls to populate the data.

Quote

December 1, 20223 yr

52 minutes ago, b3rs3rk said:

When watching the Network tab of the Developer console and sitting on the Dashboard, do you see repeated calls to gpustatus.php? To me it looks like your dashboard isn't even attempting the Javascript-based calls to populate the data.

Yes, several GET requests to the point of spamming requests. You asking this must mean you either have an idea of the fix or know there is a issue with Unraid.

Quote

December 1, 20223 yr

Author

1 hour ago, Joker169 said:

Yes, several GET requests to the point of spamming requests. You asking this must mean you either have an idea of the fix or know there is a issue with Unraid.

It 'spamming' is correct and configurable as to how often the javascript runs the collector to refresh the widget if it's too often for your liking, but there's really no other way to do it. If you click on any one of those requests and look at the actual response, does it reflect the same data as manually running the gpustatus.php script from the CLI (from the troubleshooting steps)?

Quote

December 1, 20223 yr

15 minutes ago, b3rs3rk said:

It 'spamming' is correct and configurable as to how often the javascript runs the collector to refresh the widget if it's too often for your liking, but there's really no other way to do it. If you click on any one of those requests and look at the actual response, does it reflect the same data as manually running the gpustatus.php script from the CLI (from the troubleshooting steps)?

Vastly different, the response returned the N/A at for all of the data:

Were-as the CLI script returned with same as before:

{"clock":"1189","fan":"N\/A","memclock":"715","memutil":"24%","memused":"3874","power":"32W","powermax":"250","rxutil":"0","txutil":"0","temp":"30 \u00b0C","tempmax":"85 \u00b0C","util":"0%","vendor":"NVIDIA","name":"Tesla P100-PCIE-16GB","clockmax":"1328","memclockmax":"715","memtotal":"16384","encutil":"0%","decutil":"0%","pciemax":16000,"perfstate":"P0","throttled":"No","thrtlrsn":"","pciegen":3,"pciegenmax":3,"pciewidth":16,"pciewidthmax":16,"sessions":3,"uuid":"GPU-5ab1abde-31a8-eaa3-d02a-d75ad238d36d","plexusing":false,"plexmem":0,"plexcount":0,"jellyfinusing":false,"jellyfinmem":0,"jellyfincount":0,"handbrakeusing":false,"handbrakemem":0,"handbrakecount":0,"embyusing":false,"embymem":0,"embycount":0,"tdarrusing":false,"tdarrmem":0,"tdarrcount":0,"unmanicusing":false,"unmanicmem":0,"unmaniccount":0,"dizquetvusing":false,"dizquetvmem":0,"dizquetvcount":0,"ersatztvusing":false,"ersatztvmem":0,"ersatztvcount":0,"fileflowsusing":false,"fileflowsmem":0,"fileflowscount":0,"frigateusing":false,"frigatemem":0,"frigatecount":0,"deepstackusing":true,"deepstackmem":3872,"deepstackcount":3,"nsfminerusing":false,"nsfminermem":0,"nsfminercount":0,"shinobiprousing":false,"shinobipromem":0,"shinobiprocount":0,"foldinghomeusing":false,"foldinghomemem":0,"foldinghomecount":0,"appssupp":["plex","jellyfin","handbrake","emby","tdarr","unmanic","dizquetv","ersatztv","fileflows","frigate","deepstack","nsfminer","shinobipro","foldinghome"]}

Quote

December 3, 20223 yr

New updates fixed the issue of blank data. thanks but the latest one (2022.11.30a) does not detect frigate anymore.

Quote

1

December 5, 20223 yr

Author

On 12/1/2022 at 12:22 PM, Joker169 said:

Vastly different, the response returned the N/A at for all of the data:

Were-as the CLI script returned with same as before:

{"clock":"1189","fan":"N\/A","memclock":"715","memutil":"24%","memused":"3874","power":"32W","powermax":"250","rxutil":"0","txutil":"0","temp":"30 \u00b0C","tempmax":"85 \u00b0C","util":"0%","vendor":"NVIDIA","name":"Tesla P100-PCIE-16GB","clockmax":"1328","memclockmax":"715","memtotal":"16384","encutil":"0%","decutil":"0%","pciemax":16000,"perfstate":"P0","throttled":"No","thrtlrsn":"","pciegen":3,"pciegenmax":3,"pciewidth":16,"pciewidthmax":16,"sessions":3,"uuid":"GPU-5ab1abde-31a8-eaa3-d02a-d75ad238d36d","plexusing":false,"plexmem":0,"plexcount":0,"jellyfinusing":false,"jellyfinmem":0,"jellyfincount":0,"handbrakeusing":false,"handbrakemem":0,"handbrakecount":0,"embyusing":false,"embymem":0,"embycount":0,"tdarrusing":false,"tdarrmem":0,"tdarrcount":0,"unmanicusing":false,"unmanicmem":0,"unmaniccount":0,"dizquetvusing":false,"dizquetvmem":0,"dizquetvcount":0,"ersatztvusing":false,"ersatztvmem":0,"ersatztvcount":0,"fileflowsusing":false,"fileflowsmem":0,"fileflowscount":0,"frigateusing":false,"frigatemem":0,"frigatecount":0,"deepstackusing":true,"deepstackmem":3872,"deepstackcount":3,"nsfminerusing":false,"nsfminermem":0,"nsfminercount":0,"shinobiprousing":false,"shinobipromem":0,"shinobiprocount":0,"foldinghomeusing":false,"foldinghomemem":0,"foldinghomecount":0,"appssupp":["plex","jellyfin","handbrake","emby","tdarr","unmanic","dizquetv","ersatztv","fileflows","frigate","deepstack","nsfminer","shinobipro","foldinghome"]}

Can you expand the error property in those responses and share?

Quote

December 5, 20223 yr

Author

On 12/3/2022 at 5:56 PM, morpheus302 said:

New updates fixed the issue of blank data. thanks but the latest one (2022.11.30a) does not detect frigate anymore.

Hmm, I was under the impression that it hasn't worked yet. When did it start working for you?

Quote

December 5, 20223 yr

8 hours ago, b3rs3rk said:

Hmm, I was under the impression that it hasn't worked yet. When did it start working for you?

11.29 worked fine (i think)

Quote

1

December 7, 20223 yr

On 12/5/2022 at 6:18 AM, b3rs3rk said:

Can you expand the error property in those responses and share?

Sure.

0	Object { code: 302, message: "Vendor command returned unparseable data.", extra: "" }

Edited December 9, 20223 yr by Joker169
Added screenshot

Quote

December 10, 20223 yr

Version 2022.11.30a I get N/A for everything as well, just adding that here. I have had this for a while and thought it was just something I did, good to see its not just me.

Edit: Rolled back per the person a few posts back and it works, thanks!!

https://raw.githubusercontent.com/b3rs3rk/gpustat-unraid/6cf1b1e96bc8cd5c1cf7ac8fefea1271d8891e26/gpustat.plg

Edited December 10, 20223 yr by Jclendineng
Adding fix that worked for me

Quote

[PLUGIN] GPU Statistics

Featured Replies

Top Posters In This Topic

Popular Days

Most Popular Posts

juan11perez

mlapaglia

SimonF

Posted Images

Join the conversation

Top Posters In This Topic

Popular Days

Most Popular Posts

juan11perez

mlapaglia

SimonF

Posted Images

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)