MySQL installed with homebrew stopped working - mysql
I'm running Laravel with Valet on localhost. The other day my DB stopped working and I got this error.
I've tried varies solutions from StackOverlfow but nothing seems to work for good.
I had some success with re-installing MySQL. First it worked, then after a restart the error returned as if nothing had happened.
Any ideas and possible solutions are welcome!
2019-11-22T07:28:20.732087Z 0 [Warning] [MY-010159] [Server] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
2019-11-22T07:28:20.833268Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:21.834984Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:22.838856Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:23.844548Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:24.848946Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:25.849871Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:26.854401Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:27.859471Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:28.862669Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:29.867559Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:30.868884Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:31.873861Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:32.878402Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:33.882308Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:34.885179Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:35.887673Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:36.890348Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:37.894877Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:38.900421Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:39.904220Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:40.909429Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:41.913230Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:42.918485Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:43.923973Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:44.927397Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:45.931041Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:46.935998Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:47.941222Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:48.943928Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:49.945988Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:50.950217Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:51.955518Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:52.960605Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:53.965354Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:54.970208Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:55.976164Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:56.982518Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:57.984856Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:58.987334Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:28:59.990658Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:00.995798Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:01.997097Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:02.999242Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:04.005513Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:05.010475Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:06.014483Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:07.020468Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:08.026727Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:09.029067Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:10.033853Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:11.036066Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:12.041863Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:13.045891Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:14.050010Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:15.055826Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:16.062497Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:17.068520Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:18.074686Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:19.081226Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:20.084656Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:21.086282Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:22.089582Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:23.095008Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:24.098510Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:25.101950Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:26.108228Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:27.116696Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:28.123539Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:29.129444Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:30.135448Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:31.140923Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:32.144339Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:33.150813Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:34.156732Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:35.160435Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:36.165699Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:37.172622Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:38.180502Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:39.184494Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:40.188930Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:41.192453Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:42.196437Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:43.198767Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:44.206068Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:45.212700Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:46.216042Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:47.222179Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:48.227701Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:49.234171Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:50.236459Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:51.241873Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:52.245806Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:53.249358Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:54.254697Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:55.262889Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:56.269719Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:57.276984Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:58.283896Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:29:59.287215Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:30:00.291169Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:30:01.297730Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-11-22T07:30:01.301008Z 1 [ERROR] [MY-012592] [InnoDB] Operating system error number 35 in a file operation.
2019-11-22T07:30:01.302042Z 1 [ERROR] [MY-012596] [InnoDB] Error number 35 means ‘Resource temporarily unavailable’
2019-11-22T07:30:01.304279Z 1 [ERROR] [MY-012215] [InnoDB] Cannot open datafile ‘./ibdata1’
2019-11-22T07:30:01.305396Z 1 [ERROR] [MY-012959] [InnoDB] Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2019-11-22T07:30:01.306751Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Cannot open a file.
2019-11-22T07:30:01.308318Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2019-11-22T07:30:01.309340Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2019-11-22T07:30:01.310976Z 0 [ERROR] [MY-010119] [Server] Aborting
2019-11-22T07:30:01.311578Z 0 [System] [MY-010910] [Server] /usr/local/Cellar/mysql/8.0.18_1/bin/mysqld: Shutdown complete (mysqld 8.0.18) Homebrew.```
You might want to copy/delete ibdata1 from /usr/local/var/mysq
then restart MySQL brew services start mysql
i didn't work with homebrew before ,but try to change the port you are using .
It looks like you have more than one MySQL installed. One is up and running and the other is attempting to start but cannot. Perhaps you have both MySQL and MariaDB running? That could do it.
It's also possible the same installation is attempting to run MySQL twice (depending on the configuration on what programs boot up when the computer starts).
Though it is quite old thread, still helps somebody. You have another installation which is already running from daemon.
Find from where MySQL is getting Auto started
sudo launchctl list | grep -i mysql
Say Result :
10133 1 com.oracle.oss.mysql.mysqld
Then remove it. Below command parameter changes as per output of your previous command.
sudo launchctl remove com.oracle.oss.mysql.mysqld
Related
Assertion failure: ut0ut.cc:553 thread 140316173764352 [ERROR] [MY-012872] [InnoDB] [FATAL]
enter image description here nnoDB: ###### Diagnostic info printed to the standard error stream 2023-02-15T03:39:09.042343+05:30 0 [ERROR] [MY-012872] [InnoDB] [FATAL] Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung. 2023-02-15T03:39:09.085843+05:30 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: ut0ut.cc:553 thread 140316173764352 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html InnoDB: about forcing recovery.
mysql InnoDB: Unable to lock ./#innodb_redo/#ib_redo0 error: 13
2022-07-31T10:46:33.631091Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.30-0ubuntu0.20.04.2) starting as process 1268525 2022-07-31T10:46:33.680919Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2022-07-31T10:46:35.911807Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./#innodb_redo/#ib_redo0 error: 13 2022-07-31T10:46:35.911857Z 1 [ERROR] [MY-012894] [InnoDB] Unable to open './#innodb_redo/#ib_redo0' (error: 11). 2022-07-31T10:46:35.911872Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Cannot open a file. 2022-07-31T10:46:36.124480Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine 2022-07-31T10:46:36.124674Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2022-07-31T10:46:36.124690Z 0 [ERROR] [MY-010119] [Server] Aborting This instance of mysql has been running fine for over a year on ubuntu. The server crashed and generated a crash log - now I get this error when trying to restart the server. I have looked at other posts and have verified/tried: A) There is not another mysql instance running B) AppArmor has been edited to allow access (nothing has changed & re-verified) Looking at the file it is trying to lock, nothing jumps out at me on why it can not lock it: -rwxr-xr-x 1 mysql mysql 3276800 Jul 29 06:20 '#ib_redo0'* Suggestions? What am I missing?
Cannot get Mysql 8.0 to stay open in Mac OS
MySQL suddenly cannot keep open. I tried ps -ef | grep mysql sudo kill -9 5211 I tried removing my my.cnf I tried creating a new my.cnf as suggested by a previous post Nothing is working. mySQL from "System Preference" turns on after I put my password and few seconds later turns off. Here is the error log: 2019-02-14T01:13:17.285925Z 0 [System] [MY-010116] [Server] /usr/local/Cellar/mysql/8.0.12/bin/mysqld (mysqld 8.0.12) starting as process 11402 2019-02-14T01:13:17.288972Z 0 [Warning] [MY-010159] [Server] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive 2019-02-14T01:13:17.317235Z 1 [ERROR] [MY-012592] [InnoDB] InnoDB: Operating system error number 2 in a file operation. 2019-02-14T01:13:17.317441Z 1 [ERROR] [MY-012593] [InnoDB] InnoDB: The error means the system cannot find the path specified. 2019-02-14T01:13:17.317548Z 1 [ERROR] [MY-012594] [InnoDB] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2019-02-14T01:13:17.317666Z 1 [ERROR] [MY-012646] [InnoDB] InnoDB: File ./ibdata1: 'open' returned OS error 71. Cannot continue operation 2019-02-14T01:13:17.317798Z 1 [ERROR] [MY-012981] [InnoDB] InnoDB: Cannot continue operation. 2019-02-14T01:15:15.776723Z 0 [System] [MY-010116] [Server] /usr/local/Cellar/mysql/8.0.12/bin/mysqld (mysqld 8.0.12) starting as process 12646 2019-02-14T01:15:15.779642Z 0 [Warning] [MY-010159] [Server] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive 2019-02-14T01:15:15.796296Z 1 [ERROR] [MY-012592] [InnoDB] InnoDB: Operating system error number 2 in a file operation. 2019-02-14T01:15:15.796337Z 1 [ERROR] [MY-012593] [InnoDB] InnoDB: The error means the system cannot find the path specified. 2019-02-14T01:15:15.796352Z 1 [ERROR] [MY-012594] [InnoDB] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2019-02-14T01:15:15.796365Z 1 [ERROR] [MY-012646] [InnoDB] InnoDB: File ./ibdata1: 'open' returned OS error 71. Cannot continue operation 2019-02-14T01:15:15.796380Z 1 [ERROR] [MY-012981] [InnoDB] InnoDB: Cannot continue operation. Here is the error. I will check what it means.
Since you have removed .cnf file, so it is expecting ./ibdata1 file in current folder and it is not there. Usually data directory is defined in .cnf file with datadir property. e.g datadir=/var/lib/mysql And this ibdata1 is in datadir folder.
java.lang.AssertionError: assertion failed:
[error] (run-main-0) java.lang.AssertionError: assertion failed: [error] java.lang.AssertionError: assertion failed: [error] at scala.Predef$.assert(Predef.scala:170) [error] at chisel3.core.assert$.apply(Assert.scala:76) [error] at chisel3.iotesters.setupVerilatorBackend$.apply(VerilatorBackend.scala:262) [error] at chisel3.iotesters.Driver$$anonfun$execute$1$$anonfun$apply$mcZ$sp$1.apply$mcZ$sp(Driver.scala:56) [error] at chisel3.iotesters.Driver$$anonfun$execute$1$$anonfun$apply$mcZ$sp$1.apply(Driver.scala:39) [error] at chisel3.iotesters.Driver$$anonfun$execute$1$$anonfun$apply$mcZ$sp$1.apply(Driver.scala:39) [error] at logger.Logger$$anonfun$makeScope$1.apply(Logger.scala:138) [error] at scala.util.DynamicVariable.withValue(DynamicVariable.scala:58) [error] at logger.Logger$.makeScope(Logger.scala:136) [error] at chisel3.iotesters.Driver$$anonfun$execute$1.apply$mcZ$sp(Driver.scala:39) [error] at chisel3.iotesters.Driver$$anonfun$execute$1.apply(Driver.scala:39) [error] at chisel3.iotesters.Driver$$anonfun$execute$1.apply(Driver.scala:39) [error] at scala.util.DynamicVariable.withValue(DynamicVariable.scala:58) [error] at chisel3.iotesters.Driver$.execute(Driver.scala:38) [error] at chisel3.iotesters.Driver$.execute(Driver.scala:100) [error] at mnist.FC2Main$.delayedEndpoint$mnist$FC2Main$1(FC2Main.scala:8) [error] at mnist.FC2Main$delayedInit$body.apply(FC2Main.scala:7) [error] at scala.Function0$class.apply$mcV$sp(Function0.scala:34) [error] at scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12) [error] at scala.App$$anonfun$main$1.apply(App.scala:76) [error] at scala.App$$anonfun$main$1.apply(App.scala:76) [error] at scala.collection.immutable.List.foreach(List.scala:392) [error] at scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35) [error] at scala.App$class.main(App.scala:76) [error] at mnist.FC2Main$.main(FC2Main.scala:7) [error] at mnist.FC2Main.main(FC2Main.scala) [error] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [error] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [error] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [error] at java.lang.reflect.Method.invoke(Method.java:498) [error] Nonzero exit code: 1 [error] (Test / runMain) Nonzero exit code: 1 [error] Total time: 20041 s, completed Jan 15, 2019 3:04:24 AM [error] (run-main-0) java.lang.AssertionError: assertion failed: This error shows up when I was trying to run a big Chisel program. If the calculation of the program is smaller, it doesn't show up. Basically, my code calculates the multiplications of a few matrices. I increased the sbt memory to the most and deleted the temporary files before running the code.
It would be helpful if you could put the stack trace into your original post as an edit like so: [error] (run-main-0) java.lang.AssertionError: assertion failed: [error] java.lang.AssertionError: assertion failed: [error] at scala.Predef$.assert(Predef.scala:170) [error] at chisel3.core.assert$.apply(Assert.scala:76) [error] at chisel3.iotesters.setupVerilatorBackend$.apply(VerilatorBackend.scala:262) [error] at chisel3.iotesters.Driver$$anonfun$execute$1$$anonfun$apply$mcZ$sp$1.apply$mcZ$sp(Driver.scala:56) In any case, it's pointing to this line: https://github.com/freechipsproject/chisel-testers/blob/8a737012f3c93dd41a3a9e120eebfc07ba541ebf/src/main/scala/chisel3/iotesters/VerilatorBackend.scala#L262 That suggests to me that the Verilator compilation is failing. Do you have other stuff being printed? Perhaps something like: /bin/sh: 1: verilator: not found If that is the case, then you don't have verilator installed, here are the instructions for Linux: https://github.com/freechipsproject/chisel3#ubuntu-like-linux
Duration of starting Mysqld is too long on Lustre file system (InnoDB: Unable to lock ./ibdata1, error: 38)
I can start mysqld and use it normally. But the duration of start is very long (over 3 minuts). When I check log file (/var/log/mysqld.log), I found InnoDB: Unable to lock ./ibdata1, error: 38. Recently, I moved my mysql data from /var/lib/mysql to /home/user/mysql because files are too large. Then I changed datadir in /etc/my.cnf and /etc/init.d/mysqld respectively and changed datasock in etc/my.cnf. Owner and mod of /home/user/mysql and files in it is correctly set as well. The /home volume in this installation is on the Lustre file system. When I found there are 3 innodb engine table in my database, I droped them. But the problem is still here. Here is the log when starting mysqld (/var/log/mysqld.log). 141027 19:40:03 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 141027 19:40:04 mysqld_safe Starting mysqld daemon with databases from /home/user/mysql InnoDB: Unable to lock ./ibdata1, error: 38 141027 19:40:04 InnoDB: Retrying to lock the first data file InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 InnoDB: Unable to lock ./ibdata1, error: 38 141027 19:41:45 InnoDB: Unable to open the first data file InnoDB: Error in opening ./ibdata1 141027 19:41:45 InnoDB: Operating system error number 38 in a file operation. InnoDB: Error number 38 means 'Function not implemented'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html 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! 141027 19:41:45 [ERROR] Plugin 'InnoDB' init function returned error. 141027 19:41:45 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 141027 19:41:45 [Note] Event Scheduler: Loaded 0 events 141027 19:41:45 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.52' socket: '/home/user/mysql/mysql.sock' port: 3306 Source distribution
You're using a Lustre file system for your /home volume. Unless you enable it specifically on a Lustre volume, that file system doesn't support file locking. But InnoDB needs to lock its files to function correctly. So when InnoDB issues the ioctl(2) calls to lock the file, the file system kicks back "Function not implemented." That's what your error log says. InnoDB: Error in opening ./ibdata1 141027 19:41:45 InnoDB: Operating system error number 38 in a file operation. InnoDB: Error number 38 means 'Function not implemented'. Here's a link to an old listserv on this point. http://lists.lustre.org/pipermail/lustre-discuss/2007-August/003768.html Somewhere in that thread somebody mentions how to enable file locking. You may want to work with the people administering your file systems to create a special-purpose Lustre volume for your MySQL database, a volume that has locking enabled. Is this a mission-critical MySQL server? If so, please do a lot of due-diligence before deploying it on this file system.