Stubbs

Members
  • Posts

    88
  • Joined

  • Last visited

Everything posted by Stubbs

  1. Can you update the OwnCast container to v0.0.10? It released yesterday. Cheers.
  2. They are not showing up on the log anymore, but the rebuild speed varies from 29 MB/s to 3 MB/s. I've been changing the cables around multiple times, and re-inserted the drives into the hotswap bay. I think it's working fine now, and I'm starting to suspect there's a big problem with one of my previous SATA cables. I actually had a really difficult time unplugging one from the motherboard.
  3. I replaced the cables again and started rebuilding the parity drive. The speed went down to 2 MB/s at the start before going back up to 25 MB/s. I'm worried I'll be an old man before it fully rebuilds. I don't feel like touching it again because this has been an absolute nightmare for me all day. Jul 21 02:40:19 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7db6519: link becomes ready Jul 21 02:40:19 Tower kernel: br-236e25b7e44c: port 3(veth7db6519) entered blocking state Jul 21 02:40:19 Tower kernel: br-236e25b7e44c: port 3(veth7db6519) entered forwarding state Jul 21 02:40:21 Tower avahi-daemon[4067]: Joining mDNS multicast group on interface veth7db6519.IPv6 with address fe80::ec19:f4ff:fe80:239c. Jul 21 02:40:21 Tower avahi-daemon[4067]: New relevant interface veth7db6519.IPv6 for mDNS. Jul 21 02:40:21 Tower avahi-daemon[4067]: Registering new address record for fe80::ec19:f4ff:fe80:239c on veth7db6519.*. Jul 21 02:40:39 Tower kernel: ata6.00: exception Emask 0x0 SAct 0x703000 SErr 0x0 action 0x0 Jul 21 02:40:39 Tower kernel: ata6.00: irq_stat 0x40000008 Jul 21 02:40:39 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED Jul 21 02:40:39 Tower kernel: ata6.00: cmd 61/40:a0:a8:a4:7f/05:00:00:00:00/40 tag 20 ncq dma 688128 out Jul 21 02:40:39 Tower kernel: res 41/10:00:a8:a4:7f/00:00:00:00:00/40 Emask 0x481 (invalid argument) <F> Jul 21 02:40:39 Tower kernel: ata6.00: status: { DRDY ERR } Jul 21 02:40:39 Tower kernel: ata6.00: error: { IDNF } Jul 21 02:40:39 Tower kernel: ata6.00: configured for UDMA/133 Jul 21 02:40:39 Tower kernel: ata6: EH complete Jul 21 02:40:46 Tower kernel: ata6.00: exception Emask 0x0 SAct 0x7000000 SErr 0x0 action 0x0 Jul 21 02:40:46 Tower kernel: ata6.00: irq_stat 0x40000008 Jul 21 02:40:46 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED Jul 21 02:40:46 Tower kernel: ata6.00: cmd 61/40:c0:a8:a4:7f/05:00:00:00:00/40 tag 24 ncq dma 688128 out Jul 21 02:40:46 Tower kernel: res 41/10:00:a8:a4:7f/00:00:00:00:00/40 Emask 0x481 (invalid argument) <F> Jul 21 02:40:46 Tower kernel: ata6.00: status: { DRDY ERR } Jul 21 02:40:46 Tower kernel: ata6.00: error: { IDNF } tower-diagnostics-20210721-0240.zip
  4. Help tower-diagnostics-20210721-0215.zip
  5. I just reconnected the previous(fast) cables, booted up, parity rebuild started, and sure enough, those old, nasty errors started appearing again, along with a lousy 6 MB/s rebuild speed (in contrast to the 50MB/s speed I had with the "slower" cables. Here is the log. My Array won't even turn off now, it's stuck on "Array Stopping•Retry unmounting disk share(s)...". I'm worried I will have to restart it again and pray no data will be lost. tower-diagnostics-20210721-0142.zip
  6. Well, it appears to have started rebuilding without any issues so far. The problem is, I think I replaced the previous SATA cables with slower 3GB/S ones. I'm thinking that maybe I should do a quick swap back to the old ones, assuming they're not the problem. I don't want to spend a full 24 hours stressing my array.
  7. This is what I did last time, which resulted in a 90% used up error log, and basically this: Trying again right now though. If it happens again, I'll upload the diagnostic.
  8. Ok, my Disk 4 is back online and working, but my Parity Drive is still broken. Both of these drives are in my x3 HDD Hotswap Bay, which are powered by two power cables. They're extremely difficult to replace or re-insert in my set up so I couldn't do that. The middle HDD (disk 3) has not failed yet, but the Parity Drive in there still has problems. I replaced both SATA cables for the top and bottom bay (parity and disk 4). tower-diagnostics-20210721-0105.zip
  9. My mistake. I was just looking at the top bar and neglected to look at the bottom of the posting area. Being stressed doesn't help... tower-diagnostics-20210721-0041.zip
  10. https://files.catbox.moe/nsotzb.zip Alright, here it is. I also can't even boot my array anymore. My Parity HDD and Disk 4 are now showing up as unassigned devices that need to be formatted, and trying to format them results in "fail". I'm feeling sick...
  11. I ran into a problem. I was encoding videos in the Handbrake container, then at the same time, ran into that highly obnoxious issue where the file permissions for certain folders reset to something I couldn't move, so I ran Safe New Permissions. This caused my Unraid server to freeze with all my CPU cores locked at 100%, and this wasn't ending so I had to shut down my server manually. When I restarted, I started getting these nasty errors. My parity drive wasn't working. I tried removing it from the array and readding it, it started a read check, but that just started returning a mountain of errors, and now my Disk 4 isn't working. I can't even copy-paste the log because it keeps filling up endlessly with errors. I'm scared all my data is starting to disappear now. Is there nothing that can be done?
  12. Again, I'm not sure whether this is related to the Owncast software or the container, but when I try to set up external storage configured with Digital Ocean, I get the error: https://i.imgur.com/hYuOMnN.png Error: More than 1000 frames duplicated I could've sworn I got storage-based streaming working a few days ago, and it may have been before I updated the container to the latest version. I can't test it on the previous version because it's not listed on dockerhub. The stream basically looks like a slide show with a buffering circle. Also the stream portion uploaded to Digitalocean is split in 1.5mb increments, which clearly isn't right: https://i.imgur.com/FHWC0Iq.png It still works fine if I stream directly from my home server without using external storage, but I obviously don't want that because of my worse upload speed.
  13. Hmm, that's so confusing. Maybe it's something to do with configuration. Here is mine with LibreWolf: On Waterfox, it outright doesn't work at all (all addons disabled): One of my viewers yesterday was a Waterfox user too and he said chat wasn't working. My Firefox was outdated though (because I don't use it) so maybe it works with that.
  14. You can test it yourself on Firefox here: https://awatches.techxodus.org/ I predict it will say "Chat is offline", even though I have it enabled in the settings. Browser cache has been emptied. I'm running all of Firefox, Waterfox and LibreWolf on Windows for now.
  15. I just tried a stream with your Owncast container, and while it worked pretty well, it does not work for Firefox browsers and its forks. For Waterfox, it just gets stuck on the initial splash screen. For LibreWolf, the video works, but it says "chat unavailable", even though it works perfectly fine for Chromium-based browsers. I had to ask my viewers to switch to a Chromium-based browser if you can. I assume this is an issue related to this specific container, because I don't see any issues about it in the official github repo.
  16. where is it? Pretty sure I'd be more comfortable backing my USB Drive locally than sending my data elsewhere.
  17. That isn't my problem. That's a solution for having containers inside the VPN network connect with containers outside the VPN network. My problem is that containers inside the VPN network aren't even connected to the internet, let alone the VPN. I also don't understand this part of the FAQ: Set the "host to localhost"? What host? Where?
  18. "NOTE: USB Backup is deprecated on Unraid version 6.9.0 It is advised to use the Unraid.net plugin instead" What's the Unraid.net plugin?
  19. Alright, finally got around to this. It fixes the WebUI, but the containers I'm routing through Binhex's container gets no connection. The Binhex container is still connected though. NZBGet has the extra parameter: --net=container:binhex-delugevpn Network type is set to "None" Deluge has a variable called "VPN_INPUT_PORTS" with "6789" in the field. Deluge also has a port for "6789" Again, the WebUI works, Binhex's container works, but the containers routed through the Binhex's container get no connection.
  20. The ADDITIONAL_PORTS variable doesn't appear for me in this container's configuration. I'm using the latest image and tried force updating.
  21. This hasn't worked for a few months for me now, I think it stopped working when I changed my LAN address. The container routes through the VPN container, but the webUI does not load. I don't know how to troubleshoot it either. I've made sure the VPN container has the correct LAN_NETWORK (same as my router), I set the port up correctly and everything, but the webUI is still just blank white. Force update on the VPN container didn't work. I've also tried other VPN containers and it's always the exact same problem.
  22. The more detailed log: 2021-05-14 07:27:14,760:DEBUG:acme.client:Storing nonce: 00033E53nKQ6FMRgnfb07hZGGW0_LU5GctvsON8mTd172Hk 2021-05-14 07:27:14,760:INFO:certbot._internal.auth_handler:Performing the following challenges: 2021-05-14 07:27:14,760:INFO:certbot._internal.auth_handler:dns-01 challenge for test.org 2021-05-14 07:27:14,761:WARNING:certbot.plugins.dns_common:Unsafe permissions on credentials configuration file: /config/dns-conf/luadns.ini 2021-05-14 07:27:14,765:DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.luadns.com:443 2021-05-14 07:27:15,766:DEBUG:urllib3.connectionpool:https://api.luadns.com:443 "GET /v1/zones HTTP/1.1" 200 165 2021-05-14 07:27:15,770:DEBUG:certbot._internal.error_handler:Encountered exception: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/certbot/_internal/auth_handler.py", line 70, in handle_authorizations resps = self.auth.perform(achalls) File "/usr/lib/python3.8/site-packages/certbot/plugins/dns_common.py", line 60, in perform self._perform(domain, validation_domain_name, validation) File "/usr/lib/python3.8/site-packages/certbot_dns_luadns/_internal/dns_luadns.py", line 54, in _perform self._get_luadns_client().add_txt_record(domain, validation_name, validation) File "/usr/lib/python3.8/site-packages/certbot/plugins/dns_common_lexicon.py", line 48, in add_txt_record self.provider.create_record(type='TXT', name=record_name, content=record_content) TypeError: create_record() got an unexpected keyword argument 'type' 2021-05-14 07:27:15,770:DEBUG:certbot._internal.error_handler:Calling registered functions 2021-05-14 07:27:15,770:INFO:certbot._internal.auth_handler:Cleaning up challenges 2021-05-14 07:27:15,772:DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.luadns.com:443 2021-05-14 07:27:16,810:DEBUG:urllib3.connectionpool:https://api.luadns.com:443 "GET /v1/zones HTTP/1.1" 200 165 2021-05-14 07:27:16,813:ERROR:certbot._internal.error_handler:Encountered exception during recovery: TypeError: delete_record() got an unexpected keyword argument 'type' 2021-05-14 07:27:16,814:DEBUG:certbot._internal.log:Exiting abnormally: Traceback (most recent call last): File "/usr/bin/certbot", line 8, in <module> sys.exit(main()) File "/usr/lib/python3.8/site-packages/certbot/main.py", line 15, in main return internal_main.main(cli_args) File "/usr/lib/python3.8/site-packages/certbot/_internal/main.py", line 1435, in main return config.func(config, plugins) File "/usr/lib/python3.8/site-packages/certbot/_internal/main.py", line 1304, in certonly lineage = _get_and_save_cert(le_client, config, domains, certname, lineage) File "/usr/lib/python3.8/site-packages/certbot/_internal/main.py", line 140, in _get_and_save_cert lineage = le_client.obtain_and_enroll_certificate(domains, certname) File "/usr/lib/python3.8/site-packages/certbot/_internal/client.py", line 444, in obtain_and_enroll_certificate cert, chain, key, _ = self.obtain_certificate(domains) File "/usr/lib/python3.8/site-packages/certbot/_internal/client.py", line 374, in obtain_certificate orderr = self._get_order_and_authorizations(csr.data, self.config.allow_subset_of_names) File "/usr/lib/python3.8/site-packages/certbot/_internal/client.py", line 424, in _get_order_and_authorizations authzr = self.auth_handler.handle_authorizations(orderr, best_effort) File "/usr/lib/python3.8/site-packages/certbot/_internal/auth_handler.py", line 70, in handle_authorizations resps = self.auth.perform(achalls) File "/usr/lib/python3.8/site-packages/certbot/plugins/dns_common.py", line 60, in perform self._perform(domain, validation_domain_name, validation) File "/usr/lib/python3.8/site-packages/certbot_dns_luadns/_internal/dns_luadns.py", line 54, in _perform self._get_luadns_client().add_txt_record(domain, validation_name, validation) File "/usr/lib/python3.8/site-packages/certbot/plugins/dns_common_lexicon.py", line 48, in add_txt_record self.provider.create_record(type='TXT', name=record_name, content=record_content) TypeError: create_record() got an unexpected keyword argument 'type' 2021-05-14 07:27:16,815:ERROR:certbot._internal.log:An unexpected error occurred: 2021-05-14 07:27:16,815:ERROR:certbot._internal.log:TypeError: create_record() got an unexpected keyword argument 'type'
  23. Tried adding extra parameters to address what I was trying to do. Ended up breaking the container, so I reinstalled it, and now it's flat out not working. Any idea what's causing the problem? Log: dns-01 challenge for site.org Unsafe permissions on credentials configuration file: /config/dns-conf/luadns.ini Cleaning up challenges Cleaning up challenges Encountered exception during recovery: TypeError: delete_record() got an unexpected keyword argument 'type' Encountered exception during recovery: TypeError: delete_record() got an unexpected keyword argument 'type' An unexpected error occurred: TypeError: create_record() got an unexpected keyword argument 'type' Please see the logfiles in /var/log/letsencrypt for more details. ERROR: Cert does not exist! Please see the validation error above. Make sure you entered correct credentials into the /config/dns-conf/luadns.ini file. Encountered exception during recovery: TypeError: delete_record() got an unexpected keyword argument 'type' An unexpected error occurred: TypeError: create_record() got an unexpected keyword argument 'type' Please see the logfiles in /var/log/letsencrypt for more details. ERROR: Cert does not exist! Please see the validation error above. Make sure you entered correct credentials into the /config/dns-conf/luadns.ini file.