Really frustrated by MySql on start up server - mysql

I've been trying to figure out this problem for like two days straight, please help.
I'm relatively a noobie, so please bear with me...
I installed MySql, latest version, using the dumbest way, i.e. dmg file, and also workbench from MySql site.
For the very first time, I used system preference to start the server, everything worked out fine. Then, I tried to create the sample database by using the sample scheme and insert statement files from MySql site. But when I tried to execute those two files, I was prompted for entering password, I had no idea what's going on at that moment, so I closed everything, Googled about how to set up my own password for the root user account for MySql, and used mysqldadmin setpassword... something like that to reset the root password.
Then, the nightmare starts... Since then, no matter which method I tried to use to start up the server, no luck, i.e. system preference, manually. (I do have the PATH environment variable set up correctly btw).
So, here're the two errors I'm getting,
if I just use sudo mysqld:
2015-02-10 20:45:58 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-02-10 20:45:58 49381 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/mysql-5.6.23-osx10.8-x86_64/data/ is case insensitive
2015-02-10 20:45:58 49381 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!
2015-02-10 20:45:58 49381 [ERROR] Aborting
2015-02-10 20:45:58 49381 [Note] Binlog end
2015-02-10 20:45:58 49381 [Note] mysqld: Shutdown complete
if I tried this sudo mysqld -u root -p mypassword:
2015-02-10 20:10:22 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-02-10 20:10:22 48437 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/mysql-5.6.23-osx10.8-x86_64/data/ is case insensitive
2015-02-10 20:10:22 48437 [Note] Plugin 'FEDERATED' is disabled.
2015-02-10 20:10:22 48437 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-10 20:10:22 48437 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-10 20:10:22 48437 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-02-10 20:10:22 48437 [Note] InnoDB: Memory barrier is not used
2015-02-10 20:10:22 48437 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-10 20:10:22 48437 [Note] InnoDB: Using CPU crc32 instructions
2015-02-10 20:10:22 48437 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-02-10 20:10:22 48437 [Note] InnoDB: Completed initialization of buffer pool
2015-02-10 20:10:22 48437 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2015-02-10 20:10:22 48437 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-02-10 20:10:22 48437 [Note] InnoDB: Retrying to lock the first data file
I try to make some config change in my.cnf file, but I can't even find it under my /etc/ directory...
Any help would be extremely appreciated, I'm really starting to hate myself... T.T
p.s. when I tried using mysqld-safe, it looks like the server has been started, but in the workbench, it clearly says the server is still stopped...

Related

Error: MySQL shutdown unexpectedly XAMPP Plugin 'InnoDB' init function returned error [duplicate]

