Hi,
yesterday I set up a Mysql4.0.17-Classic on an new Server with Redhat 9.
Today MySQL shut down unexpectedly. The Logfile showed the following
last entry:
040107 10:36:29 8124 Connect [EMAIL PROTECTED] on
8124 Query SHOW VARIABLES LIKE 'pid_file'
..and the error-log:
=============
040107 10:36:29 /usr/local/mysqlmaster/bin/mysqld: Normal shutdown
A mysqld process already exists at Mit Jan 7 10:36:29 CET 2004
040107 10:36:30 /usr/local/mysqlmaster/bin/mysqld: Shutdown Complete
040107 10:36:30 mysqld ended
I'm using a start-script for mysql since more than one year which was
functioning very well with all 3.23-x Versions.
It starts Mysql with the following line:
mybase="/usr/local/mysqlmaster"
myuser="mysqlec"
$mybase/bin/safe_mysqld --defaults-file=$mybase/data/my.cnf --user=$myus
er &
I'm wondering why Mysql didn't restart after the unexpected shutdown and
if something is wrong in the new acutal safe_mysqld?
Greetings
Lutz Maibach
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
