i tried to setup a container and it completely froze the GUI while installing it. thankfully i managed to ssh into the server and kill that container, the GUI worked for 10 minutes and froze again. using htop, there's nothing thats taking up resources and the problematic container isn't running ( didn't even manage to complete the installation).

how can i diagnose this? is there any way to pull the syslog using cli, because that's the only way i can access the server as of now? my containers are running fine and are accessible on the ip:port

1 hour ago, sohailoo said:

is there any way to pull the syslog using cli

 

yes, by using command below:

 

diagnostics

 

What's more, you could try to reload ngxin to bring GUI back:

 

/etc/rc.d/rc.nginx stop

/etc/rc.d/rc.nginx start

 

 

Edited September 23, 20232 yr by JackieWu

24 minutes ago, JackieWu said:

 

yes, by using command below:

 

diagnostics

 

thanks i managed to pull the diagnostics, i hope it'll help someone figure out the problem. unfortunately,  restarting nginx didn't help

tower-diagnostics-20230923-2321.zip

 

32 minutes ago, sohailoo said:

thanks i managed to pull the diagnostics, i hope it'll help someone figure out the problem. unfortunately,  restarting nginx didn't help

tower-diagnostics-20230923-2321.zip 269.16 kB · 0 downloads

 

 

For GUI problem, try this:

/etc/rc.d/rc.nginx stop

/etc/rc.d/rc.php-fpm restart

/etc/rc.d/rc.nginx start

 

In your syslog, there are some obvious errors:

 

1. cache pool "ssd_download" may encounter filesystem error, you can perform a filesystem check, you can follow the offical guide Checking and fixing file systems.

 

2. "page fault" is related to RAM problem, I think maybe this is the culprit for the GUI problem, you can take a memtest.

 

Edited September 23, 20232 yr by JackieWu

17 hours ago, JackieWu said:

 

For GUI problem, try this:

/etc/rc.d/rc.nginx stop

/etc/rc.d/rc.php-fpm restart

/etc/rc.d/rc.nginx start

 

In your syslog, there are some obvious errors:

 

1. cache pool "ssd_download" may encounter filesystem error, you can perform a filesystem check, you can follow the offical guide Checking and fixing file systems.

 

2. "page fault" is related to RAM problem, I think maybe this is the culprit for the GUI problem, you can take a memtest.

 

checked the ram, nothing wrong with it. i restarted the server and removed the btrfs pool and just made it a one drive xfs pool instead of 2 btrfs. lost around 45gb of data because of some uncorrectable errors. I'll deal with having smaller cache until i get some same size SSDs and moving to zfs with some redundancy.

9 minutes ago, sohailoo said:

checked the ram, nothing wrong with it. i restarted the server and removed the btrfs pool and just made it a one drive xfs pool instead of 2 btrfs. lost around 45gb of data because of some uncorrectable errors. I'll deal with having smaller cache until i get some same size SSDs and moving to zfs with some redundancy.

 

thanks for feedback