ClearOS Bug Tracker


View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0006751ClearOSapp-system-database - System Databasepublic2015-12-14 09:032016-05-17 09:12
Reporterbchambers 
Assigned Tobchambers 
PrioritynormalSeveritymajorReproducibilitysometimes
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version7.1.0 
Target Version7.2.0 UpdatesFixed in Version7.2.0 Updates 
Summary0006751: proc table becomes corrupted
DescriptionWe've now had two reports of the exact same corruption in a MariaDB database:

Mon Dec 14 10:19:44 2015: [fatal ] SQL [00000014] Failed: Table './mysql/proc' is marked as crashed and should be repaired, Query Size: 33, Query: "DROP PROCEDURE IF EXISTS GetProps"

Something more than co-incidence is going on here...spidy sense.
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0002431)
bchambers (administrator)
2015-12-14 11:35

Did we just upgrade the System MySQL (MariaDB) database engine by any chance?

There are some 'hits' to this proc table corruption when an upgrade goes from 5.0 to 5.5.

The recommended action is to run 'mysql_upgrade' after upgrading.
(0002441)
timb80 (developer)
2015-12-16 07:22

I can also reproduce this issue here on my setup (with system-mariadb-5.5.41-2 and Zarafa 7.2.0)
Issue is also shown here with earlier version of MariaDB 5.5.31 but fixed in 5.5.32 supposedly
https://forums.zarafa.com/showthread.php?7980-SQL-error-on-Zarafa-7-1-with-MariaDB-5-5-25/page2 [^]
(0002461)
timb80 (developer)
2015-12-16 08:31
edited on: 2015-12-16 08:32

Running the following fixed mine but then command automatically fixes broken tables so may be a bit over the top


[root@raphael ~]# cat /var/clearos/system_database/root
password = dxxxxxxxxxxxxxxxxxxxxxxxxxx
[root@raphael ~]# /usr/clearos/sandbox/usr/bin/mysql_upgrade -uroot -p
Enter password:
Phase 1/3: Fixing table and database names
Phase 2/3: Checking and upgrading tables
Processing databases
information_schema
mysql
mysql.columns_priv OK
mysql.db OK
mysql.event OK
mysql.func OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.host OK
mysql.ndb_binlog_index OK
mysql.plugin OK
mysql.proc
warning : Table is marked as crashed
status : OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.servers OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.user OK
owncloud
owncloud.oc_activity OK
owncloud.oc_activity_mq OK
owncloud.oc_appconfig OK
owncloud.oc_file_map OK
owncloud.oc_filecache OK
owncloud.oc_files_trash OK
owncloud.oc_group_admin OK
owncloud.oc_group_user OK
owncloud.oc_groups OK
owncloud.oc_jobs OK
owncloud.oc_ldap_group_mapping OK
owncloud.oc_ldap_group_members OK
owncloud.oc_ldap_user_mapping OK
owncloud.oc_locks OK
owncloud.oc_mimetypes OK
owncloud.oc_preferences OK
owncloud.oc_privatedata OK
owncloud.oc_properties OK
owncloud.oc_share OK
owncloud.oc_share_external OK
owncloud.oc_storages OK
owncloud.oc_users OK
owncloud.oc_vcategory OK
owncloud.oc_vcategory_to_object OK
performance_schema
zarafa
zarafa.abchanges OK
zarafa.acl OK
zarafa.changes OK
zarafa.clientupdatestatus OK
zarafa.deferredupdate OK
zarafa.hierarchy OK
zarafa.indexedproperties OK
zarafa.lob OK
zarafa.mvproperties OK
zarafa.names OK
zarafa.object OK
zarafa.objectmvproperty OK
zarafa.objectproperty OK
zarafa.objectrelation OK
zarafa.outgoingqueue OK
zarafa.properties OK
zarafa.receivefolder OK
zarafa.searchresults OK
zarafa.settings OK
zarafa.singleinstances OK
zarafa.stores OK
zarafa.syncedmessages OK
zarafa.syncs OK
zarafa.tproperties OK
zarafa.users OK
zarafa.versions OK
Phase 3/3: Running 'mysql_fix_privilege_tables'...
OK

#systemctl restart system-mariadb
#/usr/sbin/zarafa-condrestart


- Issue History
Date Modified Username Field Change
2015-12-14 09:03 bchambers New Issue
2015-12-14 11:35 bchambers Note Added: 0002431
2015-12-16 07:22 timb80 Note Added: 0002441
2015-12-16 08:31 timb80 Note Added: 0002461
2015-12-16 08:32 timb80 Note Edited: 0002461 View Revisions
2016-02-25 09:00 user2 Status new => acknowledged
2016-03-21 10:07 bchambers Assigned To => bchambers
2016-03-21 10:07 bchambers Status acknowledged => assigned
2016-05-17 09:05 user2 Target Version => 7.2.0 Updates
2016-05-17 09:05 user2 Status assigned => resolved
2016-05-17 09:05 user2 Fixed in Version => 7.2.0 Updates
2016-05-17 09:05 user2 Resolution open => fixed
2016-05-17 09:11 user2 Issue cloned: 0008741
2016-05-17 09:11 user2 Relationship added related to 0008741
2016-05-17 09:12 user2 Status resolved => closed