I restarted my server because it froze (probably the stupidest thing I did so far) and then got some internal server errors. I soon discovered that mysql had failed on startup (service mysql status).
I read the mysql error log( Pastebin ) and started googling.
I'm running Ubuntu at its latest version, mysql Ver 14.14 Distrib 5.7.31, for Linux (x86_64) using EditLine wrapper.
What I tried:
deleting both ib_logfile (after doing a backup) in /var/lib/mysql
apt-get upgrade (I really don't know why)
-checking my.cf for errors
Here is my /var/log/mysql/error.log
2020-08-07T15:43:06.094116Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-08-07T15:43:06.095903Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.31-0ubuntu0.18.04.1) starting as process 952 ...
2020-08-07T15:43:06.100450Z 0 [Note] InnoDB: PUNCH HOLE support available
2020-08-07T15:43:06.100482Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-08-07T15:43:06.100489Z 0 [Note] InnoDB: Uses event mutexes
2020-08-07T15:43:06.100496Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2020-08-07T15:43:06.100502Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-08-07T15:43:06.100508Z 0 [Note] InnoDB: Using Linux native AIO
2020-08-07T15:43:06.100771Z 0 [Note] InnoDB: Number of pools: 1
2020-08-07T15:43:06.100876Z 0 [Note] InnoDB: Using CPU crc32 instructions
2020-08-07T15:43:06.102827Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2020-08-07T15:43:06.112754Z 0 [Note] InnoDB: Completed initialization of buffer pool
2020-08-07T15:43:06.114871Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-08-07T15:43:06.127135Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2020-08-07T15:43:06.128655Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 7945493345
2020-08-07T15:43:06.128723Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7945545114
2020-08-07T15:43:06.130551Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 7945493345 and the end 7945545114.
2020-08-07T15:43:06.130573Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2020-08-07T15:43:06.732437Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2020-08-07T15:43:06.732470Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2020-08-07T15:43:06.732482Z 0 [ERROR] Failed to initialize builtin plugins.
2020-08-07T15:43:06.732491Z 0 [ERROR] Aborting
2020-08-07T15:43:06.732526Z 0 [Note] Binlog end
2020-08-07T15:43:06.732586Z 0 [Note] Shutting down plugin 'CSV'
2020-08-07T15:43:06.732959Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
If you need more logs/informations, I will provide them.
Thanks, I'm really desperate, I really don't want to loose the past 2 years of my life.
For MYSQL not starting in XAMP
Here is a good fix that worked for me
Navigate to /var/lib/mysql.
If you see log files like, ib_logfile0 and ib_logfile1, rename or
move them to some other folder.
Stop and start the MySQL service.
That`s all.
Before deleting ib_logfile0, ib_logfile1 and ibdata1, I started mysql in InnoDB recovery mod 4 and logged in to phpmyadmin to backup all of my databases. After that I removed the ib files, purged mysql and phpmyadmin, reinstalled them, reconfigured mysql, logged into phpmyadmin and imported my databases.

MYSQL not starting (InnoDB: Plugin initialization aborted with error Generic error)

I restarted my server because it froze (probably the stupidest thing I did so far) and then got some internal server errors. I soon discovered that mysql had failed on startup (service mysql status).
I read the mysql error log( Pastebin ) and started googling.
I'm running Ubuntu at its latest version, mysql Ver 14.14 Distrib 5.7.31, for Linux (x86_64) using EditLine wrapper.
What I tried:
deleting both ib_logfile (after doing a backup) in /var/lib/mysql
apt-get upgrade (I really don't know why)
-checking my.cf for errors
Here is my /var/log/mysql/error.log
2020-08-07T15:43:06.094116Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-08-07T15:43:06.095903Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.31-0ubuntu0.18.04.1) starting as process 952 ...
2020-08-07T15:43:06.100450Z 0 [Note] InnoDB: PUNCH HOLE support available
2020-08-07T15:43:06.100482Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-08-07T15:43:06.100489Z 0 [Note] InnoDB: Uses event mutexes
2020-08-07T15:43:06.100496Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2020-08-07T15:43:06.100502Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-08-07T15:43:06.100508Z 0 [Note] InnoDB: Using Linux native AIO
2020-08-07T15:43:06.100771Z 0 [Note] InnoDB: Number of pools: 1
2020-08-07T15:43:06.100876Z 0 [Note] InnoDB: Using CPU crc32 instructions
2020-08-07T15:43:06.102827Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2020-08-07T15:43:06.112754Z 0 [Note] InnoDB: Completed initialization of buffer pool
2020-08-07T15:43:06.114871Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-08-07T15:43:06.127135Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2020-08-07T15:43:06.128655Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 7945493345
2020-08-07T15:43:06.128723Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7945545114
2020-08-07T15:43:06.130551Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 7945493345 and the end 7945545114.
2020-08-07T15:43:06.130573Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2020-08-07T15:43:06.732437Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2020-08-07T15:43:06.732470Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2020-08-07T15:43:06.732482Z 0 [ERROR] Failed to initialize builtin plugins.
2020-08-07T15:43:06.732491Z 0 [ERROR] Aborting
2020-08-07T15:43:06.732526Z 0 [Note] Binlog end
2020-08-07T15:43:06.732586Z 0 [Note] Shutting down plugin 'CSV'
2020-08-07T15:43:06.732959Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
If you need more logs/informations, I will provide them.
Thanks, I'm really desperate, I really don't want to loose the past 2 years of my life.
For MYSQL not starting in XAMP
Here is a good fix that worked for me
Navigate to /var/lib/mysql.
If you see log files like, ib_logfile0 and ib_logfile1, rename or
move them to some other folder.
Stop and start the MySQL service.
That`s all.
Before deleting ib_logfile0, ib_logfile1 and ibdata1, I started mysql in InnoDB recovery mod 4 and logged in to phpmyadmin to backup all of my databases. After that I removed the ib files, purged mysql and phpmyadmin, reinstalled them, reconfigured mysql, logged into phpmyadmin and imported my databases.

Can no longer run mysql with homebrew

I had mysql running fine on my Mac running High Sierra, 10.13.5. Last night, however, the system rebooted in the middle of the night for some unknown reason and I haven't been able to get things back and running properly since.
When I run brew services start mysql I get:
Successfully startedmysql(label: homebrew.mxcl.mysql)
in response. However, ps aux | grep mysql shows no running server and I cannot log into mysql. If I run, mysql.server start I get:
. ERROR! The server quit without updating PID file (/usr/local/var/mysql/iMac-5K-3.local.pid).
The error file contents are as follows:
2018-06-18T13:51:57.6NZ mysqld_safe mysqld from pid file /usr/local/var/mysql/iMac-5K-3.local.pid ended
2018-06-18T13:52:07.6NZ mysqld_safe Logging to '/usr/local/var/mysql/iMac-5K-3.local.err'.
2018-06-18T13:52:07.6NZ mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
2018-06-18T13:52:07.837840Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-06-18T13:52:07.838096Z 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.
2018-06-18T13:52:07.838155Z 0 [Note] /usr/local/opt/mysql/bin/mysqld (mysqld 5.7.22) starting as process 8334 ...
2018-06-18T13:52:07.840681Z 0 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
2018-06-18T13:52:07.841958Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-06-18T13:52:07.841975Z 0 [Note] InnoDB: Uses event mutexes
2018-06-18T13:52:07.841983Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-06-18T13:52:07.841990Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-18T13:52:07.842257Z 0 [Note] InnoDB: Number of pools: 1
2018-06-18T13:52:07.842356Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-06-18T13:52:07.843494Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-06-18T13:52:07.852043Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-06-18T13:52:07.901671Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-06-18T13:52:07.902006Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 2700829144 and the end 2700828672.
2018-06-18T13:52:07.902049Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2018-06-18T13:52:08.338717Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2018-06-18T13:52:08.338812Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-06-18T13:52:08.338823Z 0 [ERROR] Failed to initialize builtin plugins.
2018-06-18T13:52:08.338835Z 0 [ERROR] Aborting
2018-06-18T13:52:08.338849Z 0 [Note] Binlog end
2018-06-18T13:52:08.338929Z 0 [Note] Shutting down plugin 'CSV'
2018-06-18T13:52:08.339077Z 0 [Note] /usr/local/opt/mysql/bin/mysqld: Shutdown complete
2018-06-18T13:52:08.6NZ mysqld_safe mysqld from pid file /usr/local/var/mysql/iMac-5K-3.local.pid ended
OK, found the solution here.
I didn't bother with step 1 since I don't have a master/slave setup. I just did:
mv /var/lib/mysql/ib_logfile* ~
I can now start mysql successfully.

