Every now and again, when installing or upgrading MySQL on Windows, mysqld will not start, and it’s not due to any changes in the config file, using some old config option, permissions, something changed/removed, or anything else. It just simply fails, when you know it should work.
If you’re lucky, you’ll at least see the “Can’t create IP socket: No such file or directory” error in the error log.
However, the above error is generated when you invoke mysqld from the command line, and not via the service.
So if you’re not seeing any error on the console, or in the error log, when starting mysql via the service, then try it from the command line, so you can perhaps get more information in the error log.
The “Can’t create IP socket: No such file or directory” error is not very specific, nor is it helpful in determining the problem (especially since this in on Windows).
However, I’ve found this can occur/or be resolved in a couple ways:
- Re-download the binary (I’ve had this occur if what I downloaded got corrupted somehow)
- Re-extract the binary (I’ve had this occur if the binary got corrupted during the unzip operation)
- Simply try starting mysqld (or service) in a new DOS window (Strange but worked for me the last time I encountered the error, when the above 2 did not)
So next time you run into this error message, give the above a try, before you go rebooting your system, or spending a lot of time commenting out each line in your my.ini file, one-by-one, trying to chase down the offending culprit that doesn’t exist.