MySQL 5.7.9 can't connect to server #46055

Closed
kojustin opened this Issue Nov 17, 2015 · 41 comments

Projects

None yet
@kojustin

I did a homebrew update today and I'm no longer able to connect to a Mysql server that I routinely use. When I use my normal connect command, I get an error about SSL.

$ mysql --version
mysql  Ver 14.14 Distrib 5.7.9, for osx10.11 (x86_64) using  EditLine wrapper
$ mysql --password --verbose --user root --host HOSTNAME.rds.amazonaws.com
Enter password: 
ERROR 2026 (HY000): SSL connection error: error:00000001:lib(0):func(0):reason(1)

I don't have SSL set up for this server so it should not be attempting to use SSL on this connection. I also have MySQL 5.6.27 installed via homebrew. If I brew switch to that version I am able to connect.

To check to see if this was just an issue with MySQL 5.7.9, I downloaded it from mysql.com and tried the binary inside the archive. That version worked correctly. The archive I downloaded was http://dev.mysql.com/get/Downloads/MySQL-5.7/mysql-5.7.9-osx10.10-x86_64.tar.gz, MD5: 1589d67d504ce400bb10bdc875e7679b, Size: 301.3M. The working version of 5.7.9 reports itself as

$ mysql-5.7.9-osx10.10-x86_64/bin/mysql --version
mysql-5.7.9-osx10.10-x86_64/bin/mysql  Ver 14.14 Distrib 5.7.9, for osx10.9 (x86_64) using  EditLine wrapper
@DomT4
Contributor
DomT4 commented Nov 17, 2015

You should back up the directory first, but given the information you've provided here I'd be tempted to try:

rm -r $(brew --prefix)/var/mysql && brew postinstall mysql

And then reattempt the connection.

@kojustin

That does not work for me. I removed that directory and then reinstalled Mysql 5.7.9 from homebrew and I am still getting that error.

Are there any other directories there Mysql from Homebrew might be looking for configuration files?

brew info says....

$ brew info mysql
mysql: stable 5.7.9 (bottled)
Open source relational database management system
https://dev.mysql.com/doc/refman/5.7/en/
Conflicts with: mariadb, mysql-cluster, mysql-connector-c, percona-server
/usr/local/Cellar/mysql/5.7.9 (12629 files, 464M) *
  Poured from bottle
From: https://github.com/Homebrew/homebrew/blob/master/Library/Formula/mysql.rb

It is possible that the bottled binary was built incorrectly? Looking at that Formula, it looks like a build from source. Maybe I should try rebuilding locally?

@MikeMcQuaid
Member

After doing that you will also need to restart your MySQL server's launchd agent. You may want to restart your machine to be extra safe.

@kojustin

Ok I'll try that, but I'm not connecting to the local server instance of MySQL. For my particular use case I am purely installing MySQL to get the command-line mysql client which I am using to connect to remote hosts.

@MikeMcQuaid
Member

Can you download a 10.11 build of MySQL? I'm guessing that connection might be using SSL even without configuration and the change in OpenSSL in 10.11 means it behaves differently.

@kojustin

I don't see a 10.11 build of MySQL on the official site.

http://dev.mysql.com/downloads/mysql

mysql

Does Homebrew have a way for me to choose a build based on the version of OSX?

@drn
Contributor
drn commented Nov 18, 2015

Have been getting this for the past few days as well. I will note that if you're not worried about security, you can bypass the SSL connection error by using the --skip-ssl option. Not a good practice, but it is a temporary workaround.

I'm currently using OS X 10.11 and am receiving the same issue:

❯ mysql --version
mysql  Ver 14.14 Distrib 5.7.9, for osx10.11 (x86_64) using  EditLine wrapper
❯ brew info mysql
mysql: stable 5.7.9 (bottled)
Open source relational database management system
https://dev.mysql.com/doc/refman/5.7/en/
Conflicts with: mariadb, mysql-cluster, mysql-connector-c, percona-server
/usr/local/Cellar/mysql/5.7.9 (12629 files, 464M) *
  Poured from bottle
