eroc1990

The description in the template says nothing of what it is (a password manager for teams). That should be rectified.

I just decided to downgrade to 6.11.5 for now. Leaving it as is, evaluating performance from there, and may try upgrading again at some point in steps to see where the issues really begin to manifest. Thanks for the help though, @JorgeB.

Yup, usually you'd expect better performance. Unfortunately for me, that has not been the case. I've been up-to-date on the BIOS for a while, including prior to installing 6.12.x. I wish I could fix it by updating that. Oh well. I might just wind up manually downgrading back to the latest point release of 6.11 as a result of this.

Isn't it odd, though, that it's just suddenly happening? This would never happen on previous versions of UnRAID.

I'm going to lead by stating that my UnRAID setup is not normal. I don't do pool/cache. UnRAID is basically a container/VM manager for me, with direct /mnt/disk# mappings for mounted volumes in Docker. Recently, I've been running into an issue where BTRFS will just crash on me out of the blue. My system is usually running anywhere between 60-80% memory usage, of which I have 32 GB. My Docker disk image is formatted BTRFS (was XFS for a while, recently changed after a similar XFS crash prompted a rebuild of the image file). Disk 1/2 are formatted XFS, and 3, 4, and 5 are BTRFS. It seems like there's no rhyme or reason to the crashes I've encountered. The server wasn't under excessive load, memory wasn't constrained beyond what I stated earlier. I'll just see my alerting from my VPS telling me stuff's down, and then I refresh and the system logs are filled with BTRFS read/write errors. Per Scrutiny, all disks in my server are healthy, so I don't think it's a drive issue. I haven't extensively tested my memory, but pre-6.12, I would have uptime in excess of 30-40 days between manual reboots, if needed, save for a random crash here or there due to me allocating more resources to something than I meant to. I've attached two diagnostics, one generated automatically when the issue occurred, and another I manually generated post-reboot. Any insight on how I can improve my server's stability would be greatly appreciated. ericserverpc-diagnostics-20230718-1621.zip ericserverpc-diagnostics-20230718-1638.zip

You've got too many nameservers active. If the VPN service doesn't provide you with server addresses that work with this container, try some public one like Quad9 or 1.1.1.1, but make sure to delete the other IP addresses you aren't using.

Startup logs aren't going to give much context. Do you have the logs around when the failure occurred?

Just keep in mind that the last update to this container was three years ago, so tread carefully when installing and make sure you are properly securing your environment.

Any clue if there's a way to define where it saves the temporarily archived data? I'd rather save the files to a folder on one of my drives instead of inside the Docker image disk, especially since there's no upper limit for how much storage the application uses when downloading files to archive.

Is that part of them switching over to those 10. addresses?

Anyone else having issues with the Binhex rtorrentvpn (or any of the Binhex <insert name here>vpn containers) suddenly being unable to resolve PIA? All of a sudden, traffic on my containers dropped to 0, and I've been receiving the following error: 2021-11-07 02:41:10,532 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error This always results in the container giving up and quitting its connection attempts. Is there anyone else that's been running into this kind of issue? EDIT to add: There have been no changes to my Internet service or network configuration. My PIA account is still valid and credentials are accurate. EDIT again to add: So it looks like, for some reason, the PIA DNS servers are not being appended to /etc/resolv.conf when my Binhex containers start. Can't figure out why not, as the containers are running privileged.

Try removing the text characters and slashes, leaving just the IP address of your target. Sent from my iPhone using Tapatalk

Works like a charm! Thanks again for setting this up!

Sounds good. I’ll hold off on implementing this until that’s been updated. I’m glad to see this is a thing now though, so thank you.

Any plans to support CHAP authentication? Or did I miss that the option exists? I'm able to define my target but it won't connect because of the lack of authentication capability.