dmacias

I updated python to a version that included pkg-resource right after you posted.

You should only need python3 and borg. I updated the python3 packaged. Update it and try again.

The Sensors page takes the highest hard drive temp from the already available /var/local/emhttp/disks.ini. I didn't want to re-poll the hard drives since they had already been polled. This however only includes array drives. The fan control script takes the highest temp from all drives. That's the reason for the 38 in the fancontrol log and 26 in the readings. There was some talk recently about possibly adding an ignore function to fan control. This would keep fans from spinning up due to external or preclearing drives. That's on my todo list. Similar to the dropdown checklist for sensors but for hard drives.

updated shellinabox to latest 2.20 Notable changes/fixes: OpenSSL 1.1 fixes May build with MUSL library Fixed issue #222, LOGIN service Fixed issue #360, ignore escape sequences to fix dir listing Fix for function key presses Adjusting scale on IE New option to disable peer check (issue #364) Add option for custom SSH port Support for APL characters PDF documentation Fix for BSD build New ready event support for iframe messages

https://github.com/dmacias72/unRAID-plugins/raw/master/source/packages/borgbackup-1.1.0-x86_64-2.txz I compiled it again and added msgpack a and pkg_resource.

Give the new package a try and let me know.

Ok I'll update it

I added pigz.

Maybe airbillion knows Msgpack 4.8 is included in the borg package. Maybe I'll try compiling msgpack myself. https://github.com/borgbackup/borg/issues/583

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.