@drn
Contributor
drn commented Nov 18, 2015

Actually, I just found a bug report that mentions a reason for this issue - https://bugzilla.redhat.com/show_bug.cgi?id=1228755

MySQL server hardcodes 512 bit DH parameters which is severally insecure. See CVE-2015-4000 aka LOGJAM vulnerability. It needs to be fixed to use at least 1024 bit parameters or better.

You should be able to workaround the issue via the --ssl-cipher option. Set it to something like 'DEFAULT:!EDH:!DHE' to disable the DH key exchange method.

I used the --ssl-cipher='DEFAULT:!EDH:!DHE' flag and connected to the database I was having the issue with. Hope it works for you as well

@DomT4
Contributor
DomT4 commented Nov 18, 2015

Comment 9 seems to hint that should be fixed with the 5.7.x release?

@kojustin

This still seems like a build issue to me. As I mentioned in the original report, I was not able to reproduce with official builds of MySQL 5.7.9 off of mysql.com. @drn, perhaps you could try downloading from mysql.com and confirming that the official builds work for you as well?

My reading of that bugzilla issue is the same as @DomT4's. It doesn't seem likely to be the same issue as whatever this bug is. Whatever that bug is covering, the fix should already be present in 5.7.9, which is the version @drn and I are both having trouble with.

Is there a way for me to force Homebrew to install MySQL from source? Or some other way for me to try to reproduce the process that created the bottled version of MySQL? Something changed between the official version built by mysql.com and the built version in homebrew.

@DomT4
Contributor
DomT4 commented Nov 18, 2015

Is there a way for me to force Homebrew to install MySQL from source?

An extremely easy way 😄. brew install mysql -s.

Or some other way for me to try to reproduce the process that created the bottled version of MySQL?

brew install mysql -s --build-bottle
And then:
brew bottle mysql

@kodi
kodi commented Nov 21, 2015

Any workaround on this?

i did this in /etc/my.cnf

[mysqld]
ssl-cipher=DEFAULT:!DH

[mysql]
ssl-cipher=DEFAULT:!DH

and then i was able to connect with mysql -u -h ...command but still, my django/Mysql-python lib is giving same error when i use django to debug remote host (i connect to remote database)

I will try downgrading to homebrew/versions/mysql56 to see if it works threre

@kojustin

Using mysql56 works for me.

@gavsim
gavsim commented Nov 24, 2015

Having similar issues, can't get Ruby on Rails to connect nor can I connect using Sequel Pro since installing mysql 5.7.9

@MikeMcQuaid
Member

@gavsim brew services restart mysql

@kojustin

I can't reproduce my original issue after building from source. I didn't do anything special just brew install -s mysql. Trying to figure out how to package this binary any upload.

@kojustin

@DomT4 @mikemcquaid , is there a way for me to package my local build of mysql so that it can be distributed as a bottle? I read

https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/Bottles.md

but I don't see a section about taking user uploads. If not, is there a process in place to ping Brew Test Bot to ask it to rebuild a bottle?

@kojustin

Actually never mind, please ignore my previous two comments. I was testing incorrectly, I am still seeing the same issue when building mysql 5.7.9 from source.

@MikeMcQuaid
Member

@kojustin https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/Troubleshooting.md#troubleshooting

Please follow these steps and post the information here so we can help you with your problem.

Thanks!

@craigcarnell

Same issue here, downgraded to mysql 5.6. However I am getting:

Quite often

PDOException: SQLSTATE[HY000] [2006] MySQL server has gone away in /Users/ccarnell/Sites/myproject/lib/Zend/Db/Adapter/Pdo/Abstract.php on line 129
@MikeMcQuaid
Member

