• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Knute Snortum
  • Junilu Lacar
  • Devaka Cooray
Saloon Keepers:
  • Ganesh Patekar
  • Tim Moores
  • Carey Brown
  • Stephan van Hulst
  • salvin francis
Bartenders:
  • Ron McLeod
  • Frits Walraven
  • Pete Letkeman

Mysql server failing to start with an AssertionError  RSS feed

 
Ranch Hand
Posts: 624
2
Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Everything was working fine from last few weeks, but today suddenly Mysql server stopped. Now when I am trying to restart it, different errors are coming with respect to the way I am starting the server.   
If starting from Terminal using `mysqld`, the command get stuck and nothing happens:


If start MySQL server from MacOs system preference, on clicking the start button nothing happens.   
I checked for the error logs and I think found the stack where the server suddenly got crashed.

   
I gone through the links suggested in the logs, and found that
1. either this could be caused by a bug
2. or it could be some corrupted data error.

But the data in tables is hardly 5-6 rows and that is text and number. So what is "corrupted data" means here?   
I am newbie to MYSQL, how can I be sure that whether it's a bug or something else.   
**MYSQL version - 8.0.11**   
 
Bartender
Posts: 1856
81
Android Chrome IntelliJ IDE Java MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Are you able to run MySQLCheck to fix the system? You can read more about MySQLCheck here https://dev.mysql.com/doc/refman/8.0/en/mysqlcheck.html.

I suggest that you run mysqlcheck with the --auto-repair and --all-databases options. Depending on the database and the data in the database this could take some time to complete.
There are many other options for mysqlcheck which you may want to look into as well.
 
Pete Letkeman
Bartender
Posts: 1856
81
Android Chrome IntelliJ IDE Java MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You may want to clear out temp files and make sure that you do have enough storage space on your system.
Have you rebooted the system in question?

You may have to supply the configuration/options file to mysqld which you can read about at https://dev.mysql.com/doc/refman/8.0/en/option-files.html
You may want to double check this https://dev.mysql.com/doc/refman/8.0/en/postinstallation.html out to see if everything mention is covered.

I know it's rare, but what if you run "fsck" or whatever the MacOS version is to see if you have any hard drive issues?
 
Puspender Tanwar
Ranch Hand
Posts: 624
2
Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A quote from the link.

mysqlcheck must be used when the mysqld server is running, which means that you do not have to stop the server to perform table maintenance.


In my case the server is down, I cannot run the above suggested command. I get an error
 
Puspender Tanwar
Ranch Hand
Posts: 624
2
Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Pete Letkeman wrote:You may want to clear out temp files and make sure that you do have enough storage space on your system.
Have you rebooted the system in question?


When the server was not starting, after that I rebooted the system but the issue is still there

You may have to supply the configuration/options file to mysqld which you can read about at https://dev.mysql.com/doc/refman/8.0/en/option-files.html
You may want to double check this https://dev.mysql.com/doc/refman/8.0/en/postinstallation.html out to see if everything mention is covered.
I know it's rare, but what if you run "fsck" or whatever the MacOS version is to see if you have any hard drive issues?

I will try these out.

Since one log said the this is a permission issue, I changed the permission of mysql root folder and now the error is changed when started from terminal:
 
Pete Letkeman
Bartender
Posts: 1856
81
Android Chrome IntelliJ IDE Java MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This may help with the data directory https://dev.mysql.com/doc/refman/8.0/en/data-directory-initialization.html, but this may remove the existing data.
For case insensitive look to the options file, in fairly sure there is an option to change this.
 
Bartender
Posts: 19807
93
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Back up to the first error message.

What you you get when you issue the command "df -hT /usr/local/mysql-8.0.11-macos10.13-x86_64/data/" ?

Because this is the kind of error I'd expect to see if you had put your MySQL data on a DOS FAT or NTFS partition.

This isn't a dual-boot Windows/MacOS machine is it?
 
Puspender Tanwar
Ranch Hand
Posts: 624
2
Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I changed the mysql root privileges - didn't help
created a my.cnf file under /etc/mysql folder - didn't help (/data/ directory error)
in my.conf file, give the path of /data directory - didn't help

And since it was taking a lot of time to debug the issue, and nothing was under my Database, I decided to delete the MYSQL and reinstall it. Reinstalling it resolved the issue.
I don't remember exact files of previous installation but I noticed some difference is ..../mysql/ directory this time.
Installation created /data/ directory from root user this time.
 
Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!