Rysz

I've wanted to add this feature, but to my knowledge it's not possible without executing a command inside each Docker container and that's a boundary I'm not willing to cross also for privacy concerns. Here's a guide how to find out: https://superuser.com/questions/1183454/finding-out-the-veth-interface-of-a-docker-container Another possibility would be stopping all Dockers and then bring them up one by one and look at the interface table in between starts which new virtual interface appears when which Docker is started.

Hello, I just tried it from two different servers and it works just fine here. Maybe something got stuck in Community Apps, I found this post about the warning with a solution:

Hello! I've had to change around some paths in the NUT plugin to ensure future version compatibility for UNRAID 6.13+ .... and that's what's likely causing the trouble here - sorry about the inconvenience for your plugin! 😞 const nutConfig string = "/boot/config/plugins/nut/nut.cfg" has changed to const nutConfig string = "/boot/config/plugins/nut-dw/nut-dw.cfg" This is the complete migration process: https://pastebin.com/YkCC1Vde But it's probably best to look for the configuration file in both locations because people who have not migrated to the newer NUT version will have the configuration file in the old (first) location, and those who migrated to the newer version of NUT will have it in the new (second) location (and the old location renamed to 'nut-old'). Send me a PM anytime if you need any more information regarding NUT.

I see that you were using the older NUT 2.8.0 backend when you posted your response, is this still a problem with the newer and now default NUT 2.8.1. backend? Also please post in the NUT Support Thread next time so that your answer doesn't go unnoticed as it unfortunately was in this topic.

Thanks - you can also reinstall the NUT plugin after changing the backend if you can't reboot. Interesting would be if it works on "release (2.8.0 stable)" in particular. The issue with that series must be older than March, because NUT 2.8.1. was released 10/2023 and the default backend the plugin uses was compiled from that release by me 11/2023 and has remained unchanged since then.

Data Volume Monitor (DVM) for UNRAID "A plugin that lets you monitor and act on your consumed data volume utilizing vnStat." With much pride I'd like to present my latest project - the Data Volume Monitor (DVM). Dashboards, footer information, notifications, user actions (on VMs/Docker containers) and custom scripting. These are a few of the features being offered - all centred around the data volume consumption of your server. Don't want to your Syncthing container to pull in more than 50 GB a day? No problem, DVM will stop and restart the container for you within those limits. Running a few data intensive VMs and want to pull the plug when it's been too much? No problem, DVM will disconnect and reconnect specific VMs from/to the network. Want to move around some files and folders when you've pulled in too much data? No problem, set up a custom script and DVM will execute it for you when it's time. Please report back if you are experiencing any problems! This plugin was developed with older machines in mind - it's been tested on 6.8.3 and above.

Hello, in the meantime it was discovered there's currently a backend driver bug with the BX series (see post above) which we're working on. Many BX users are reporting false RB or LB states, so it's NUT and not your UPS. I hope there'll be a fix soon, I'll keep you posted. Same as above, can you please try the other backends with the backend switch in NUT Settings (reboot or reinstall plugin afterwards) to see if it happens on the older backend versions also?

Hello! This is unfortunately a known bug in the NUT backend driver (not the plugin) with that UPS series at the moment, which we're currently investigating. Do you perhaps have a chance to try the other older NUT backends (NUT Settings => Network UPS Tools Backend Switch => ideally reboot or at least reinstall plugin after switching the backend) if it also happens with the older versions? This would help us a lot to close in on what is causing the bug by comparison so we can hopefully fix it in the APC driver as soon as possible. An unrelated question, how are you connected to NUT with Home Assistant when you're using "standalone" NUT mode? Normally that should only work in "netserver" NUT mode. Edit: Nevermind, just tested it and NUT also exposes the general UPS information in "standalone" mode. https://github.com/networkupstools/nut/issues/2347 Thanks in advance! 🙂

Yeah it was just a very minor change in the positioning of some statements in the installation and removal processes - sorry, I missed the release note. 🙂 I've added the release notes now, you probably won't see them because you've already checked for updates, but other users will see them.

This is fixed now - thanks a lot for your investigation, I've taken the liberty of crediting you in the changelog. If you're interested how I solved this: https://github.com/desertwitch/NUT-unRAID/blob/2b7b5113df28836b68e1089d81cdf6095eec861e/source/nut-dw/usr/sbin/nut-notify#L71-L102

