1

Topic: Cron task failing (system tables used by Event Scheduler...)

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.2
- Linux/BSD distribution name and version: FreeBSD 10.2
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? Yes
- Related log if you're reporting an issue: Below
====

I think this may have begun after I updated to FreeBSD 10.2 from 10.1 but I'm not certain.

mysqldump: Couldn't execute 'show events': Cannot proceed because system tables used by Event Scheduler were found damaged at server start (1577)
mysqldump: Couldn't execute 'show events': Cannot proceed because system tables used by Event Scheduler were found damaged at server start (1577)
mysqldump: Couldn't execute 'show events': Cannot proceed because system tables used by Event Scheduler were found damaged at server start (1577)
mysqldump: Couldn't execute 'show events': Cannot proceed because system tables used by Event Scheduler were found damaged at server start (1577)
mysqldump: Couldn't execute 'show events': Cannot proceed because system tables used by Event Scheduler were found damaged at server start (1577)
==> Backup completed with !!!ERRORS!!!.

==> Detailed log (/var/vmail/backup/mysql/2015/10/08/2015-10-08-03:30:00.log):
=========================
* Starting backup: 2015-10-08-03:30:00.
* Backup directory: /var/vmail/backup/mysql/2015/10/08.
* Backing up databases:  mysql vmail cluebringer amavisd iredadmin.
* File size:
----
28K    amavisd-2015-10-08-03:30:00.sql
36K    cluebringer-2015-10-08-03:30:00.sql
52K    iredadmin-2015-10-08-03:30:00.sql
576K    mysql-2015-10-08-03:30:00.sql
24K    vmail-2015-10-08-03:30:00.sql
----
* Backup completed (Success? NO).

Any idea what this means or how I can fix it?

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Cron task failing (system tables used by Event Scheduler...)

A quick Google search will give you many answers. e.g.
http://serverfault.com/questions/562282 … vent-table

3

Re: Cron task failing (system tables used by Event Scheduler...)

looks like you *did not* run "mysql_upgrade -u root -p" after the migration!
you should do this after *any* mysql/mariadb update directly after the
service was restarted to prevent from hidden *serious* problems like
root not allowed to use several grant-commands because missing columns
in the permission tables and such nasty things