16GB log table - how to purge

[KLT]

Hi all, our log table is around 16GB in size, which, for a text file, seems enormous.

1. What would make it that large? (We've only had the system for 2 years)

2. Is any of that data used for reports?

3. What is standard practice for purging the data? (and how to do that?)

4. I'm currently getting this error when attempting to access the system log through the admin: /www/include/db.php line 811: mysqli_query(): (HY000/14): Can't change size of file (OS errno 28 - No space left on device)
Any ideas on how we could fix that?

Thanks in advance for your replies.

Kent

SVN 9.0

[Mike Perry]

There are several RS log tables. Can you say which one?

Line 811 in db.php refers to the debug log.

Check your include/config.php file for the following :

$debug_log_location

If it is set you can probably delete the file.

Then log into your RS installation as a super admin and go to System | Console | Debug log and if you don't need debug active all the time just check the off box.

[Robert Przybylski]

MySQL Resourcespace database.  Table:  resource_log is 15.3GB  and entire database is 17.5GB.

Thanks !

[KLT]

FYI: Rob is in our IT dept and has way more tech knowledge than me. 

So, Mike, it appears that it's the resource log.

[Mike Perry]

I don't know how operationally necessary the entire data set is in that table as far as the overall RS installation is concerned. I'm not aware of any tools within RS to manage or purges unnecessary log data at scheduled times.

I would try backing up the entire db then truncating the resource_log table. Then see if the installation runs okay. If it doesn't restore the db.

Another potential problem might be interaction between the resource_log table and others that might depend on data from it.

Are there any restrictions on available disk space for the db? Absent any direction from Resource Space I can't say with certainty what would be appropriate or advisable.

Best I've got --

Mike

[Mike Perry]

I've done a little more research -- the resource_log seems to be tied to version control.So if you're using the version control functionality it would probably not be advisable to prune or empty it. . .