[BlueOnyx:26974] Re: Summary of Disk Usage Error

[Michael Stauber]

Hi Felipe,

> Hello, whenever we try to open the Usage Information -> Disk section on 
> Server Management, the page returns:
> 
> “Internal Server Error”
> 
> “The server encountered an internal error and was unable to complete 
> your request. “
> 
> Enabling the debug mode it returns the following:
> 
> TypeError
> 
> Unsupported operand types: string / int
> 
> */usr/sausalito/ui/chorizo/ci4/Modules/Base/Disk/Controllers/ServerDiskUsage.php*at line *1034*

I just checked the code in question. The error indicates that the quota 
information for Vsites that your BlueOnyx has stored in its CODB 
database (GUI backend) is incorrect. It should have the values stores as 
integer, but somehow a string got stored instead. Or the field is empty. 
Either way: It has unexpected data in it for either allowed disk quota 
of the Vsite, its actual disk usage or both.

I just published an updated base-disk-* to the YUM repositories for 
5210R and 5211R which checks if the values are integers before using 
them in calculations. If they're not integers, they'll be set to "0" 
instead.

However, the underlying problem is that one or more of your Vsites has 
disk quota issues and is not reporting expected values.

Please get the YUM updates installed this way:

yum clean all
yum update

Then as "root" and from the shell please run these two commands:

/usr/sausalito/sbin/disk_restorequotas.pl
/sbin/swatch

The first reads the actual disk quota limits from CODB and writes them 
out to the filesystem.

The second command (among other things) reads the actual disk usage and 
writes them back into CODB.

Then in your BlueOnyx GUI go to /disk/serverDiskUsage?serverDiskUsage=1 
and the error should be gone.

But then check in the "Sites" tab and also the "All Users" tab  to see 
if that page reports that the allowed and used disk quota for Vsites and 
Users is reported correctly. At least the "Allowed Disk Space" should 
NOT be "0". If it shows as "0", then your Vsite(s) or Users may not have 
disk quota set (correctly - or at all). Or it could be that the disk 
quota on the filesystem itself is damaged.

-- 
With best regards

Michael Stauber