phdphd Posted February 7, 2019 Share Posted February 7, 2019 (edited) Hi All, I have been using the uWamp package. Since this morning while Apache starts correctly, MySQL starts then stops. What does this line mean in mysql log :[ERROR] unknown option '--datadir C:/UwAmp/bin/database/mysql-5.7.11/data' ? Thanks! Edited February 7, 2019 by phdphd Quote Link to comment Share on other sites More sharing options...
phdphd Posted February 7, 2019 Author Share Posted February 7, 2019 After some fixing, I no longer have this error, but instead I have the following one : Quote InnoDB: Trying to access page number 4 in space 1118, space name database_name/table_name, which is outside the tablespace bounds. Byte offset 0, len 16384, i/o type read. If you get this error at mysqld startup, please check that your my.cnf matches the ibdata files that you have in the MySQL server. In the file my.ini, in the [mysqld] section I added Quote innodb_data_file_path=ibdata1:12M:autoextend However I still get the same error on server restart. I also noticed the presence of a file called "ibtmp1", whether the server is running or stopped. Should I put it also in the innodb_data_file_path option ? In the message, the table_name is a quite large table (around 4 MB) that is regularly fed with new records. This is the first time I have this error. Thanks! Quote Link to comment Share on other sites More sharing options...
requinix Posted February 8, 2019 Share Posted February 8, 2019 How did you create the database? Did you copy data files from another MySQL installation? Quote Link to comment Share on other sites More sharing options...
phdphd Posted February 8, 2019 Author Share Posted February 8, 2019 I initially created the database using phpmyadmin. Since then I had an issue (HD crash) a couple of years ago you helped to solve. From that time I had no issue while feeding the above mentioned table every 4 months. Quote Link to comment Share on other sites More sharing options...
phdphd Posted February 8, 2019 Author Share Posted February 8, 2019 I uninstalled, and reinstalled my LAMP stack, and restored the database. Everything is back to normal now. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.