MySQL "An error has occurred"

[demirdemir]

Hello,
I have seen this issue come up with lots of other people but not a real solution has been offered it seems. I will try to explain it as much as I can, in hopes that someone may have an idea of wht is wrong.

I have a newly rented a Debian dedicated server with directadmin. Everything works fine except that all of a sudden MySQL just quits everyday or so. No more connections are made to MySQL. Then I go to directadmin services and there seems to be MySQL still running with a PID. When I click on Stop or Start MySQL I receive the dreaded directadmin message "An error has occurred". When I try /etc/init.d/mysqld start via SSH I receive a message that MySQL is already running. So the only way I came up to restart the MySQL is to reboot the server.

When the server is rebooted and MySQL is working fine, I go to directadmin services and then I can click on "MySQL Stop" and have it stopped really. But I get that "An error has occurred" message anyway. Then I can click on Start and it starts the MySQL again. But I get that "An error has occurred" message again.

After a day or so MySQL quits again, and I have to reboot again.
So any ideas on this "An error has occurred" message problem?

 

[nobaloney]

To see the actual error try stopping MySQL from a shell login. Instructions differ between OS Distributions.

Jeff

 

[demirdemir]

There are no errors when MySQL is stopped from a shell login.
MySQL stops with [OK] message and within a minute directadmin starts it up again. In the mysql error log there is a warning :

100601 5:48:35 [Note] Event Scheduler: Purging the queue. 0 events
100601 5:48:35 [Warning] Forcing shutdown of 2 plugins
100601 5:48:35 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete

100601 05:48:35 mysqld_safe mysqld from pid file /usr/local/mysql/data/server1.pid ended100601 05:49:01 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
100601 5:49:01 [Note] Plugin 'InnoDB' disabled by command line option
100601 5:49:01 [Note] Event Scheduler: Loaded 0 events
100601 5:49:01 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.1.34' socket: '/tmp/mysql.sock' port: 0 MySQL Community Server (GPL)

Should I disable directadmin mysql monitoring?

 

[demirdemir]

I have disabled directadmin MySQL monitoring just to test.

I stopped MySQL from directadmin, and started it back from shell login, so in directadmin services.status mysqld=OFF.

But I really would like to know why directadmin gives "An error has occured" message whenever I stop OR start mysql... A blank "Details" section does not help at all.

I wouldn't mind the error message if MySQL did not quit everyday. But the problem might be related.

 

[nobaloney]

While only DirectAdmin staff can give a definitive response, I'd make an educated guess that the error comes from the warnings because you're shutting down the plugins. I don't know what plugins, or why you've got them installed, so that's as far as my help on this issue can go.

As to why MySQL is stopping, unless your logs tell you something we can analyze, it's going to remain a mystery to me.

Since MySQL is stopping, and since your sites that depend on it will break, I'd say you need to monitor it and always restart it. If you don't want to depend on DirecdtAdmin to do it for you, you can always create your own daemon or cronjob to do that.

Jeff