People having issues here:

  • If you upgraded to MySQL 5.7 and restarted MySQL your local data has been upgraded to the MySQL 5.7 format and after installing MySQL 5.6 it needs to be manually downgraded somehow (I don't know how) or, if it's just development data, just delete var/mysql/mysql and rerun brew postinstall mysql
  • If your MySQL server is not responding then it needs to be manually restarted with e.g. brew services restart mysql or brew services restart mysql56
  • You may have more than one MySQL server trying to run at once. If you're still getting issues after both of the above: try to restart your machine
  • You may also need to manually rebuild any e.g. RubyGems that are built against either MySQL 5.7 or MySQL 5.6 if you have changed version
@kojustin

Here are my brew logs on gist https://gist.github.com/65b917fb4a766ccca091.

To summarize:

  1. I'm only using CLI mysql to connect to remote servers.
  2. Previously working with version 5.6.27 of mysql. mysql --user root --host XXX.us-east-1.rds.amazonaws.com --password
  3. Same command continues to work with the current mysql56 Formula.
  4. Same command is broken with current mysql Formula. Fails with ERROR 2026 (HY000): SSL connection error: error:00000001:lib(0):func(0):reason(1)
  5. Building the brew from source does not fix the issues.
  6. Using a binary of Mysql 5.7.9 (same version as homebrew) from the official site, the original command continues to work.
  7. Based on drn's comment I tried settings the cipher list, I found this is working with the current mysql formula mysql --user root --host XXX.us-east-1.rds.amazonaws.com --password --ssl-cipher='DEFAULT'. The --ssl-cipher flag is documented to passed to SSL.
@DomT4
Contributor
DomT4 commented Nov 25, 2015

On the SSL situation, potentially interesting is that I suspect the upstream binary is built against yaSSL whereas we built it against openssl.

@kojustin

That seems possible. This is from upstream

$ otool -L ~/Downloads/mysql-5.7.9-osx10.10-x86_64/bin/mysql
/Users/kostar/Downloads/mysql-5.7.9-osx10.10-x86_64/bin/mysql:
    /usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0, current version 5.4.0)
    /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 120.0.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1197.1.1)

This is local from home-brew

$ otool -L /usr/local/bin/mysql
/usr/local/bin/mysql:
    /usr/lib/libedit.3.dylib (compatibility version 2.0.0, current version 3.0.0)
    /usr/local/opt/openssl/lib/libssl.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
    /usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
    /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 120.1.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1225.1.1)

The homebrew version is using a dynamic lib of openssl. The upstream version doesn't make any mention of an SSL library.

@DomT4
Contributor
DomT4 commented Nov 25, 2015

I'd be surprised if mysql aren't statically linking any external deps into their release. What's the file size difference between ~/Downloads/mysql-5.7.9-osx10.10-x86_64/bin/mysql and ours?

@kojustin

Upstream is 4.8M, bottled version is 3.7M

@nfagen
nfagen commented Dec 3, 2015

Recently ran into this issue after a brew update on osx 10.11.1 I am using the gem mysql2 to connect to a remote server during some watir automation. Was receiving this error: ERROR 2026 (HY000): SSL connection error: error:00000001:lib(0):func(0):reason(1)

What fixed it for me was:

  1. homebrew uninstall mysql
  2. home brew install homebrew/versions/mysql56
  3. brew link mysql56
  4. Then I uninstalled mysql2 since it was built against the breaking mysql: gem uninstall mysql2
  5. I then reinstalled mysql2 0.3.19(version I use) so it's built against mysql56: gem install mysql -v0.3.19

This fixed the ssl connection error I was receiving when the remote server doesn't require one. I can now connect to the db's as expected with no issues anymore. Hopefully this helps someone else in a similar situation.

@mvabl-steve

