whatabout

Thank you for that information. As this array has been without parity for some time now while I chased these errors, I opted for the downgrade to v6.12.4. Parity sync is now at 76.7% without encountering a single error.

Hello, For a few weeks I've been seeing errors scatter across all disks in my server. These errors occur across all backplanes, cables, ports. They've reappeared following new configs, component replacements, etc. If a new config is applied and no parity device declared, it seems that all disks will hum along without issue. However when a parity action is began, whether sync/rebuild/read, it is inevitable that before long a disk will encounter errors. And then another, and another, until the system pauses that parity action or I intervene to cancel it. Until today when I installed an all new CPU _and_ motherboard. Kicked off a parity sync, and, again, errors begin appearing on every disk. I've replaced: - Controller - RAM - Motherboard - CPU I've attached diagnostics captured immediately after cancelling that parity sync. box-diagnostics-20240209-2006.zip

Mine's stopped connecting to the swiss pia server, also without any known changes. The PIA desktop client connects to both, though. ¯\_(ツ)_/¯

Thank you so much, binhex. It was due to a GeoIP restriction on the firewall blocking the country of this specific server. I added that country to the allow list and everything is once again operational. Not sure why it had worked previously, as I hadn't recently changed any of these settings. Perhaps the GeoIP feature only recently identified the server's location. ¯\_(ツ)_/¯

Very good point. Same symptom is not the same problem. I've attached supervisord here. Thank you for assistance. supervisord_2020-02-04_07-42.txt

I've got the same problem. Two separate binhex-delugevpn containers were working absolutely perfectly until this past Friday evening. Suddenly, neither were reachable via webUI and I began to incur hit-and-runs on the tracker. I've tried re-creating them from scratch, even using empty /config. I've also tried them on another host. I've used new openvpn files. I've even tried airvpn instead of pia. I can get vpn-less Deluge containers running no problem. But it seems no matter what I do I cannot get binhex-delugevpn to work. Same goes for binhex-qbittorrentvpn and binhex-rtorrentvpn. The containers start but then …nothing. And the logs don't have a smoking gun. Unfortunately renaming core.conf has no effect either way.