UTStatsDB Forums

I get this error after i try to import ~70 Logiles from the ./Logs Folder.

Fatal error: Uncaught mysqli_sql_exception: The table 'temp_wtkills' is full in /srv/www/html/ut/includes/logsql.php:122 Stack trace: #0 /srv/www/html/ut/includes/logsql.php(122): mysqli_query() #1 /srv/www/html/ut/includes/logsave.php(1417): sql_query() #2 /srv/www/html/ut/logs.php(798): storedata() #3 /srv/www/html/ut/admin.php(559): require('...') #4 /srv/www/html/ut/admin.php(295): logparse() #5 {main} thrown in /srv/www/html/ut/includes/logsql.php on line 122

why using a temporary Table for importing Logfiles ?

The Erromessage is strange. I use MYsql / MariaDB realy often, but such error message ? Never had it.

Can someone Explain this and can tell me how to fix that ? That brokes my import realy hard.

Regards
Skully

Just a workaround to fix that temp table full error :

look into your my.cnf for your Mysql / mariadb server

look for :
[mysqld]
tmp_table_size =
max_heap_table_size =

if that not in there write it in.

set it to 64M or something higher than the 16MB Standard.
After that it looks so :
tmp_table_size = 64M
max_heap_table_size = 64M

restart your mysql / mariaDB Server

you can now check your new settings with that :

SHOW VARIABLES LIKE 'tmp_table_size';
SHOW VARIABLES LIKE 'max_heap_table_size';

it must show ~64MB or in my case : 67108864 Bytes

the Error is now gone.

And now i understand why the import takes so much time.
Creating a temptable, copy all the stuff in and delete copy the stuff out of the table and delete the table.
The same Procedure for every logfile is taking so much time.....

And i ask me why ?!

why using a temp table and not doing that in the real table.
just create a import table and do your things there. You can clear the table after the import. truncate i mean. You will never have issues about temp table full.

My 2 Cents.

Regards
Skully

I only supplied SQL configurations with the full standalone verisions of UTStatsDB I created back in 2008, which I definitely don't advise using anymore. Better to use a modern version of MySQL (or better, MariaDB) and start with the stock configuration that can be tweaked for your hardware.

I only supplied SQL configurations with the full standalone verisions of UTStatsDB I created back in 2008, which I definitely don't advise using anymore. Better to use a modern version of MySQL (or better, MariaDB) and start with the stock configuration that can be tweaked for your hardware.

I downloaded the file from here . UTStatsDB 3.10 under that link here : https://utstatsdb.com/files/dl.php?file=59

I use debian 12 Linux
Apache in the newest version and Maria DB also in newest Version.
PHP is 8.x

and i have used the stock configuration , my first choice was SQLite but thats to slowly.

Regards
Skully