Thanks for the detailed information, I think you could be right about your observations. Another possibility is that NUT has lost communication with the UPS for a short time and by in-built backend behaviour NUT always considers a non-communicating UPS that was last seen on battery as critical and immediately sets FSD and shuts down. But since the other computer managed to remain in contact with the UPS a failing command chain is more likely. That script is a 7 years old and could use some general overhauling. I'll introduce some safeguards against any failing upsc-grep-awk chains, which I'm generally not that happy with in their current state, with the next update but it might take a while.

It's because you're using manual configuration mode where everything is supposed to be configured through the configuration files. You'll have to set manual configuration mode to "No" or "for UPS Driver" (if your UPS needs custom settings to be recognized) in order to see the GUI options. I'm guessing you enabled manual configuration mode because your UPS.CONF file has special directives needed for your UPS, so I'd switch to "for UPS Driver" so that those are kept unchanged but you can still use the GUI.

Yes, exactly, now it's just a "dumb" UPS.

Thanks for the additional information, unfortunately nothing is being picked up by the NUT device scanner either. So it seems to be the USB port on the UPS indeed, especially so if the cable works with other devices. Sorry I couldn't be of more help there.

Please post in the respective support topic instead:

Thanks for the detailed information, it seems your system doesn't see the USB device at all. Can you also post the NUT Debug Package (can be found inside NUT Settings) just for me to have a complete picture there? Do you perhaps have a Windows device (e.g. laptop or whatever) around you could try connecting the UPS to and see if it shows up there at all (Device Manager)? Looking at this my first guess would be the USB cable has gone bad - broken port on the UPS is less likely (but not impossible).

AP9827 is the most common cable and used by almost all APC UPS for USB - I'm pretty sure you have that one if it came with the UPS. But everything in this thread is guesswork at best, what we know for sure so far is that you tried it with two different cables (one of which is known to work with another UPS) on three different computers/OSes. That alone very strongly points to a fault with the UPS itself - I'm sorry I can't be of more help there.

Yeah that's a ModBus UPS that you're using. His UPS isn't though, so that won't help in his case I'm afraid.

I'm afraid that really looks like something is faulty on the UPS itself and not the devices it's connected to. 😞

I wouldn't say it's a common issue, but I've certainly seen it happen so it's not impossible. Do you perhaps have a Windows PC that you can try connecting the UPS to and see if it shows up there? Just to rule out that this is a Linux driver issue...

That sounds a lot like your UPS data port or UPS USB controller is damaged and not sending any information if it's not showing in "lsusb" on two different computers with two different cables. If your UPS is still in warranty I would return it to APC.

It's not that easy because Unraid has no process supervisor (either systemd or openrc), which k3s would require. For all that hassle and necessary changes it'd probably be better to set up a Kubernetes server as a VM or on another machine.

It seems APCUPSD development has been stale for a couple of years now, so wouldn't expect much there. In the meantime it seems the NUT ModBus implementation seems to work (see above), so might be worth testing that.

Da brauchst du eigentlich nicht viel machen, wenn ich dich soweit richtig verstanden haben. Es geht doch eigentlich nur darum eine defekte Festplatte zu tauschen, da übernimmt Unraid die Hauptarbeit. Selbst musst du da überhaupt keine Formatierung vornehmen oder Daten verschieben. Der Sinn der Parität ist es ja die Festplatte nahtlos austauschen zu können. 🙂 Foto von der Festplatten-Belegung machen Server herunterfahren Alte Festplatte aus dem Server ausbauen Neue Festplatte in den Server einbauen Server hochfahren An Stelle/Position der nun fehlenden/defekten Festplatte die neue Festplatte auswählen Nochmal mit dem Foto abgleichen das auch alle anderen Festplatten am selben Platz sind Array starten und die Daten wiederherstellen lassen (passiert automatisch) Abschließenden nicht korrigierenden Parity-Check machen ob alles richtig beschrieben wurde. Wenn die neue Festplatte schon im Server ist und läuft, noch einfacher: Foto von der Festplatten-Belegung machen Array stoppen An Stelle/Position der defekten Festplatte nun die neue Festplatte auswählen Nochmal mit dem Foto abgleichen das auch alle anderen Festplatten am selben Platz sind Array starten und die Daten wiederherstellen lassen (passiert automatisch) Abschließenden nicht korrigierenden Parity-Check machen ob alles richtig beschrieben wurde. https://docs.unraid.net/legacy/FAQ/replacing-a-data-drive/

That's actually a very good idea for a simulation test. So basically shutdown everything, turn off UPS completely by button (not standby), remove mains power cable, wait a minute or two, reconnect mains power cable and see what happens (if it turns on).