Rysz

The Unraid Discord is a bit hidden at the moment, but it's a great source of information and means to ask questions. It would be great if the invite link (https://discord.unraid.net/) could be incorporated into the website somewhere. 🙂 An idea would be integrating it into the header (e.g. next to "Support") or, though more hidden, into the "Support" subpage.

You'll have to try all the "UPS Communication Type" until you find one that provides more details. The problem is not between NUT and the UPS network card, but the UPS network card and UPS itself. Please let us know if you found a setting that has worked for you.

That's not enough information for NUT to operate. Did you change anything for "UPS Communication Type" ? Seems the UPS network card can't read the values from the UPS.

In the second field under "Access Control" (for *.*.*.*) change the Permission to "Read/Write". Then click "Apply" and then try again with the settings for NUT that I posted above - let me know. Note that in NUT you need to set "Start Network UPS Tools Service:" to "Yes" and click "Apply" after.

When you click on "Configuration" in the UPS web interface, are there any settings related to SNMP?

Usually you would set up the SNMP network connection like this: Note that if that doesn't work, SNMP might need to be enabled on the UPS. It should say in the manual how to do that via the web interface exposed by the UPS.

It's Broadcom proprietary software that's not allowed to be re-distributed under their EULA. So I personally don't see any possibility of this making it into a plugin or the base OS in the future.

You mean another NUT server or the UPS has a network card that you want NUT to connect to?

It can't test all of the memory, but it can test a large subset of your memory (e.g. 12GB out of available 16GB). It's very useful for situations where you have no physical access or just want to do a quick preliminary test over a suspicion. As an example, today we suspected RAM problems for a Discord user with OS instabilities and filesystem corruption. Using this plugin, we quickly identified that their RAM had severe problems, becoming apparent within seconds of testing: So it's not a full replacement for an extensive offline memory-test (e.g. using memtest86), but it can be helpful in situations. 🙂

Thanks Simon, cross posted this as a bug report for visibility / keeping track:

Might be a good time to update to 6.12.10 then, it's been stable as a rock for me. 🙂

Can you please post your diagnostics file - it shouldn't restart on its own.

Read this:

I'd seriously advise against this as it closes one very unlikely problem to just open up another much more likely problem: This makes sshd vulnerable to a denial of service (the exhaustion of all MaxStartups connections), but it makes it safe from this vulnerability. A denial of service attack is much easier to perform than the discovered exploit and much more likely to randomly happen to any range of IPs. The SSH vulnerability has only been proven on 32-bit systems and under lab conditions with extensive efforts (several hours invested) so far. While it is assumed to be possible to exploit 64-bit systems as well, it seems to take considerable effort and at that point you really have to ask yourself if you are that much of a target for someone to invest such efforts to break into your Unraid system with a zero-day exploit. There's probably tons of companies out there vulnerable to this exploit right now and you think they're going to go for your Unraid server instead, to steal... what? Unraid is designed for ease of use and not maximum operational security, so you shouldn't be exposing any services on your Unraid server directly to the internet. Forget SSH, reverse proxies... this should be non-negotiable - period. Users, on this subforum in particular, seem to be under the false impression that there's a point where they've taken enough steps to make Unraid safe to be exposed to the internet, this is a dangerous assumption made under a very false sense of security. A system running everything as root and not receiving in-place, zero-day security updates will never be 100% safe. Unraid is a file-server and a local network appliance aimed at providing you convenience at an acceptable degree of security (for use in your LAN - not WAN). Use it for what it can do. Use a VPN to access your Unraid services from remote (if you must) and 99.99% you will not have to care about such things ever. Put services you must directly expose inside VMs on operating systems that are designed for it, don't invest your efforts in the wrong place. This is my personal opinion and not that of Lime Technology or any of the official Unraid staff members and/or creators.

Yes, there's a setting in 7.0 beta to have it written to the USB instead of the RAM.

Probably better to post this here for increased visibility: https://forums.unraid.net/bug-reports/prereleases/

Please post your diagnostics file. Is there anything in the "UPS Details" tab? You can also try with the NUT plugin, it also supports UPS via SNMP.

The problem is that the version of mbuffer installed by the plugin is not compatible with the new OS version (7.x). This becomes even worse because the OS provides its own mbuffer package, which will in fact get broken by the incompatible package being installed on top of it. I don't know which functions of the OS rely on a (functioning) mbuffer package... so the fallout of this (if left untreated) is entirely unclear at this point. To fix this package problem for now, you can run the following command in a terminal (SSH/WebGUI Terminal): sed -i '/^mbuffer-20240107-x86_64-1_SBo.tgz/d' /boot/config/plugins/unRAID6-Sanoid.plg and reboot your system afterwards (you must do this, for the OS to reinstall its own package). The reboot will remove the broken package and the plugin is now patched not to install it again (instead use the one provided with the OS). This solution will "permanently" fix the problem (even through reboots, if you really must use the plugin), at least until you reinstall or update the plugin (it then needs to be reapplied). This is a temporary solution and something the plugin author should fix ASAP, installing a broken package on top of an existing OS package is very bad for several reasons, to the point it may impact stability of the OS itself. Be advised that even when uninstalling the plugin, you will need to reboot your server for the OS to reinstall the package which was overwritten by this plugin, and this should really be done to ensure smooth operation. If it were my server, I'd make do without this solution and uninstall the plugin (on 7.x) until it is fixed. Let's hope to hear back from the developer soon, but he's last been online two months ago... CC @Squid (FYI) Info for the developers: The installed perl package is also semi-broken (it is linked against the now EOL and no longer available OpenSSL version). perl-5.34.0-x86_64-2_slack15.0: libssl.so.1.1 => not found // libcrypto.so.1.1 => not found (so anything SSL will fail when using that package)

Since 99% of users won't ever visit the GitHub repositories, it's more convenient to just work inside the file tree for me.

The configurations looks good, so I'm not sure what is causing this, but your UPS doesn't seem listed as tested and compatible for that relatively new apc_modbus driver (yet)... so this might be the UPS firmware not playing nice with the driver. Did you also attempt it on another USB port or with another USB cable? You try opening an issue here (since its driver related): https://github.com/networkupstools/nut/issues. Please also check that you set the inbuilt UPS Settings (not NUT) away from anything modbus-related, even when they are disabled, perhaps they have a hold over the modbus connection still somehow. Honestly, personally I'd save myself the trouble and just run with the USB driver, which seems to work with your UPS, it already reports all the parameters that are needed for NUT's operation (even if not the load and wattage, but those are only eye-candy for the GUI and not relevant for safe shutdown operation).

Do you have the regular UPS Settings disabled while running NUT? Can you please post the NUT Debug Package that's on NUT Settings page?

The plugin system offers no way for a plugin to be activated or deactivated at the moment. It's generally safe to keep this plugin installed (it doesn't do anything without user interaction), but you can also uninstall it until you need it.

Hey Dan, I've got a little graphical glitch on similarly named shares (it's limited to the GUI): unraid-glitch.mp4 It doesn't happen when I (un)mount "media", but it does happen when I (un)mount "media-adx2"...

Can you take a screenshot of what's happening? What version of Unraid are you on?