Normally, your system should have a /etc/mysql/debian.cnf holding the following:
root@GPLHost:xen650901>_ ~# cat /etc/mysql/debian.cnf
# Automatically generated for Debian scripts. DO NOT TOUCH!
[client]
host = localhost
user = debian-sys-maint
password = XXXXXXXXXXXXXXXX
socket = /var/run/mysqld/mysqld.sock
[mysql_upgrade]
user = debian-sys-maint
password = XXXXXXXXXXXXXXXX
socket = /var/run/mysqld/mysqld.sock
basedir = /usr
Of course, the XXX thing is replaced by a random value setup by the mysqld package. If you don't have it, or if debian-sys-maint is not present in this file, then you have the above. I don't believe that a setup without the above described file is a healthy setup. Optionally, edit /etc/default/automysqlbackup and set your user / pass.
Also, what is this:
"Cannot proceed because system tables used by Event Scheduler were found damaged at server start"
Please fix your system and come back to tell if the fault is on automysqlbackup.
Normally, your system should have a /etc/mysql/ debian. cnf holding the following:
root@GPLHost: xen650901> _ ~# cat /etc/mysql/ debian. cnf mysqld/ mysqld. sock mysqld/ mysqld. sock
# Automatically generated for Debian scripts. DO NOT TOUCH!
[client]
host = localhost
user = debian-sys-maint
password = XXXXXXXXXXXXXXXX
socket = /var/run/
[mysql_upgrade]
user = debian-sys-maint
password = XXXXXXXXXXXXXXXX
socket = /var/run/
basedir = /usr
Of course, the XXX thing is replaced by a random value setup by the mysqld package. If you don't have it, or if debian-sys-maint is not present in this file, then you have the above. I don't believe that a setup without the above described file is a healthy setup. Optionally, edit /etc/default/ automysqlbackup and set your user / pass.
Also, what is this:
"Cannot proceed because system tables used by Event Scheduler were found damaged at server start"
Please fix your system and come back to tell if the fault is on automysqlbackup.
Thomas