• Posts

  • Joined

  • Last visited

Recent Profile Visitors

725 profile views

b3rs3rk's Achievements


Apprentice (3/14)



  1. Hey folks. I just upgraded my UnRAID server to use a new SuperMicro board and am trying to get the IPMI tools working properly. It identifies the SuperMicro IPMI branding and can read all of the sensors without issue. But I'm having an issue with actually changing anything in the config. Any change on any tab I make is ignored even after clicking Apply, then Done. When I go back to the IPMI settings page it is all set to the defaults again. I tried searching in this thread but didn't see anything about a config not being saved. When looking at the Firefox console, I'm seeing a DOMException whenever I browse to the IPMI settings page. The function that is throwing the exception is this one: function decData() { $('#PASSWORD').val(atob($('#PASSWORD').val())); } Not sure if that is the reason things are not working for me, but it's the only error I see when attempting to make changes/save the config. I had previously been using AutoFan and System Temp plugins from Dynamix, but I removed them just in case they were causing issues. They are pretty much worthless now anyways since everything is handled via IPMI on this board. Specs: UnRAID 6.9.2 Pro Xeon Silver 4110 SuperMicro X11SPL-F Motherboard BIOS Version: 3.4 (Latest) BMC Firmware Version: 1.73.05 (Latest) EDIT: It seems that even though I had the Network Connections set to No, it was still trying to autofill my UnRAID user/pass in the BMC connection and submitting it whenever I clicked apply for unrelated settings. After disabling autofill for the UnRAID site in Firefox I was able to make changes.
  2. Beyond the multiple vendor support that was somewhat recently implemented (added Intel and AMD) this is probably the most requested feature. I think I know what needs to be done to address this after talking with some other community devs but it will take time to implement. I'm limited in what I can test because I have a single GPU setup with no onboard graphics because I'm using Xeon. Makes it difficult to start poking around with it too. Trust me, it's on the horizon just no ETA yet.
  3. I'm pretty sure it was just an issue with the settings not getting saved. Maybe. I didn't point you to the correct location for the real plugin config the first time so it is hard to say.
  4. lol, I know. I had you put in a debug on Line 287 of the lib/Nvidia.php file that is probably still there causing the script to exit. You can either reinstall the plugin or make that line blank again.
  5. Is it updating the cfg file? Without that being updated it won't work. Check your boot plugin config file, I just realized you might be looking at the default.cfg which is my fault. more /boot/config/plugins/gpustat/gpustat.cfg
  6. I might have a defaults problem somewhere in the Settings page. But it should be working now after you applied it?
  7. I mean, you probably could. But I'm really not sure what could be wrong with the settings creation. Make sure everything looks like this then click Apply at the bottom of the page. If the Apply button is greyed out and you can't click it then it won't work. You have to change something to get it to switch. EDIT: Greyed out -- Changes detected --
  8. Are VENDOR and GPUID set in your cfg file now?
  9. You should select the Vendor and GPU on the GPUStat settings page and click Apply at the bottom to fill those out and then it should work.
  10. Well that's annoying, working exactly how it is supposed to work. Can you share the contents of your gpustat.cfg file from the /usr/local/emhttp/plugins/gpustat directory?
  11. I should have been more decisive. Sorry. Run this one and send the result: php -r "var_dump(@simplexml_load_string(shell_exec('nvidia-smi -q -x -g GPU-23265d6c-1de2-5786-b964-e20b2a209ad6 2>&1')));"
  12. Okay, so the simplexml_load_string is definitely failing because that's the only time it should return False. Try this (I substituted your UUID so the below should work for your install): php -r "var_dump(shell_exec('nvidia-smi -q -x -g GPU-23265d6c-1de2-5786-b964-e20b2a209ad6 2>&1'));" If it looks like normal XML, try this: php -r "var_dump(@simplexml_load_string(shell_exec('nvidia-smi -q -x -g GPU-23265d6c-1de2-5786-b964-e20b2a209ad6 2>&1')));" If that dumps a SimpleXMLElement, I'm not sure what is wrong as that is basically what the plugin does. If it doesn't, try the commands again but remove the 2>&1 at the end of the shell_exec commands to show stderr. Then bundle the outputs up in a file and paste here for troubleshooting purposes.
  13. I'm not seeing anything that would cause this to happen. A 302 error will occur when the data retrieved from the nvidia-smi call is not an instance of valid XML or it is empty XML. If it wasn't valid XML+, you'd probably be getting a stack error when I try to use @simplexml_load_string on it to turn it into a SimpleXMLElement. When you have the chance, nano the Nvidia.php file: nano -c +287 /usr/local/emhttp/plugins/gpustat/lib/Nvidia.php This should take you directly to line 287 in that file which should be a blank line. Change that line to read: var_dump($data); exit; Save it and exit nano, then re-run the gpustatus.php file like you did for the troubleshooting steps in the first post (great reading skills btw) and send me the result.
  14. Did you go to the Settings page and set something non-default? Usually the Vendor is set to Change Me on install and had to be set to NVIDIA unless you have an old config file present. EDIT: I see that it is throwing a 302 error. Let me look through the full Nvidia-smi output and see if I can identify the problem.
  15. @ich777 how much do I owe you for being my front line support engineer lol