dmacias

I have a list of a bunch of Supermicro and ASRock commands. I knew I had those commands but didn't realize the range was 0 - 255 (00-ff). I updated the plugin with changes for X9 boards. If you have any trouble you can run ipmifan --debug from the command line. It will show all the variables on the console and log the command string to the fanlog.

Thank you for this. I had no idea the X9 had this available. Would be nice if others could confirm it works for their X9 boards also. You are correct that the gui %'s are based on 64. So 100% = 64. It may be as simple as converting the resulting PWM value to hexadecimal and setting a upper limit to 255. I can determine the board model automatically. I'll see what I can do.

Sounds like fun. Thanks

Looking at the github for the mosh slackbuild it looks like the mosh 1.3.2 build 6 was a "Massive rebuilt against openssl 1.1.0h" I downgraded mosh to 1.2.4 because all the previous 1.3.2 builds are gone. I'll try and build it myself against openssl 1.01 when I get a chance.

How are you logging into it? Either the unRAID mosh package was built against openssl 1.1 or your client is. If it's unRAID, I can revert to an earlier version or try to compile it myself.

I added protobuf and mosh. You will also need to install perl and utempter.

I think it was just the null username and password. The 127.0.0.1 is fine but the default should be MONITOR [email protected] 1 monuser monpass master I just removed the plugin and deleted the plugin directory on the flash drive. And reinstalled just to double check. Everything works. So maybe there was some old conf or cfg files left over. Or bad values from the Autodetect button since there was a bug with that. I'll make it so you can't have null username and passwords.

What's your upsmon.conf look like? Looks like line 1 may be missing something

The autodetect was broken due to the -U parameter being deprecated for nutscan. After autodtect, the port auto would be added. I had planned to implement more driver specific settings but haven't had time. For now rc.nut will just add auto to any null port value. In the future I would just hide the port field for drivers that don't need it.

It's my understanding that if you use usb then APCSmart should use usbhid-ups driver. How do you have it setup?

Did you setup in the Nut settings usbhid-ups drive and port auto?

There's is a problem with autodetect. The -U command parameter was dropped from the latest Nut. You can run /usr/bin/nut-scanner -N from the command line. But I think your problem is the built in UPS service Apcupsd is still running. Do you really need Nut? Does the built in UPS not work for you?

Yes. Tripp Lite Ups, later kennels or motherboard would cause the nut driver to stop working. Once it disconnected it wouldn't reconnect. Had to restart the service but would just stop again. The version of nut I compiled using the libusb 1.0+0.1 branch fixes this but still shows occasional errors in the log.

I don't know how to set it up on windows. But you will need to use client/network slave mode and point to your unRAID server

On unRAID set the Nut UPS Mode to Netserver then install Nut on your PC. What OS is your PC?

You will have to deselect some of the packages that still show update after clicking Apply (deletes the package). Then reselect them and apply. I don't really have a way of dealing with build number changes on the same version. e.g. autoconf-2.69-noarch-1.txz upgrading to autoconf-2.69-noarch-2.txz. I'll see if I can do something about that.

I downloaded and tested newer versions of some packages and the error was gone. Probably just make but I'll update some of the others. It's just hard sometimes because unRAID is current on some packages but not others.

I couldn't use this nut plugin anymore due to usb disconnects with my Tripp Lite on 6.5 kernel and new Supermicro X11 board. My ups did work fine with apcupsd though. I compiled a new version of nut against the libusb1.0+0.1 branch (which is rebased to master) and added a couple patches for timeout, retries and closing connection. I included this new package in the latest release for 6.5 only. So far my ups had stayed connected for a few days now. I do get this in the log occasionally usbhid-ups[6380]: nut_libusb_get_report: Input/Output Error But otherwise it seems to stay connected.

Also what version are you on?

I encountered the same thing. The newer package of libunistring doesn't include that link anymore. I'm not sure if other packages need to be updated to not rely on that or what you're compiling relies on it. But you can add the link. ln -sf /usr/lib64/libunistring.so /usr/lib64/libunistring.so.0 I'll check it out more and possibly just add that command to the libunistring package install

Added docker compose

Thanks, I'll fix it. Edit: fixed

I'll add it. Just give me a day or so.

I'll try to get you some manual commands to run or look back through the thread and there should be some for your board

Did you install apr-util package?