dmacias

Not sure. Was this happening on 1.0.11?

I reverted it back to 1.0.11. Maybe I'll try and compile it again without fuse support.

That was fun!! updated borg.

Thanks, that worked. Should have looked through your plugins.

It probably has to do with your boards sort of being in limbo. You can run impifan even though you shouldn't. It probably crashed or didn't stop properly and left the pid. ipmi2json only checks for the ipmifan pid. Starting and stopping ipmifan should clear it up. Thanks for testing it out.

Ok thanks for the update. I have never figured the missing Done button. It happens on a few of my plugins that start and stop the plugin's services. But the missing button only happens if the service is enabled and started. It's like a process hangs but if you click the X everything has competed. So I don't know. I have tried setid /etc/rc.d.rc.script &. It works for my ipmi plugin but not for nut.

It won't work until I adjust the ipmifan script to deal with the shorter raw cammands and multiple board arrays. The script is running but those percentages aren't getting set because the ipmi-raw command won't be formulated correctly.

Good. I'll have to update the GUI to deal with the multiple board arrays and then I'll have update that ipmifan script.

I updated the ipmi2json script. It should work now.

Ok. Thanks. I was wondering if that may be the problem. I'll update shortly.

You do have more fans? If so, try running ipmi2json --debug from the command line and post the results. Remove any username or passwords if applicable.

In the 2017.10.09 update I added Asrock dual socket (EP2C602) support to the ipmi2json script (Configure Button). You need to stop any ipmi fan scripts. If you click on Configure on the Fan Settings page or run ipmi2json from the command line it will detect all available fans by setting them all to full speed then setting each point in the ipmi-raw command to 1/3. Then create a board.json in /boot/config/plugins/ipmi on the flash drive. Should look something like this but with actual fan names. { "ASRock": { "raw": "00 3a 01", "auto": "00 00 00 00 00 00", "full": "01 64 64 64 64 64", "fans": { "FAN_POS1": "00", "FAN_POS2": "00", "FAN_POS3": "00", "FAN_POS4": "00", "FAN_POS5": "00" } }, "ASRock1": { "raw": "00 3a 11", "auto": "00 00 00 00 00 00", "full": "01 64 64 64 64 64", "fans": { "FAN_POS1": "00", "FAN_POS2": "00", "FAN_POS3": "00", "FAN_POS4": "00", "FAN_POS5": "00" } } }

Which latest and what wasn't working? 2017.10.8a should have fixed that problem. The rc.nut script will now killall upsd and upsmon processes if not gracefully shut down. But it should have been fixed by moving the pids to /var/run/nut.

No problem.

Ok Im getting the same when I upgrade from previous to latest now. I'll fix shortly Edit: It's fixed now. It will copy all the old pids to the new /var/run/nut location.

Try running from the command line ps aux | grep ups If something is still running run e.g. killall upsmon There's some differences between the nut packages. I think I need to add some more checks to stop the previous version.

I'll see if I can finish something to test soon.

Thanks that's good info. Assumed but not confirmed till now. I'll see if I can at least finish the config script to create the json for the board.

It doesn't work for your board yet. I added some of the code for detecting the number of sockets into the configure script but haven't finished the output yet. Your board basically needs 2 separate commands and arrays to control your fans. It's like two boards in one. If you look back through the thread there's done discussion about it. Maybe you could confirm that the commands work for me. I'll see if I can find the post. Edit: This is what I have for your board # ASRock Dual Socket # ipmi-raw 00 3a 01 CPU_1_OVERRIDE CPU_1 REAR_1 FRONT_1 FRONT_2 UNKNOWN # ipmi-raw 00 3a 11 CPU_2_OVERRIDE CPU_2 UNKNOWN UNKNOWN # ipmi-raw 00 3a 01 00 AA BB CC DD EE # ipmi-raw 00 3a 11 00 AA BB CC DD EE

If you click on help it will explain the settings. But basicaly the lower temp threshold and below sets your fan rpms @ 0 and the the upper temp threshold and above sets fans to full 100%. Fan speed is set from 0-100% between the 2 temps. Fan speed min and max allow you adjust that from say 20-80%. I think instead of 1-64 I'll show 0-100 in the next release.

You could try raising the low temperature threshold to 25 or 30. Thus pushing the scale higher. You also need to set the fan speed minimum to a value the makes the lowest fan speed greater than the speed set for that fan's threshold in the sensor config editor. Basically if your fan spins too slow or stops the bmc will kick it up to full speed.

The usbhid-ups-ups part doesn't look right. I would check your /boot/config/plugins/nut/ups/ups.conf. You also might try uninstalling the plugin, renaming/deleting the /boot/config/plugins/nut directory and then reinstalling the plugin and trying Autodetect. Edit. I believe the usbhid-ups-ups is ok. I'll look through things a bit more.

I have Start APC UPS Daemon set to no, UPS cable set to custom, Custom UPS Cable set blank and UPS Type set to dumb. You might try starting and stopping APC UPS too.

Normally you click uninstall off, it toggles, changes blue and then shows uninstall on. Then everytime you click Apply, any non selected packages will be uninstalled. However, I if your on the latest version of the plugin you can't from the webgui. I forgot one little period in the last update. I'll fix shortly. But you can deselect what you don't want. Click Apply. Then run packagemanager -u from the command line. Edit: should be fixed now if you update the plugin

It's in the OP and been discussed here a lot. The speedtest script is really dependent on machine and connection. Especially on faster connections, it doesn't work. But it can be useful if that reading is consistent. It will still show you if there's a problem with your connection. If I ever get around to it I will create a docker to run the script and still use the plugin to parse the results. It seems to give better results in a docker vs running bare unRAID. Don't know why.