[MDEV-4130] seeing issues while running ./bin/mysqld_safe Created: 2013-02-03 Updated: 2013-02-03 Resolved: 2013-02-03 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 10.0.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Mani Sundarigari | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Linux vlmmk644 2.6.18-308.8.1.0.1.el5 #1 SMP Tue May 29 20:48:54 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux software details : drwxr-xr-x 13 maria maria 4096 Jan 27 12:29 mariadb-10.0.0-linux-x86_64 |
||
| Description |
|
How to fix this issue. |
| Comments |
| Comment by Elena Stepanova [ 2013-02-03 ] |
|
Please quote the previous fragment of the log. |
| Comment by Mani Sundarigari [ 2013-02-03 ] |
|
130203 12:20:29 mysqld_safe Starting mysqld daemon with databases from /demarialab1/pocinst/data/dbs |
| Comment by Elena Stepanova [ 2013-02-03 ] |
|
This problem means that you have InnoDB data file /demarialab1/pocinst/data/dbs/ibdata1 which was created with InnoDB settings (particularly, innodb_data_file_path) different from your current settings. If you are trying to create a new database, remove all existing data files and start from clean datadir. For more details, search MySQL manual or other sources (use the text of the error message), this InnoDB limitation has existed for very long time, is not a bug and is not specific for MariaDB. |