I'm not a developer, and I think my question may be very basic. But I don't know where else to ask.

I use MySQL for data analysis & things like R. I know almost nothing about using CLI. I usually connect to MySQL with a 3rd-party GUI.

I work on a MacBook Pro with El Capitan. A while back, maybe on Yosemite, I started using Homebrew, and brew installed MySQL.

I had everything working fine, until I ran brew upgrade a couple weeks ago, the one for El Cap. Suddenly, nothing will connect to MySQL, and if I access it via CLI, it points to an empty environment - no databases except the info/schema one.

I know I didn't lose my data. I suspect I actually may have two installations of MySQL - one Home-brewed, and one factory-installed.

Can anyone give me some pointers on how to figure this out, and if I do have two installs, how to reconcile them and then remove the factory-installed version?

I did run

Steves-MacBook-Pro:~ steves93$ mysql --version
mysql  Ver 14.14 Distrib 5.7.9, for osx10.11 (x86_64) using  EditLine wrapper

and

Steves-MacBook-Pro:~ steves93$ brew info mysql
mysql: stable 5.7.9 (bottled)
Open source relational database management system
https://dev.mysql.com/doc/refman/5.7/en/
Conflicts with: mariadb, mysql-cluster, mysql-connector-c, percona-server
/usr/local/Cellar/mysql/5.7.9 (12629 files, 464M) *
  Poured from bottle
From: https://github.com/Homebrew/homebrew/blob/master/Library/Formula/mysql.rb
==> Dependencies
Build: cmake ✔
Required: openssl ✔, boost ✔
==> Options
--universal
    Build a universal binary
--with-archive-storage-engine
    Compile with the ARCHIVE storage engine enabled
--with-blackhole-storage-engine
    Compile with the BLACKHOLE storage engine enabled
--with-debug
    Build with debug support
--with-embedded
    Build the embedded server
--with-local-infile
    Build with local infile loading support
--with-memcached
    Enable innodb-memcached support
--with-tests
    Build with unit tests
==> Caveats
We've installed your MySQL database without a root password. To secure it run:
    mysql_secure_installation

To connect run:
    mysql -uroot

