dmacias

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?

Are you on the latest bios and bmc firmware? Are your fans 4pin pwm fans?

added ripgrep and fd. Will need time for hyperfine.

I assume CPU_FAN2_1 is a pwm fan. Is the other REAR_FAN2 fan pwm? Have you updated your bios and bmc to latest version of firmware. If not, update and run configure again. I'll try to look back through the thread but I think this was brought up before for this board. Don't remember the conclusion. The fans not showing up in the board.json means the ipmi2json script was not able to control them and determine rpm changes. So until those fans are able to be controlled through ipmiraw commands there's not much that can be done.

switched to a version that doesn't depend on sgutils

To remove the package just run this from the command line rm /boot/config/plugins/NerdPack/packages/6.5/perl-5.26.1-x86_64-4.txz To remove the package directory rm -rf /boot/config/plugins/NerdPack/packages/6.5/

That's weird. It should detect any corrupt packages and remove them. I'll check into that. But just manually delete the package and try again from the webgui