dmacias

Thanks I reverted the Nerdpack python 2 Sent from my SM-N970U using Tapatalk

The reason I assume none are installed is because the image you posted shows all of them as downloaded = no. That mean that DevPack didn't download and install them. So the packages are installed inherently in unraid but DevPack didn't install the same package headers only.

Thanks for the heads up. I do use ssh but authorized keys only. I also see the 1000 user and group on etc and rc.d but everything else in etc is root. I compile my packages on my laptop in Linux. I usually use root to compile them but obviously didn't on the last update. I'll push an update when I get home.

Yes, Unraid has Apcupsd built in under Settings/UPS Settings

I was getting macvlan call traces this past year on Unraid 6.8 and 6.9. I have unifi hardware also and have always had vlans and static ip's for dockers. Here's some things I have done since I started getting the call traces. Not all of these were done to try and fix the problem. Just upgraded some hardware. I swapped my SM MB for my current x11ssi-ln4f (old one had bent pins anyway that made one of ram ports not work). I also upgraded my network USG4 router and USW 24 PoE switch to UDM Pro router and 24 PoE Pro switch. Upgraded to Mellanox 10GB network card and disabled the 4 Intel nic ports on the MB. Dedicated IPMI port was still active. Still was getting call traces through all these changes. One of 2 things fixed this for me. I noticed Unraid's network settings for my 10GB card was set to eth0 and my vlans on br0 had IPv4 address assignments setup. I changed those vlans Ipv4 assignments to none. (not sure why I had this set up as I already manually set docker IP addresses to an ip in the vlans range in the docker's config) My dedicated IPMI lan with a fixed ip (I set a fixed ip in the SM IPMI/BMC settings) was set as eth1 (not part of br0) and eth1 was setup to get an IP under IPv4 address assignment. I changed that to none also. So after setting both my vlans and eth1 IPv4 address assignment to none, I have not had a single call trace or server crash in a few weeks. Previously server would have call traces once in a while but would crash crash at least once a week.

Actually none of those are installed. It's misleading because those are part of unraid but they remove the headers. I created packages with just the headers for inherent unraid packages to be installed over the existing package. They should show downloaded and the switch should be turned on.

Did you install all the DevPack packages? I think it's in glibc. I usually just install everything

Updated to 3.1

The binaries are all within Slackware packages hosted on my github. Some are compiled by me and some are from other repositories. When installed, the Slackware package are downloaded to the flash drive then installed. When rebooting the server they are installed from the flash drive.

The "underscore" in the version was messing up json-c. I renamed it

It's included in 6.9

I updated bind, json-c and added krb5. If I remember I'll add the auto select of dependencies for bind next time I update the plugin

Looks like you need libffi

Updated

Note that this upgrades json-c. /usr/lib64/libjson-c.so.4 is replaced with /usr/lib64/libjson-c.so.5. I don't know what else relies on the older version of json-c. Updated bind and json-c and added krb5

Added psutil. Should be able to install using pip3 now

Sounds like a different version is installed already by another plugin or manually

Updated bind. Let me know.

Sure it's easier. I don't have to maintain a package when python has a perfectly good package manager.

This is a python app. You can install this with pip3 install undervolt. Need pip, setuptools and python

I'd appreciate any help. What does this command print out? dmidecode -qt2|awk -F: '/^\tProduct Name:/ {print $2}' If it's the board model, id like to add it to an array for future use with similar models. Then I just have to add a model name to the array to compare and implement the necessary raw commands. Unless there's an better way to differentiate this model from other ASRock models. I'm not sure what your hack was. If you just hard-coded a json array with everything. But I'd prefer using the ipmi2json script to build this json array. Reason being that bmc firmware updates sometimes change ipmi fan names and sometimes there's different names between different models even though they use the same ipmi raw commands. If prefer building the json array matching each location in the raw command to each fan it corresponds to. Thanks for any help and for figuring out the ipmi commands.

I wouldn't try anything like that

I usually alway update the bios and bmc if there's an update. I guess if depends on the release notes of it's worth it.

Maybe try ipmitool. Could be a freeipmi problem. Also is the bmc firmware up to date.

Sorry, there's no individual control with the Supermicro boards.