Forum GLPI-Project

taciano

Member

Registered: 2016-02-22

Posts: 9

Mysql crash tables after Optimize automatic actions

Good Morning!

I'm struggling with GLPI version 0.90.3
I use the MySQL database ( MariaDB ) version 15.1 Distrib 10.0.22 - MariaDB .
My problem is that whenever the automatic action is taken " optimize " , crash some table database . The errors are:

1 - Got error 127 When reading table ' ./glpi_tickets_users
2 - [ ERROR] mysqld : Table ' ./glpi_useremails ' is marked as crashed and last ( automatic ? ) Repair failed

Examples are , but usually , the tables crash:
glpi_users
glpi_tickets_users
glpi_useremails
glpi_suppliers
glpi_suppliers_tickets

Does anyone have any solutions or more information about it?

yllen

GLPI-DEV

From: Sillery (51)

Registered: 2008-01-14

Posts: 15,278

Re: Mysql crash tables after Optimize automatic actions

Whet is the weight of your database?

---

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)

taciano

Member

Registered: 2016-02-22

Posts: 9

Re: Mysql crash tables after Optimize automatic actions

Mysql has 405MB

ddurieux

Plugins Dev

From: Propières, France

Registered: 2005-06-17

Posts: 7,521

Re: Mysql crash tables after Optimize automatic actions

Repaire the tables.

The table crashes in these cases I have seen:

* not enought dsk space
* bad server reboot (reboot without wait mysql stop, hard reset...)
* MySQL crash (see it only 1 time )

taciano

Member

Registered: 2016-02-22

Posts: 9

Re: Mysql crash tables after Optimize automatic actions

I use the myisamchk utility to repair the tables problem. Nevertheless, when the GLPI optimization task runs , errors appear in some table.
No disk space left ( free 110GB ) .
The server was not shut down incorrectly in no time.