You are not logged in.
Pages: 1
Using Centos 7.5.
Database seems to be "self-inflating" by itself.
I mean, 6 months ago I made a backup with mysqldump, file was 70 Mb large. GLPI data has remained totally untouched since then -yes, I'm sure-, though server has remained certainly powered on, obviously. Few days ago I was asked for another backup, so I did mysqldump again, and this time file was 150 Mb large!?
I have no auto-inventory installed; no OCS nor Fusion nor the like.
Could anyone help with this by chance?
Thanks.
Offline
Which ones are the biggest tables?
They might be log ones.
You'll need to configure some purging to avoid them growing too much.
Offline
In the mysql console I used
show table status from <glpi_database>;
I could only judge by number of rows, and some of the "bigger" tables were
glpi_crontasks (rows = 31)
glpi_crontasklogs (rows = 2308310)
glpi_events (rows = 1130)
glpi_logs (rows = 1197)
I also searched for those tables that could potentially be changing by themselves on daily basis, loosely guessing (I may be wrong, I know...) that all those "updated" today could be the ones changing *daily*. Tables updated today I only found:
glpi_computers
glpi_crontasks
glpi_crontasklogs
(Why would computers table be changing by itself!?)
Just as a vague guess, the crontasklogs table could look kinda big...
Do these details tell you something?
Offline
Well, glpi_crontasklogs could be keeped under control if automatic actions had reasonable purge limits.
I don't think glpi_computers had any issues. Search for the ones been updated yesterday and history will tell you what was the las edit on each of them.
Offline
Your post did not help at all.
It's rather seem like you wanted to look pretentious with random words.
I'll try to be more direct.
I'm starting to suspect glpi_crontasklogs. Anyone else could agree, or is willing to help?
If so, how could I purge this table, both manually and automatically?
I just confirmed sql backup file with mysqldump gets bigger everyday just by itself; this is not longer a "I think/I guess". And it's a real problem for me.
Offline
If you have automatic actions running in CLI mode, they are launched even if you have no actions in GLPI.
So glpi_crontasklogs will grow in time
CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6 - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)
Offline
Pages: 1