Results 1 to 2 of 2
I have read the older posts about this subject but they didnt make me any wiser...
the problem i when i start the mysql-server with:
/usr/local/mysql/bin/mysqld_safe –user=mysql &
this happen:
...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 10-19-2004 #1Just Joined!
- Join Date
- Oct 2004
- Posts
- 1
mysql-problem at startup
I have read the older posts about this subject but they didnt make me any wiser...
the problem i when i start the mysql-server with:
/usr/local/mysql/bin/mysqld_safe –user=mysql &
this happen:
[root@domain root]# Starting mysqld daemon with databases from /usr/local/mysql/data
STOPPING server from pid file /usr/local/mysql/data/domain.pid
041019 21:30:28 mysqld ended
log:
041019 21:30:27 mysqld started
InnoDB: Error: auto-extending data file ./ibdata1 is of a different size
InnoDB: 0 pages (rounded down to MB) than specified in the .cnf file:
InnoDB: initial 640 pages, max 0 (relevant if non-zero) pages!
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
041019 21:30:27 Can't init databases
041019 21:30:27 Aborting
041019 21:30:27 InnoDB: Warning: shutting down a not properly started
InnoDB: or created database!
041019 21:30:27 /usr/local/mysql/libexec/mysqld: Shutdown Complete
041019 21:30:28 mysqld ended
???
- 11-02-2004 #2Just Joined!
- Join Date
- Nov 2004
- Posts
- 1
Solution
Solution for me was very simple. I was upgrading from 3.23 to 4.1 and there was an existing ibdata1 in the mysql data directory of size 0. As soon as I deleted this file everything started okay.
Hope this save someone hours of confusion!


Reply With Quote
