greyday

Did Monterey (MacOS 12) break this app/docker? After updating my MBair I can no longer access my daapd server. EDIT: I'm certain it's a MacOS thing, not a DAAPD thing, but if there's a way to re-enable the library in Monterey I'm all ears...

Quick question--is it no longer necessary to set up a multi-disk "single" array manually, or will the gui approach still default to R1? The FAQ entry talks about releases 6.2 and 6.3...

I haven’t tried so I couldn’t say for sure, but it would be a fun experiment (though zero doubt someone has already tried it). I may give it a go once I figure out my crashing issues. My thought is this: if you assign cores to the vm I see no reason why the vm wouldn’t see that as the physical limit. If you didn’t assign cores then I’m not sure, you might have issues since they would be shared. Again, a fun thing to play around with once I have the time…

Have you tried running the second Unraid license as a VM? You'd still probably need a separate card and/or DAS for the array, but you wouldn't need the other physical server...

I'm going to assume that sorted it and go ahead and mark this sorted, but for posterity: it seems that disabling the UPS Monitor isn't enough if you want to use NUT with a USB connection, you have to set the input in UPSM to anything but USB...

Not reproducible as in I can make it happen, but recurring—it happens every couple days. I tried switching the connection setting from usb to custom to see if maybe it was just still detecting the connection even though it was disabled, will post back if that solved the problem…

I recently upgraded my UPS to a Bxterra, so I had to disable the default UPS monitor and install the NUT plugin, which worked fine. But now I'm getting this weird issue where after a few days the UPS monitor turns itself back on, dropping the NUT plugin from the dashboard/replacing it with the original with no info, and sending me a "lost contact with UPS" error. I checked the settings and the monitor is still set to disabled and the NUT plugin is still enabled, the data is still there on the plugin page, and the NUT page footer is still active and displaying the percentage and load. Is there something extra that needs to be done to disable the default UPS monitor? Or a way to uninstall it entirely perhaps?

This worked like a charm. Well, like a slightly tarnished charm, half the readings aren't there and it says the runtime is at 0 (it isn't), but it's a start at least. Thanks!

Doesn't seem to pick it up, but there's also a NUT docker image now, I tried that and got a 401 error on trying to view it, may have to investigate that one further...

I just switched over from an APC to a much larger battery backup and Unraid doesn't seem to detect it. I can't seem to find really any info online at all about bxtera software/hardware and unraid. Has anyone gotten their servers to identify a bxterra or similar rack battery? It's not the end of the world if not, but the auto-shutdown in case of a prolonged power out would definitely be great to have...

The stuff I download tends to be the like 1-3 seeders type (since I have streaming services for all the mainstream stuff). I'll grab a linux torrent later tonight and see what speeds I'm getting...

My VPN (Windscribe) is also doing the phase out thing and I had the same issues, so here's what I did: Downloaded the updated ca.crt and ta.key files and replaced the ones in appdata/binhex-delugevpn/openvpn folder Opened the .ovpn file (name will vary based on your vpn), deleted the line "compress lzo" as per Windscribe's instrux, then manually copied the certificate from the ca.crt file and replaced the old one, closed Started delugevpn, it worked like normal. That was all it took. Hopefully this helps some of you!

I know this is close to a year old, but still--my two cents? Spend the little extra (or use parts you have) to build a separate dedicated PF/OPNsense box. The first time you have to take your server down for more than 20 minutes you'll be glad you did.

Just to hopefully save some other folks some time, because it's not posted here and this is what comes up most often when I search for this problem or how to resize the log (and the next like 10 answers also never state it), the file named "go" that you need to modify is located at: boot/config/

I saw that! In day 3 of parity check, will be updating as soon as it's done.

How do you have passthrough set up (i.e., isolated card, dual or quad port, etc)? And what software did you choose? I am setting up an LTO-5 later this week and I have been reading up on it for a month or so now, there's not a ton of info out there for non-commercial datacenter setups...

I at the time had 64gb of RAM, so I am going to assume that wasn't the issue (I just installed 128--er. 125.9 usable for some reason, but still); both runs have the warnings. To be totally clear, they are colored as warnings, not errors, in the Unraid log. I'm not overly worried or anything, just wanted to know if this is something I should be fixing. Also this probably isn't important as the databases are updating fine and well, but I AM getting this error at the end of the of the opening "testing database" part of the log: WARNING: Clamd was NOT notified: Can't connect to clamd through /run/clamav/clamd.sock: No such file or directory

Hi--I have been using your docker image for a while now in Unraid 6.8.3, it works great, thank you for all your work on it! However lately I am getting these errors in the logs: LibClamAV Warning: Bytecode 79 failed to run: CL_ETIMEOUT: Time limit reached LibClamAV Warning: Bytecode run timed out in interpreter after 5000 opcodes It is still catching viruses and trojans (just ran it on a backup for my gf's main machine before she upgraded the hdd and caught several), but if I am reading the end results correctly: ----------- SCAN SUMMARY ----------- Known viruses: 8748948 Engine version: 0.102.4 Scanned directories: 159783 Scanned files: 712394 Infected files: 5 Data scanned: 640178.14 MB Data read: 5307618.48 MB (ratio 0.12:1) Time: 46830.559 sec (780 m 30 s) It is only scanning about 10% of the total server. Is that right or is this all just it skipping things it has scanned on previous passes? And if these errors are a concern, where/how can I adjust the Bytecode Timeout setting?