all of a sudden my webui is not responding. it just stays on loading ad infinitum. anyone know how to fix this? it doesn;t matter what browser i use. i can still ssh. i did have a vm running in vnc installing the os. maybe that hung it? i'm running beta 21. i tried "diagnostics" via cli but it hangs on "starting diagnostics collection..."

This is exactly what happens when I try to run my windows vm. If you look in the forums you will see threads mentioning similar problems.

I believe it's most likely a bug in the beta's. Only way I have found to get the system responsive again is a reboot.

This is exactly what happens when I try to run my windows vm. If you look in the forums you will see threads mentioning similar problems.

I believe it's most likely a bug in the beta's. Only way I have found to get the system responsive again is a reboot.

 

Yeah, I saw some of those but I didn't see a solution. I just had to reboot. It didn't trigger a parity check though but I needed to run one anyway.

 

Is there any confirmation that this is indeed a bug?

Hmmm...

I wonder if this might have been the cause for me:

 

https://lime-technology.com/forum/index.php?topic=48481.0

 

One of my plugins gives me a console via the webui and I was using it to run MC and copy data over. It didn't happen while I was messing with my VM but since seabios affects the console and my plugin gives a console via the webui, maybe that somehow caused my webui to crash eventually.

This happened to me a few times without a VM. I was just trying to do some benchmark and it just hung.

 

What I noticed is that once I increased the minimum share size to larger than the copying file (copying 8GB file, set minimum size to 10GB), the hanging seems to have stopped.

 

Note: the drive has more than 10GB free space so it shouldn't have been caused by running out of free space.

This happened to me a few times without a VM. I was just trying to do some benchmark and it just hung.

 

What I noticed is that once I increased the minimum share size to larger than the copying file (copying 8GB file, set minimum size to 10GB), the hanging seems to have stopped.

 

Note: the drive has more than 10GB free space so it shouldn't have been caused by running out of free space.

 

Are you using reiserfs as the file system on those disks which are almost full?  It has been previously reported that this file system has issues with very slow response time when the disk is almost full.  Apparently, it takes a long, long time to locate and assign those few remaining sectors.