Cannot start mySQL "mysqld: Too many arguments (first extra is 'start')."

I want to start mysql but this immediately shows up, I don't realy know how to solve it, can you please help me?
I have Ubuntu 14.04
this is what appears in the terminal.
dyphen#dyphen12-GNU:/etc/mysql$ sudo mysqld start
180510 5:55:25 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
180510 5:55:25 [Warning] Insecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.
180510 5:55:25 [Note] mysqld (mysqld 5.5.60-0ubuntu0.14.04.1) starting as process 7158 ...
180510 5:55:25 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
180510 5:55:25 [Note] Plugin 'FEDERATED' is disabled.
mysqld: Table 'mysql.plugin' doesn't exist
180510 5:55:25 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
180510 5:55:25 InnoDB: The InnoDB memory heap is disabled
180510 5:55:25 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180510 5:55:25 InnoDB: Compressed tables use zlib 1.2.8
180510 5:55:25 InnoDB: Using Linux native AIO
180510 5:55:25 InnoDB: Initializing buffer pool, size = 128.0M
180510 5:55:25 InnoDB: Completed initialization of buffer pool
180510 5:55:25 InnoDB: highest supported file format is Barracuda.
180510 5:55:26 InnoDB: Waiting for the background threads to start
180510 5:55:27 InnoDB: 5.5.60 started; log sequence number 1595675
mysqld: Too many arguments (first extra is 'start').
Use --verbose --help to get a list of available options
180510 5:55:27 [ERROR] Aborting
180510 5:55:27 InnoDB: Starting shutdown...
180510 5:55:28 InnoDB: Shutdown completed; log sequence number 1595675
180510 5:55:28 [Note] mysqld: Shutdown complete
llja is right. I made the same mistake. To start mysqld, simply type
mysqld
If a new problem surface, check /var/log/mysql/error.log for ERROR messages.

MySQL has broke, can not be started: "Restoring possible half-written data pages from the doublewrite buffer..."

When attempting to start the mysql server, it returns with exit code 1. I've done this a million times before on this server. Without messing with the server in the past month, mysql has suddenly stopped and I can not start it. My error.log:
[Note] InnoDB: Using mutexes to ref count buffer pool pages
[Note] InnoDB: The InnoDB memory heap is disabled
[Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
[Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
[Note] InnoDB: Compressed tables use zlib 1.2.8
[Note] InnoDB: Using Linux native AIO
[Note] InnoDB: Using SSE crc32 instructions
[Note] InnoDB: Initializing buffer pool, size = 128.0M
[Note] InnoDB: Completed initialization of buffer pool
[Note] InnoDB: Highest supported file format is Barracuda.
[Note] InnoDB: Starting crash recovery from checkpoint LSN=591771482442
Everything goes to ruin below this line.
[Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
InnoDB: Set innodb_force_recovery to ignore this error.
[ERROR] Plugin 'InnoDB' init function returned error.
[ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
[Note] Plugin 'FEEDBACK' is disabled.
[ERROR] Unknown/unsupported storage engine: InnoDB
[ERROR] Aborting
Until I can start mysql-server, I can not run mysqldump nor mysql -u root:
Got error: 2002: "Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")" when trying to connect
I'm running mariadb-server 10.1.23-9-deb9u1.
Not sure if this will work but since the server doesn't work anyway so try this out:
Rename logfile0 and logfile1 and then restart the server.
Before doing anything, make a copy of the entire mysql folder to another location just in case.
The answer was right infront of me:
InnoDB: Set innodb_force_recovery to ignore this error.
I set innodb_force_recovery = 1 after the [mysqld] clause in my /etc/mysql/mariadb.conf.d/50-server.cnf (This file may very depending on your OS).
I restarted it and it repaired itself. I later took out the innodb_force_recovery = 1 and restarted again, it then worked just fine.
What did I learn? Have more faith in "auto-repair" procedures. My expectations were so low for them because of my exposure to Microsoft Windows.