JorgeB Posted August 29, 2019 Share Posted August 29, 2019 Parity disk is still on the same port, you could have done what I suggested, swapping the disk cables with another one. Quote Link to comment
0x00000111 Posted October 8, 2020 Share Posted October 8, 2020 (edited) I was having the same problem wit hthe GUI locking up after an NFS server went down that my unraid box connected to. Fixed it with:  /etc/rc.d/rc.nginx restart /etc/rc.d/rc.nginx reload /etc/rc.d/rc.php-fpm restart /etc/rc.d/rc.php-fpm reload  Edited October 8, 2020 by 0x00000111 8 2 Quote Link to comment
0x00000111 Posted October 8, 2020 Share Posted October 8, 2020 Also have to manually remove the NFS mount:  umount -l -f /mnt/disks/NFS_Share  Quote Link to comment
0x00000111 Posted October 8, 2020 Share Posted October 8, 2020 One last thing, I had to manually stop the docker which was using that NFS mount:  docker stop DockerName  Quote Link to comment
tucansam Posted October 8, 2020 Share Posted October 8, 2020 Of all the times that unraid has hung on me over the years, whether it was the GUI that froze or the dockers that froze or a file transfer that hung or the command prompt that froze, when things like 'reboot' and 'init 0' and 'poweroff' and stopping everything by hand didn't work, the only thing that I have ever been able to do do fix a hung server is to temporarily put the ON/OFF device on the front of the server in the OFF position. Â And then cancel the subsequent parity check. Â Â Quote Link to comment
Ahmad Posted March 21, 2022 Share Posted March 21, 2022 I have run into an issue where the nginx configuration is malformed ... maybe due to having dual IPs?  from /etc/nginx/conf.d/servers.conf: # # Redirect http requests to https # ex: http://tower.local -> https://hash.unraid.net # server { listen 80 default_server; listen [::]:80 default_server; return 302 https://10-0-1-100 10-0-1-101.[ID].myunraid.net$request_uri; } ... # # Port settings for https using CA-signed cert # ex: https://lan-ip.hash.myunraid.net # ex: https://wan-ip.hash.myunraid.net # ex: https://hash.unraid.net # ex: https://www.hash.unraid.net # server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name 10-0-1-100 10-0-1-101.[ID].myunraid.net [external-IP].[ID].myunraid.net; # Ok to use concatenated pem files; nginx will do the right thing. ssl_certificate /boot/config/ssl/certs/certificate_bundle.pem; ssl_certificate_key /boot/config/ssl/certs/certificate_bundle.pem; ssl_trusted_certificate /boot/config/ssl/certs/certificate_bundle.pem; # # Enable OCSP stapling # ssl_stapling on; ssl_stapling_verify on; # location ~ /wsproxy/443/ { return 403; } include /etc/nginx/conf.d/locations.conf; }  note how there are line breaks on the server name and the return directives ... my server has two NICs with IPs: 10.0.1.100 and 10.0.1.101 (10Gbe & 1Gbe) it seems this is tripping up the generated nginx configuration ...  editing the nginx file manually doesnt' seem to work, as when I try to start nginx after, it overwrites it. Quote Link to comment
Ahmad Posted March 21, 2022 Share Posted March 21, 2022 more specifically it looks like the issue is from this line in /etc/rc.d/rc.nginx:  IP4=$(grep 'IPADDR:0' /var/local/emhttp/network.ini | cut -d'"' -f2)  it returns the two IP addresses...  could be solved with:  IP4=$(grep -m 1 'IPADDR:0' /var/local/emhttp/network.ini | cut -d'"' -f2)  1 2 Quote Link to comment
bonienl Posted March 21, 2022 Share Posted March 21, 2022 54 minutes ago, Ahmad said: more specifically it looks like the issue is from this line in /etc/rc.d/rc.nginx:  IP4=$(grep 'IPADDR:0' /var/local/emhttp/network.ini | cut -d'"' -f2)  it returns the two IP addresses...  could be solved with:  IP4=$(grep -m 1 'IPADDR:0' /var/local/emhttp/network.ini | cut -d'"' -f2)   Indeed the original command can produce one or more results depending on the number of IPv4 addresses defined. We need only the first one, which is assigned to interface eth0. Your solution is correct, will make an update.  2 1 Quote Link to comment
MiniKahn Posted April 22, 2022 Share Posted April 22, 2022 (edited) I have the exact same problem @Ahmad Thank you for your solution. Â Unraid 6.10 RC4 Edited April 22, 2022 by MiniKahn 1 Quote Link to comment
juan11perez Posted February 20, 2023 Share Posted February 20, 2023 @bonienl Good day, when starting unraid in "Unraid OS GUI Mode" the system performs as expected and I get a GUI directly from my graphics card. Subsequently if I start a vm using that card, then the vm takes over and works as expected.  Once I shutdown the vm the card output doesn't revert to "Unraid OS GUI Mode".  Is there a command or any other way to recover "Unraid OS GUI Mode" without a server restart? Thank you. Quote Link to comment
juan11perez Posted February 22, 2023 Share Posted February 22, 2023 Good day, when starting unraid in "Unraid OS GUI Mode" the system performs as expected and I get a GUI directly from my graphics card. Subsequently if I start a vm using that card, then the vm takes over and works as expected.  Once I shutdown the vm the card output doesn't revert to "Unraid OS GUI Mode".  Is there a command or any other way to recover "Unraid OS GUI Mode" without a server restart? Thank you. Quote Link to comment
dmac11 Posted October 14, 2023 Share Posted October 14, 2023 On 10/8/2020 at 2:41 AM, 0x00000111 said: I was having the same problem wit hthe GUI locking up after an NFS server went down that my unraid box connected to. Fixed it with:  /etc/rc.d/rc.nginx restart /etc/rc.d/rc.nginx reload /etc/rc.d/rc.php-fpm restart /etc/rc.d/rc.php-fpm reload  This worked for me despite what other people were saying about it not working on versions after 6.4.  I'm on 6.11.5 and the gui would give me nginx 502/500 errors. This fixes it without having to reboot Quote Link to comment
KptnKMan Posted November 14, 2023 Share Posted November 14, 2023 (edited) I know this is an old thread, but nothing here worked for me.  What worked for me on unraid 6.12.3:  Check nginx processes (should return process list): netstat -tulpn | grep nginx  netstat should return something like (show nginx running on 80 and 443): Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 512 0 192.168.22.18:80 0.0.0.0:* LISTEN 8803/nginx: master tcp 0 0 127.0.0.1:443 0.0.0.0:* LISTEN 8803/nginx: master tcp 0 0 127.0.0.1:80 0.0.0.0:* LISTEN 8803/nginx: master  kill nginx proxesses (actually is kill process on 80 and 443): sudo fuser -k 80/tcp sudo fuser -k 443/tcp   Check nginx processes again (should be blank): netstat -tulpn | grep nginx  start nginx processes: /etc/rc.d/rc.nginx start  Maybe this helps someone. Edited November 14, 2023 by KptnKMan 1 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.