Excessive Disk Space Usage

This site is best viewed in a modern browser with JavaScript enabled.

Chad

I'm getting errors like this from Reportico. Both 6.0.16 and 7.1.36-beta. Happens when the result set exceeds about 1750 rows. Nothing special about the queries. Some don't even have criteria. Doesn't happen with my other database apps or with phpMyAdmin. This is a shared server, and the temporary directory appears to be used by MySQL.

I understand this is where MySQL puts its temporary files and there isn't enough space on the hard drive. We're going to switch hosting companies because of this. My question is whether there's some way I can get Reportico to use less space-intensive queries, as the problem seems to be limited to Reportico.

Tried web and forum searches, found nothing. Any help would be appreciated.

peterdeed

Hi there ..

Thats very strange because Reportico is just building up the SQL statement and sending it to the database engine ( however it is through a library sitting on top of PDO called adodb ). So if mysql is not writing the files it could be that but I cant imagine it woul dbe very much. Perhaps Reportico is calling mysql in a way that puts it in some mode which is writing extra stuff.

Out of interest, how much free space did you start with and what happens if you remove some of the columns (it looks like you dont have many columns in you r query anyway? ).

Are you expecting temporary tables to be created at all in this query? Perhaps its running out of memory and writing to some form of cache?

Also googling the error it can relate to running out of inodes.. do you have a lot of files in that folder on in any other folders.. perhaps reportico is leaving loads of small files lying around?

Ive never seen this before but would be keen to investigate if you have any more clues.

Chad

peterdeed

Thank you for responding. Unfortunately this is shared hosting and I don't have the file permissions for /var/mysqltmp to get those answers. Tech support was no help.

I was hoping that Reportico did weird stuff when querying, but that doesn't appear to be the case.

This happens with a simple SELECT query with no parameters, constraints, temporary tables, etc. There are about 32,000 records in the "everything" query, but it happens when far fewer records are selected (~1,750).

We've been having issues with this db server in recent weeks, often getting "Too Many Connections" errors. Given what you've said about how Reportico builds SQL statements, I don't see why this would be happening in Reportico but not phpMyAdmin.

So I guess it will remain a mystery. We're in the process of changing web hosts, which should fix things.

peterdeed

Ok good luck with the transition... !