February 20, 20242 yr Idk what happening but the ui go white page when i log on none of the sub page don't display and it been going on for a couple weeks now and i can figure it out,. tower-diagnostics-20240220-1129.zip
February 20, 20242 yr Community Expert What browser? Any adblockers or anything else that might interfere? Tried other browsers or computers? Cleared browser cache?
February 20, 20242 yr Author edge, firefox sarai, lan base and wan base with a mac and pc and vm to test. ive also clear my cache
February 20, 20242 yr Community Expert 19 minutes ago, cutch3233 said: wan base Do you mean your server is accessible from the internet? How?
February 20, 20242 yr 40 minutes ago, cutch3233 said: it been going on for a couple weeks now and i can figure it out,. Is it an intermittent problem? I see you are running 6.12.8 which has only been available for a few days, how did you upgrade if the webgui wasn't working? Or is it just some pages with issues? Is the entire page white or does it show a header and navigation? Just trying to get a clear understanding of the problem, thanks!
February 20, 20242 yr Author 14 minutes ago, ljm42 said: Is it an intermittent problem? I see you are running 6.12.8 which has only been available for a few days, how did you upgrade if the webgui wasn't working? Or is it just some pages with issues? Is the entire page white or does it show a header and navigation? Just trying to get a clear understanding of the problem, thanks! The power thing you seeing is me having to power cycle the system to restore access to the ui. CLI does work from ssh. only thing running is unbalanced moving a bunch of files but i do not see iun the logs what is causing it
February 20, 20242 yr Author 18 minutes ago, trurl said: Do you mean your server is accessible from the internet? How? I try to connect to my server from unraid connect ui over the internet from my phone.
February 20, 20242 yr 11 minutes ago, cutch3233 said: The power thing you seeing is me having to power cycle the system to restore access to the ui. So the webgui initially works after a reboot and then after some time it goes blank? The next time this happens, please SSH to the server (or use a local keyboard/monitor) and and type "diagnostics". This will create a new diagnostics zip file on the flash drive (in the logs directory) which will capture logs after the problem starts, hopefully giving us some clues. Also once the problem starts, please type: cat /var/log/phplog You may be able to copy/paste the response back here, if not you can run: cp /var/log/phplog /boot/logs and then the phplog file will be available on your flash drive along with the new diagnostics zip file (look for the latest one created today). Get both files off the flash and upload here.
February 20, 20242 yr Author 1 hour ago, ljm42 said: So the webgui initially works after a reboot and then after some time it goes blank? The next time this happens, please SSH to the server (or use a local keyboard/monitor) and and type "diagnostics". This will create a new diagnostics zip file on the flash drive (in the logs directory) which will capture logs after the problem starts, hopefully giving us some clues. Also once the problem starts, please type: cat /var/log/phplog You may be able to copy/paste the response back here, if not you can run: cp /var/log/phplog /boot/logs and then the phplog file will be available on your flash drive along with the new diagnostics zip file (look for the latest one created today). Get both files off the flash and upload here. #0 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(43): extract(false) #1 /usr/local/emhttp/plugins/community.applications/scripts/notices.php(12): require_once('/usr/local/emht...') #2 {main} thrown in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43 [20-Feb-2024 06:03:01 America/New_York] PHP Fatal error: Uncaught TypeError: extract(): Argument #1 ($array) must be of type array, bool given in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php:43 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(43): extract(false) #1 /usr/local/emhttp/plugins/community.applications/scripts/notices.php(12): require_once('/usr/local/emht...') #2 {main} thrown in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43 [20-Feb-2024 06:30:02 America/New_York] PHP Fatal error: Uncaught TypeError: extract(): Argument #1 ($array) must be of type array, bool given in /usr/local/emhttp/plugins/dynamix/template.php:50 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/template.php(50): extract(false) #1 {main} thrown in /usr/local/emhttp/plugins/dynamix/template.php on line 50 [20-Feb-2024 06:30:05 America/New_York] PHP Fatal error: Uncaught TypeError: extract(): Argument #1 ($array) must be of type array, bool given in /usr/local/emhttp/plugins/dynamix/template.php:50 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/template.php(50): extract(false) #1 {main} thrown in /usr/local/emhttp/plugins/dynamix/template.php on line 50 [20-Feb-2024 06:52:59 America/New_York] PHP Fatal error: Uncaught TypeError: extract(): Argument #1 ($array) must be of type array, bool given in /usr/local/emhttp/plugins/dynamix/template.php:50 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/template.php(50): extract(false) #1 {main} thrown in /usr/local/emhttp/plugins/dynamix/template.php on line 50 [20-Feb-2024 06:53:02 America/New_York] PHP Fatal error: Uncaught TypeError: extract(): Argument #1 ($array) must be of type array, bool given in /usr/local/emhttp/plugins/dynamix/template.php:50 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/template.php(50): extract(false) #1 {main} thrown in /usr/local/emhttp/plugins/dynamix/template.php on line 50 [20-Feb-2024 07:03:01 America/New_York] PHP Fatal error: Uncaught TypeError: extract(): Argument #1 ($array) must be of type array, bool given in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php:43 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(43): extract(false) #1 /usr/local/emhttp/plugins/community.applications/scripts/notices.php(12): require_once('/usr/local/emht...') #2 {main} thrown in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43 [20-Feb-2024 08:03:01 America/New_York] PHP Fatal error: Uncaught TypeError: extract(): Argument #1 ($array) must be of type array, bool given in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php:43 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(43): extract(false) #1 /usr/local/emhttp/plugins/community.applications/scripts/notices.php(12): require_once('/usr/local/emht...') #2 {main} thrown in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43 [20-Feb-2024 09:03:01 America/New_York] PHP Fatal error: Uncaught TypeError: extract(): Argument #1 ($array) must be of type array, bool given in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php:43 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(43): extract(false) #1 /usr/local/emhttp/plugins/community.applications/scripts/notices.php(12): require_once('/usr/local/emht...') #2 {main} thrown in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43 [20-Feb-2024 10:03:01 America/New_York] PHP Fatal error: Uncaught TypeError: extract(): Argument #1 ($array) must be of type array, bool given in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php:43 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(43): extract(false) #1 /usr/local/emhttp/plugins/community.applications/scripts/notices.php(12): require_once('/usr/local/emht...') #2 {main} thrown in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43 [20-Feb-2024 11:03:01 America/New_York] PHP Fatal error: Uncaught TypeError: extract(): Argument #1 ($array) must be of type array, bool given in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php:43 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(43): extract(false) #1 /usr/local/emhttp/plugins/community.applications/scripts/notices.php(12): require_once('/usr/local/emht...') #2 {main} thrown in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43 [20-Feb-2024 11:28:59 America/New_York] PHP Fatal error: Uncaught TypeError: extract(): Argument #1 ($array) must be of type array, bool given in /usr/local/emhttp/plugins/dynamix/template.php:50 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/template.php(50): extract(false) #1 {main} thrown in /usr/local/emhttp/plugins/dynamix/template.php on line 50 [20-Feb-2024 11:57:28 America/New_York] PHP Fatal error: Uncaught TypeError: extract(): Argument #1 ($array) must be of type array, bool given in /usr/local/emhttp/plugins/dynamix/template.php:50 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/template.php(50): extract(false) #1 {main} thrown in /usr/local/emhttp/plugins/dynamix/template.php on line 50 [20-Feb-2024 12:03:01 America/New_York] PHP Fatal error: Uncaught TypeError: extract(): Argument #1 ($array) must be of type array, bool given in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php:43 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(43): extract(false) #1 /usr/local/emhttp/plugins/community.applications/scripts/notices.php(12): require_once('/usr/local/emht...') #2 {main} thrown in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43 [20-Feb-2024 12:15:24 America/New_York] PHP Fatal error: Uncaught TypeError: extract(): Argument #1 ($array) must be of type array, bool given in /usr/local/emhttp/plugins/dynamix/template.php:50 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/template.php(50): extract(false) #1 {main} thrown in /usr/local/emhttp/plugins/dynamix/template.php on line 50 [20-Feb-2024 13:03:01 America/New_York] PHP Fatal error: Uncaught TypeError: extract(): Argument #1 ($array) must be of type array, bool given in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php:43 Stack trace:
February 20, 20242 yr Author 30 minutes ago, cutch3233 said: Feb 20 02:17:07 Tower mcelog: mcelog read: Function not implemented Feb 20 02:17:07 Tower kernel: mce: [Hardware Error]: Machine check events logged Feb 20 02:17:07 Tower kernel: mce: [Hardware Error]: Machine check events logged Feb 20 02:17:07 Tower kernel: ERST: NVRAM ERST Log Address Range not implemented yet. Feb 20 03:03:16 Tower crond[1808]: exit status 255 from user root php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2>&1 Feb 20 04:03:16 Tower crond[1808]: exit status 255 from user root php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2>&1 Feb 20 04:04:05 Tower kernel: mce: [Hardware Error]: Machine check events logged Feb 20 04:04:05 Tower kernel: mce: [Hardware Error]: Machine check events logged Feb 20 04:41:00 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Feb 20 04:42:00 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update how do i see MCE ?
February 20, 20242 yr Thank you for the phplog. Are you able to capture diagnostics when in that state? (by typing "diagnostics" and then grabbing the file out of the logs directory on the flash drive) I'm still unclear, once the problem happens is it specific pages that go all white or is it all pages?
February 20, 20242 yr This looks like a problem with your USB stick not being read properly. Please take the USB stick out (shutdown server first) and run a file system check on a windows machine.
February 20, 20242 yr Author 41 minutes ago, ljm42 said: Thank you for the phplog. Are you able to capture diagnostics when in that state? (by typing "diagnostics" and then grabbing the file out of the logs directory on the flash drive) I'm still unclear, once the problem happens is it specific pages that go all white or is it all pages? its currently in a broken state so i can pull the logs.
February 20, 20242 yr Author 43 minutes ago, ljm42 said: Thank you for the phplog. Are you able to capture diagnostics when in that state? (by typing "diagnostics" and then grabbing the file out of the logs directory on the flash drive) I'm still unclear, once the problem happens is it specific pages that go all white or is it all pages? here a screen capture of what i see on two different systems.
February 21, 20242 yr Author 4 hours ago, bonienl said: This looks like a problem with your USB stick not being read properly. Please take the USB stick out (shutdown server first) and run a file system check on a windows machine. Came back clean
February 21, 20242 yr Community Expert 45 minutes ago, cutch3233 said: Came back clean Your earlier diagnostics included this -rw------- 1 root root 32768 Jan 1 1980 FSCK0000.REC on the flash drive so there was corruption. What do you get now from command line with this? ls -lah /boot
February 21, 20242 yr Author root@Tower:~# ls -lah /boot total 439M drwx------ 11 root root 32K Dec 31 1969 ./ drwxr-xr-x 21 root root 440 Feb 20 18:04 ../ drwx------ 8 root root 32K Feb 20 19:57 .git/ -rw------- 1 root root 180 May 5 2023 .gitattributes drwx------ 3 root root 32K May 3 2023 EFI-/ -rw------- 1 root root 32K Jan 1 1980 FSCK0000.REC drwx------ 2 root root 32K May 3 2023 System\ Volume\ Information/ -rw------- 1 root root 339M Feb 15 15:16 bzfirmware -rw------- 1 root root 65 Feb 15 15:16 bzfirmware.sha256 -rw------- 1 root root 6.3M Feb 15 15:14 bzimage -rw------- 1 root root 65 Feb 15 15:16 bzimage.sha256 -rw------- 1 root root 64M Feb 15 15:15 bzmodules -rw------- 1 root root 65 Feb 15 15:16 bzmodules.sha256 -rw------- 1 root root 29M Feb 15 15:16 bzroot -rw------- 1 root root 1.2K Feb 15 15:16 bzroot-gui -rw------- 1 root root 65 Feb 15 15:16 bzroot-gui.sha256 -rw------- 1 root root 65 Feb 15 15:16 bzroot.sha256 -rw------- 1 root root 6.7K Feb 15 20:14 changes.txt drwx------ 11 root root 32K Feb 20 17:02 config/ drwx------ 2 root root 32K Jun 20 2023 extra/ -r-------- 1 root root 120K May 3 2023 ldlinux.c32 -r-------- 1 root root 68K May 3 2023 ldlinux.sys -rw------- 1 root root 7.8K Feb 15 20:14 license.txt drwx------ 3 root root 32K Feb 20 16:41 logs/ -rw------- 1 root root 1.8K Feb 15 20:14 make_bootable.bat -rw------- 1 root root 3.3K Feb 15 20:14 make_bootable_linux -rw------- 1 root root 2.4K Feb 15 20:14 make_bootable_mac -rw------- 1 root root 142K Feb 15 20:14 memtest drwx------ 2 root root 32K May 4 2023 packages/ drwx------ 2 root root 32K Feb 17 00:39 previous/ drwx------ 2 root root 32K Jul 1 2023 syslinux/ -rw------- 1 root root 492 Feb 15 20:14 syslinux.cfg- root@Tower:~# looks liek file is there but i ran scan disk on my dekstop after safe shutdown and it reported no issues.
February 21, 20242 yr Community Expert The file was from a previous repair of corruption, could be old. Still, might be worth trying a new install and copy your config from your flash backup.
February 22, 20242 yr On 2/20/2024 at 1:18 PM, cutch3233 said: its currently in a broken state so i can pull the logs. When in the broken state, please SSH in and type the word "diagnostics". This will put the diagnostics.zip file in the logs directory on the flash drive. We really need to see these diagnostics so we can see what is going on with the system. After doing that, please reboot into safe mode (which disables all plugins) and see if the same problem occurs.
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.