jlficken Posted December 9, 2019 Share Posted December 9, 2019 I've spent an hour trying to figure this out including multiple reboots to no avail. I wound up going into Safe Mode and disabling HTTPS and then I could get into my server's GUI, however, all I can get is that the server refused the connection when trying to use HTTPS. It was all working great until I rebooted but I'm stumped. Are there any logs I can look at? Quote Link to comment
BRiT Posted December 9, 2019 Share Posted December 9, 2019 (edited) Full Diagnostics.zip from after the problem happens and before the reboot to safe-mode is where a large majority of needed info would be. It would be created by running the command "diagnostics" at the unix root prompt when telnet or ssh into the server. Edited December 9, 2019 by BRiT Quote Link to comment
jlficken Posted December 9, 2019 Author Share Posted December 9, 2019 Here's what I found.fsnas1u-diagnostics-20191209-1608.zip There were some errors though: root@FSNAS1U:~# diagnostics Starting diagnostics collection... Warning: file_get_contents(/var/local/emhttp/cpuload.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 88 Warning: file(/var/local/emhttp/diskload.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 89 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 91 Warning: implode(): Invalid arguments passed in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 100 done. ZIP file '/boot/logs/fsnas1u-diagnostics-20191209-1607.zip' created. 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.