Edvard_Grieg
Members
-
Joined
-
Last visited
-
I'm not exactly sure what's going on, but I've been experiencing random crashes lately and I've been trying to isolate a common factor. HW: E5-2697v2 x2 SuperMicro X9Dri LN4 Motherboard 128GB DDR3 ECC Previous config: Unraid 6.12.10 - rock solid stable with infinite uptime other than version updates What changed: Added Sparkle A380 Elf Card Upgraded to Unraid7 Beta2 to support Arc card What I've been finding is that the server will crash- no terminal response, IP stops responding. HW is still running, but from an OS layer appears to be fully non-responsive. The added frustration is that logging does not appear to be working great. I generate logs while the server is up, but I've yet to capture anything during the crash itself. I have logs set to mirror to flash and syslog is pointed to the server IP. While the server is up it's successfully transcoding via Plex as well as Unmaniac to bulk transcode some less important files from H264 to H265. I've played with the number of worker processes, deliberately trying to get it to crash, and it seems fine, but then randomly I'll refresh a page and find it non-responsive and the server will have crashed requiring a hard power-cycle. I've run a memtest which came back fine, and again prior to adding the Intel Card and upgrading to 7b2 I had zero issues. I can obviously take out the Intel Card and downgrade back to 6.12.10, but I'd like to see if I can pinpoint what is going on. Attached are the diagnostics files and any insights towards getting this working would be great, or at least isolating so I know if I need to downgrade or replace the GPU etc. atlas-diagnostics-20240813-1655.zip
-
I think I'm running into the same thing - before I do a clean install was there anything identified? I'm trying to troubleshoot persistent crashes since upgrading U7b2 to support an ARC GPU and seeing frequent crashes and no logs in syslog.
-
I ended up getting this working with the other docker image, a few things I tweaked... set binlog_format = ROW and transaction_isolation = read-committed per nextcloud documentation I ended up with the same error, but from some other googling, looks like it's a purely front-end error, so I ran "mysql -uroot -p -e "show processlist" from inside the mariadb container to watch until there were no more nextcloud processes being run. I then restarted the nextcloud container and it appears to be working (albight slower than expected)
-
I've been running into an issue and just banging my head on a wall for the past few days. I've been trying to get nextcloud installed- I've followed the lsio blog instructions and SpaceInvaders video to a t, but invariably I'm never able to complete the Nextcloud install setup. Each time I go through and at a minimum drop the nextcloud database, but have on multiple occasions nuked the mariadb and nextcloud containers and their respective appdata folders (and the lingering nextcloud files from the \data directory). I am not even trying to get a reverse proxy working yet, even local access would be a good first step. So at this point what I run into is I'm able to install the mariadb just fine without any issues, and update the bind address and create the nextcloud user and database in the db without any issue. I then create the lsio nextcloud container; however when I run the actual nextcloud setup (populating credentials etc), I ultimately get a 504 Bad Gateway Nginx Timeout. It appears to be a legit timeout as there are tables being written into the database, so it doesn't appear to be a full communication/access issue, but there is definitely something going wrong. Docker configs are essentially the defaults with the lsio changes (setting password for mariadb, changing port to 444 for the nextcloud docker, and then pointing to appropriate shares) From a log perspective, the \data\nextcloud.log only gives some information about not being able to process a file during the install. The appdata/nextcloud/logs/nginx/error.log has the following: 2020/04/02 21:40:30 [error] 349#349: *7 upstream timed out (110: Operation timed out) while reading response header from upstream, client: <LAPTOP_IP>, server: _, request: "POST /index.php HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "<UNRAIDSERVERIP>:444" The appdata/nextcloud/logs/nginx/access.log doesn't have much <DOCKER IP> - - [02/Apr/2020:21:34:37 -0600] "GET /data/htaccesstest.txt HTTP/1.1" 400 255 "-" "Nextcloud Server Crawler" <LAPTOP IP> - - [02/Apr/2020:21:34:37 -0600] "GET /favicon.ico HTTP/2.0" 200 2464 "https://<UNRAID IP>:444/index.php" "Mozilla/5.0 (X11; CrOS x86_64 12871.57.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.81 Safari/537.36" <DOCKER IP> - - [02/Apr/2020:21:39:13 -0600] "GET /data/htaccesstest.txt HTTP/1.1" 400 255 "-" "Nextcloud Server Crawler" <LAPTOP IP> - - [02/Apr/2020:21:39:13 -0600] "GET / HTTP/2.0" 200 2475 "-" "Mozilla/5.0 (X11; CrOS x86_64 12871.57.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.81 Safari/537.36" <DOCKER IP>- - [02/Apr/2020:21:39:30 -0600] "GET /data/htaccesstest.txt HTTP/1.1" 400 255 "-" "Nextcloud Server Crawler" <LAPTOP IP>- - [02/Apr/2020:21:40:30 -0600] "POST /index.php HTTP/2.0" 504 569 "-" "Mozilla/5.0 (X11; CrOS x86_64 12871.57.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.81 Safari/537.36" <DOCKER IP> - - [02/Apr/2020:21:40:30 -0600] "GET /data/htaccesstest.txt HTTP/1.1" 400 255 "-" "Nextcloud Server Crawler" <LAPTOP IP> - - [02/Apr/2020:21:40:30 -0600] "GET /favicon.ico HTTP/2.0" 200 2474 "https://<UNRAID IP>:444/index.php" "Mozilla/5.0 (X11; CrOS x86_64 12871.57.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.81 Safari/537.36" <DOCKER IP> - - [02/Apr/2020:21:40:31 -0600] "GET /data/htaccesstest.txt HTTP/1.1" 400 255 "-" "Nextcloud Server Crawler" <LAPTOP IP> - - [02/Apr/2020:21:40:31 -0600] "GET /favicon.ico HTTP/2.0" 200 2470 "https://<UNRAID IP>:444/index.php" "Mozilla/5.0 (X11; CrOS x86_64 12871.57.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.81 Safari/537.36" The appdata/nextcloud/logs/php/error.log doesn't have much [02-Apr-2020 21:28:29] NOTICE: fpm is running, pid 337 [02-Apr-2020 21:28:29] NOTICE: ready to handle connections [02-Apr-2020 21:37:52] NOTICE: Terminating ... [02-Apr-2020 21:37:52] NOTICE: exiting, bye-bye! [02-Apr-2020 21:39:12] NOTICE: fpm is running, pid 330 [02-Apr-2020 21:39:12] NOTICE: ready to handle connections I'm hopeful someone has an idea of what might be going wrong and how to fix it.