To have launchd start mysql at login:
  ln -sfv /usr/local/opt/mysql/*.plist ~/Library/LaunchAgents
Then to load mysql now:
  launchctl load ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist
Or, if you don't want/need launchctl, you can just run:
  mysql.server start

Sorry if this is too n00b a question for here.

@pioneerskies

@mvabl-steve have you tried

mysql_upgrade -u root

or possibly if it didn't work

mysql_upgrade -u root --force --upgrade-system-tables

Upgrading to 5.7 requires an update to tables.

Think about do a backup before launch the command if you have important data.

@mvabl-steve

@pioneerskies:

Steves-MacBook-Pro:~ steves93$ mysql_upgrade -u root
Checking if update is needed.
Checking server version.
Running queries to upgrade MySQL server.
Checking system database.
mysql.columns_priv                                 OK
mysql.db                                           OK
mysql.engine_cost                                  OK
mysql.event                                        OK
mysql.func                                         OK
mysql.general_log                                  OK
mysql.gtid_executed                                OK
mysql.help_category                                OK
mysql.help_keyword                                 OK
mysql.help_relation                                OK
mysql.help_topic                                   OK
mysql.innodb_index_stats                           OK
mysql.innodb_table_stats                           OK
mysql.ndb_binlog_index                             OK
mysql.plugin                                       OK
mysql.proc                                         OK
mysql.procs_priv                                   OK
mysql.proxies_priv                                 OK
mysql.server_cost                                  OK
mysql.servers                                      OK
mysql.slave_master_info                            OK
mysql.slave_relay_log_info                         OK
mysql.slave_worker_info                            OK
mysql.slow_log                                     OK
mysql.tables_priv                                  OK
mysql.time_zone                                    OK
mysql.time_zone_leap_second                        OK
mysql.time_zone_name                               OK
mysql.time_zone_transition                         OK
mysql.time_zone_transition_type                    OK
mysql.user                                         OK
Upgrading the sys schema.
Checking databases.
mfmm.beta_group                                    OK
mfmm.mail_sent                                     OK
mfmm.mailchimp                                     OK
mfmm.messages                                      OK
mfmm.user_profiles                                 OK
mfmm.web_signups                                   OK
moveablefeast.adhoc_users                          OK
moveablefeast.app_starts                           OK
moveablefeast.beta_feedbacks                       OK
moveablefeast.catalog_items                        OK
moveablefeast.catalog_items_media_items            OK
moveablefeast.catalog_items_tour_categories        OK
moveablefeast.events                               OK
moveablefeast.file_chunks                          OK
moveablefeast.follows                              OK
moveablefeast.invitation_requests                  OK
moveablefeast.invitations                          OK
moveablefeast.media_bindings                       OK
moveablefeast.media_items                          OK
moveablefeast.purchases                            OK
moveablefeast.schema_migrations                    OK
moveablefeast.splash_ads                           OK
moveablefeast.system_events                        OK
moveablefeast.tour_categories                      OK
moveablefeast.users                                OK
moveablefeast.waypoint_headings                    OK
moveablefeast.waypoints                            OK
moveablefeast.whitelabel_clients                   OK
blog.wp_cat                                        OK
blog.wp_categories                                 OK
blog.wp_content                                    OK
blog.wp_dates                                      OK
blog.wp_tag                                        OK
blog.wp_tags                                       OK
contacts.mc1_unsub                                 OK
contacts.mclaunch_unsub                            OK
contacts.stmarksny                                 OK
contacts.allemails                                 OK
contacts.backers                                   OK
contacts.bounces                                   OK
contacts.circles                                   OK
contacts.contact                                   OK
contacts.goog                                      OK
contacts.journalists                               OK
contacts.linked                                    OK
contacts.mac                                       OK
contacts.mailchimp                                 OK
contacts.mailings                                  OK
contacts.master                                    OK
contacts.tiers                                     OK
contacts.web_signups                               OK
sandbox.mrap                                       OK
sandbox.nypd_claims                                OK
sandbox.nypd_closed                                OK
sandbox.airbnbny                                   OK
sandbox.naics                                      OK
sandbox.uber                                       OK
sys.sys_config                                     OK
Upgrade process completed successfully.
Checking if update is needed.

This confirms that I haven't lost my data. How do I figure out how to get the data from this into the brew-installed version, and then _completely remove_ this install?

Thanks!

@pioneerskies

Should I deduce you still can't

mysql -u root

and gain access to the database?

@mvabl-steve

@pioneerskies I did that successfully. I'm in it now. Everything I want to save is there. I just want it in the homebrew install. (And then I want to remove the factory-installed version, and figure out how to connect my 3rd party apps like SequelPro and RStudio to the right place.

(By the way, I can't seem to get mysqldump to work! But that's a question for a different board!)

Again, thanks for helping me so far. I'm pretty good at reading/following directions with CLI, so if you can just point me in the right direction to figure it out for myself, I will!

@mvabl-steve

whoa... everything's working as expected now. weird.

thanks @pioneerskies. whatever we did just magically made everything go back to normal.

@pioneerskies

OK...I haven't enough comprehension about your environment, but: mysql is a client, connecting to your mysql server through a socket or a port. As far as you are able to connect through mysql command you should be able to connect though Sequel Pro (try both standard and socket connection).

If you have multiple installation it should be just ok, as far as you launch the right one. For example I launch my server w/ the mysql.server start command:

⟩ which mysql.server                                                      [ruby 2.2.3]
/usr/local/bin/mysql.server

⟩ ll /usr/local/bin/mysql.server                                          [ruby 2.2.3]
lrwxr-xr-x  1 fuzzy  admin    38B  4 Dic 16:26 /usr/local/bin/mysql.server@ -> ../Cellar/mysql/5.7.9/bin/mysql.server

As you can see it points to the script inside /usr/local/Cellar folder, which is the homebrew folder, so I'm happy with it and you should be happy too if it's the same for you :)

@pioneerskies

Ok, just late to see your previous reply. Happy it's working right now :)

Cheers

@Whitespace

I was originally following http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Aurora.html#Aurora.Overview.Security.SSL to connect to a recently created Aurora instance.

I had to disallow DHE-based ciphersuites via --ssl-cipher='DEFAULT:!DHE' and removing the --ssl-verify-server-certand --ssl-ca flags.

The following then worked for me:

mysql --ssl-cipher='DEFAULT:!DHE' -h my-aurora-cluster.cluster-deadbeef.us-east-1.rds.amazonaws.com --user user_name -p database_name
@DomT4
Contributor
DomT4 commented Dec 12, 2015

Can anyone still experiencing this try again with the newly updated MySQL. The new release fixed a small bunch of SSL oddities that may well be related here: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-10.html

@kwantopia

My connection also worked by passing:

--ssl-cipher='DEFAULT:!EDH:!DHE'

to mysql client. Also when using python MySQL-python I had to pass the following dicitionary to connect method

ssl = {'cipher': 'DEFAULT:!EDH:!DHE'}
@kojustin

The new bottled version 5.7.10 resolves my issue, I can connect to my server with my original invocation. I am ok with closing this now.

@mvabl-steve

I just ran brew upgrade, and now am having trouble with MySQL again. I apologize for the long block below, which I copied from my CLI. I'm in over my head!

Steves-MBP:~ steves93$ mysql.server start
Starting MySQL
..................................................................................................... ERROR! The server quit without updating PID file (/usr/local/var/mysql/Steves-MBP.pid).
Steves-MBP:~ steves93$ mysqld
2015-12-14T19:13:11.889018Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-12-14T19:13:11.889548Z 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2015-12-14T19:13:11.889633Z 0 [Note] mysqld (mysqld 5.7.9) starting as process 22494 ...
2015-12-14T19:13:11.894513Z 0 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
2015-12-14T19:13:11.896801Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-12-14T19:13:11.896838Z 0 [Note] InnoDB: Uses event mutexes
2015-12-14T19:13:11.896847Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2015-12-14T19:13:11.896854Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-12-14T19:13:11.897374Z 0 [Note] InnoDB: Number of pools: 1
2015-12-14T19:13:11.897632Z 0 [Note] InnoDB: Using CPU crc32 instructions
2015-12-14T19:13:11.913178Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2015-12-14T19:13:11.928709Z 0 [Note] InnoDB: Completed initialization of buffer pool
2015-12-14T19:13:11.942797Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:11.942848Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:11.942864Z 0 [Note] InnoDB: Retrying to lock the first data file
2015-12-14T19:13:12.946774Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:12.946847Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:13.949985Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:13.950068Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:14.951763Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:14.951863Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:15.952913Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:15.952998Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:16.954934Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:16.954999Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:17.959658Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:17.959744Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:18.964868Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:18.964957Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:19.969266Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:19.969471Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:20.971229Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:20.971311Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:21.972339Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:21.972429Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:22.976279Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:22.976370Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:23.981518Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:23.981607Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:24.982196Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:24.982294Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:25.987492Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:25.987603Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:26.988242Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:26.988315Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:27.988547Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:27.988616Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:28.993734Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:28.993823Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:29.998968Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:29.999055Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:31.002313Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:31.002404Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:32.006041Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:32.006159Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:33.008469Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:33.008655Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:34.009650Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:34.009697Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:35.010678Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:35.010802Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:36.013644Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:36.013734Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:37.017255Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:37.017351Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:38.018510Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:38.018596Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:39.021667Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:39.021825Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:40.026634Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:40.026725Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:41.027671Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:41.027734Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:42.032925Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:42.033016Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:43.036676Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:43.036751Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:44.041878Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:44.041953Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:45.045714Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:45.045784Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:46.050633Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:46.050716Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:47.052255Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:47.052337Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:48.057235Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:48.057308Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:49.062377Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:49.062449Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:50.067540Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:50.067612Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:51.069968Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:51.070087Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:52.074098Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:52.074180Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:53.079298Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:53.079386Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:54.082118Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:54.082216Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:55.084852Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:55.084935Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:56.087520Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:56.087657Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:57.089933Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:57.090007Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:58.091400Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:58.091465Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:13:59.093345Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:13:59.093424Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:00.098155Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:00.098307Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:01.101295Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:01.101354Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:02.106446Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:02.106519Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:03.109034Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:03.109107Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:04.114235Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:04.114320Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:05.117659Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:05.117741Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:06.118150Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:06.118234Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:07.122780Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:07.122850Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:08.124921Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:08.125011Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:09.126043Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:09.126161Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:10.128665Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:10.128712Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:11.129084Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:11.129127Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:12.133887Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:12.133928Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:13.135791Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:13.135857Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:14.137790Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:14.137877Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:15.140849Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:15.140919Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:16.145682Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:16.145751Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:17.147617Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:17.147725Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:18.152380Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:18.152471Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:19.157635Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:19.157709Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:20.158571Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:20.158622Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:21.162003Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:21.162032Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:22.167140Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:22.167221Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:23.172167Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:23.172250Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:24.172310Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:24.172340Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:25.177411Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:25.177486Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:26.177893Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:26.177947Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:27.181207Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:27.181248Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:28.182331Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:28.182393Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:29.186975Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:29.187030Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:30.188123Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:30.188188Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:31.191264Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:31.191330Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:32.192989Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:32.193072Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:33.194101Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:33.194137Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:34.199236Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:34.199311Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:35.199708Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:35.199760Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:36.199903Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:36.199951Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:37.202163Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:37.202248Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:38.207185Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:38.207219Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:39.210645Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:39.210684Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:40.214027Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:40.214056Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:41.218073Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:41.218165Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:42.220316Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:42.220388Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:43.222283Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:43.222488Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:44.225256Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:44.225375Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:45.226034Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:45.226099Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:46.226831Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:46.226870Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:47.228892Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:47.228927Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:48.230576Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:48.230629Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:49.234073Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:49.234198Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:50.237979Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:50.238038Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:51.242104Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:51.242134Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:52.243021Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2015-12-14T19:14:52.243110Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-12-14T19:14:52.243146Z 0 [Note] InnoDB: Unable to open the first data file
2015-12-14T19:14:52.243226Z 0 [ERROR] InnoDB: Operating system error number 35 in a file operation.
2015-12-14T19:14:52.243306Z 0 [ERROR] InnoDB: Error number 35 means 'Resource temporarily unavailable'
2015-12-14T19:14:52.243324Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2015-12-14T19:14:52.243337Z 0 [ERROR] InnoDB: Cannot open datafile './ibdata1'
2015-12-14T19:14:52.243356Z 0 [ERROR] 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!
2015-12-14T19:14:52.243386Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Cannot open a file
2015-12-14T19:14:52.549924Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2015-12-14T19:14:52.549971Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2015-12-14T19:14:52.549988Z 0 [ERROR] Failed to initialize plugins.
2015-12-14T19:14:52.549998Z 0 [ERROR] Aborting

2015-12-14T19:14:52.550020Z 0 [Note] Binlog end
2015-12-14T19:14:52.550173Z 0 [Note] Shutting down plugin 'CSV'
2015-12-14T19:14:52.550478Z 0 [Note] mysqld: Shutdown complete

@kojustin

@mvabl-steve not sure what you are seeing but maybe you're running more than one instance of mysql server?

I'm closing this. My original issue is resolved, and none of the other participants in this thread have chimed in to say they are seeing this issue anymore.

@kojustin kojustin closed this Dec 17, 2015
@MikeMcQuaid MikeMcQuaid locked and limited conversation to collaborators Jul 10, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.