Snack_Ears

Members
  • Posts

    7
  • Joined

  • Last visited

Snack_Ears's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I have hit a wall and can't seem to figure out my issue. All of a sudden none of my containers are able to be reached through my reverse proxy. I haven't made any changes to my network or to my docker containers or my proxy hosts. I am able to load NGINX and all of my proxy host show as they always have and show online. I can curl all of my containers from an NGINX console window and all are available. Whenever I try to reach any of my dockers, I get a 522 error "timeout". I am at a loss as nothing has changed in over 6 months, and was running great just a week ago. I can provide any logs just not sure which ones will be needed. Any help will be greatly appreciated.
  2. I had to recreate my my docker image and after reinstalling the postgres14 container, I get this in the logs when attempting to start the container. No containers are able to connect to Postgres and all connections are refused. I'm at a loss on how to fix this or what is causing it. Any help would be greatly appreciated. text error warn system array login 2022-07-05 23:07:28.736 MDT [1] LOG: starting PostgreSQL 14.4 (Debian 14.4-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit 2022-07-05 23:07:28.737 MDT [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 2022-07-05 23:07:28.737 MDT [1] LOG: listening on IPv6 address "::", port 5432 2022-07-05 23:07:28.743 MDT [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2022-07-05 23:07:28.748 MDT [26] LOG: database system was interrupted; last known up at 2022-07-05 23:06:49 MDT 2022-07-05 23:07:28.761 MDT [26] LOG: database system was not properly shut down; automatic recovery in progress 2022-07-05 23:07:28.764 MDT [26] LOG: redo starts at 1/34FC9FD8 2022-07-05 23:07:28.764 MDT [26] LOG: invalid record length at 1/34FCA028: wanted 24, got 0 2022-07-05 23:07:28.764 MDT [26] LOG: redo done at 1/34FC9FD8 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2022-07-05 23:07:28.782 MDT [1] LOG: database system is ready to accept connections PostgreSQL Database directory appears to contain a database; Skipping initialization
  3. @JorgeB I completed the rebuild of both 8TB Parity drives and did an array shutdown with out losing a parity drive. This was guaranteed to do it before so it is promising. Don't want to call it good yet as I have not tried to actually put any load on the system with reading and writing at intervals. Thank you again for the help, I don't know if I would have found that with out you. @ChatNoir I found that last night while I was working on completing the steps that JorgeB outlined. Most of that didn't apply to my server hardware but I will go back through all of that and see what I can adjust out. Thank you for posting that and trying to help get some stability back in my world @zenmak Sorry I kind of hijacked your post. Please everyone see if you can help zenmak with his issue as it doesn't seem to be related to my issue, we were both just getting the same error. Thanks every for the great community!
  4. Thank you JorgeB for the info. Your instructions are great and the changes seemed to take as expected. I have completed these steps and am in the process of rebuilding both of my 8TB parity drives. I will follow up in a day or two once the rebuild is complete and I have some time to let the drives spin down and then attempt a cache move or sync. I really appreciate the help. On another note, I'm curious if people are seeing more issues on AMD systems with 6.9.x systems. I ran really solid with not issues but since I have upgraded to 6.9.2 I have had a ton of crashes. I swapped back to a x370 board with a 2600g processor and seems thing to run well. Just something I noticed in all of this. Thanks Read
  5. I have also been having this same problem since I upgraded to 6.9.2. I have been fighting this issue for over 2 months now and can't find anything that helps. I am having the problem only on 8tb Seagate Ironwolf pro drives from what I can tell, but that is the largest drives I have, so the fall into parity and the drives that are usually being written to currently. I have had the issue happen on both data and parity drives. When it happens on a data drive the server locks and I am unable to get logs. From what I can tell it happens any time that cache wants to sync or the mover moves files from cache to a drive. I am at my whit's end at this point and ready to go back to windows as I can't keep my unraid server up for more than 5 hours before I start loosing drives. After the issue happens I can restart the server, remove, start, stop and re-add the drive and then rebuild parity with no issues. Once parity is rebuilt, and I start to turn dockers and other items back on, and cache wants to sync or write to a drive I will loose at least one parity if not the data drive it is trying to write too. All Smart tests come back good on the drives that are seeing the issue. Current config Chasis: Supermicro CSE-836be16 Gigabyte x570 Aurus Elite Wifi AMD Ryzen 5 3600 4 x 8gb 32000 DDR4 memory IBM M1015 9220 8I HBA flashed into IT Mode Nvida Quattro P2000 Cache 2x 256GB Samsung Evo SSD's Parity 2x8TB Seagate Ironwolf Pro Data Mix of Seagate Desktop and NAS drives in 4, 5, 6TB Below are all of the steps that I have completed to date to try and correct this issues but have not had any success at all. Removed the 8TB data drive from the array that started with the issue and rebuilt parity Moved from 2 parity drives to a single parity drives Swapped MB(x370), Proc(Ryzen 2600g), and memory(DDR4 2600) with another older AMD system that was not in use but is in good condition. Removed the existing setup and ran stress tests on the hardware to confirm no issues Removed the Nvidia card in both the current and swapped systems Ran the HBA card in the 16x PCIe slot instead of the 4x PCIe slot Swapped SATA cables between cache drives and MB Swapped HBA cards to a backup card also and 8i 9220 card Reseated and Swapped ports for the HBA cables on the backplane Removed all plugins and dockers and ran a bare system for a week on both current and swapped hardware Moved drives around the backplane but the issue follows the drive and not the backplane port. Power supplies are redundant and I have swapped between then without any effect on the issue. The backup PS was not being used when the issue started and not plugged in at the time. The last piece of hardware that I have not replaced is the backplane. That has been ordered with new HBA cables that will be here Saturday but I find it hard to believe that is the issue as usually when a backplane goes bad it affects all the drives or the issue doesn't follow the drives when they are moved around the backplane. It is specific to a port or ports on the backplane itself. I have attached the logs from my latest failure. Please any help will be greatly appreciated as I don't know know what else to do other than go back to windows and frankly I hate that idea. Thanks Read tower-diagnostics-20210825-2131.zip
  6. I have been using unraid for about a year now with great success but I have hit a problem and can't seem to figure out what is causing it. Unraid 6.9.2 While on vacation I had one of my two parity drives get out of sync. I started a resyn of that parity drive and while it was being completed I had a data drive say it failed. The server crashed at some point after this and when it came back up I only had one parity drive set. I decided since I still had one parity drive that I would attempt to rebuild the data drive that said it failed. I have been trying now for over a week to get that drive rebuilt and I cannot get it to rebuild. SMART checks come out ok on the drive and everything seems to be ok with it but when I start a rebuild, it will run good for about an hour and then it just stops. I have gone through logging and don't see anything that stands out as to the cause. The only way I can get the server to respond once the rebuild has stopped is to do a hard reboot of the server. I really need to get this drive rebuilt so I can get the 2nd parity drive back online and rebuilt as well. I have tried all the various unassign/assign start the array and stop the array, start and restart the server, and nothing seems to help. Please any help will be greatly appreciated as I am at my whit's end. tower-diagnostics-20210803-1510.zip
  7. I can also confirm the latest update broke my openvpn connection. I rolled back to binhex/arch-delugevpn:2.0.4.dev38_g23a48dd01-2-15 and everything worked again. If you need logs or .ovpn files please let me know.