When typing in the usual IP address nothing loads, it seems to get "stuck" so to speak. The first 1/20 of the load bar fills in and stays there ad infinitum.

 

I'm finding the WebGUI inaccessible. I was using it most of the day to monitor the status of a preclear and parity check. I started the preclear about 2 days ago and the parity check almost 11 hours ago. It was behaving as expected until I returned to find it not working. The system is still on and running. While punching in the usual IP address or local address or using the prefix http:// did not work, I had a mind to try https:// since I had been trying to get it to work earlier. It wouldn't let me in but for some reason took me to my heimdall instance inferring it was the WebGUI that wasnt working, maybe not the entire system. I can reach other dockers as well. I am able to ssh in but when I run diagnostics it freezes in the next command line and doesn't run anything even if I keep it open.

 

I'm glad everything seems to be working still but I am frustrated I can't even get the diagnostics to see what is wrong. Any suggestions? Thanks for reading

 see below

 

 

Edited March 17, 20233 yr by Renel
new development

I managed to capture a diagnostics log file before forcing a shutdown.

 

Per advice from redditor from the reference, I ran

 

/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

 

I ran these to see if restarting those would bring up the GUI, but instead, it did something to make diagnostics stop hanging, I think.

 

Not sure if anyone has any insights? Thanks for reading

tower-diagnostics-20230316-2039.zip

Edited March 17, 20233 yr by Renel
formatting

Mar 16 00:51:06 Tower kernel: ThreadPoolForeg[27101]: segfault at 10000000018 ip 000014dc42430854 sp 000014dc3b9f43b8 error 4 in ld-musl-x86_64.so.1[14dc423f5000+48000]

 

Do you know what this is? It's segfaulting constantly.

Thank you for your response, it is greatly appreciated during this troubleshooting process.

 

I'm not sure why it would be segfaulting or how I might have initialized that. There doesn't seem to be much consistency in the reasons it happens from what I'm googling.

 

I apologize for the speculation below, just trying to provide some context (and I am a novice).

 

Might it have anything to do with opening an unruly amount of tabs to server via an Android client?

 

5-6 days ago I posted about a Crucial MX500 SSD that had become inaccessible after putting it into my Unraid server. First it was behaving weird, being recognized by the system intermittently and eventually ended that with the server becoming unresponsive, unable to POST. I'm wondering if that may have damaged my RAM or other components at some point because it made the server go from on to totally off and shut down immediately.

 

I will run Memtest at 3 passes per stick and report back.

Edited March 18, 20233 yr by Renel

You can also try booting in safe mode with VM/Docker services disabled, see if it runs stable like that, as a basic NAS.