Mysql server not starting on uwamp 3.1 - uwamp

Mysql Server stop working after 5 seconds (fresh install of uwamp)
Uwamp version 3.1 started with Administrator rights on windows 10 32bits.
Here is the Mysql log :
2016-02-25T13:53:19.049733Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-02-25T13:53:19.049733Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2016-02-25T13:53:19.049733Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2016-02-25T13:53:19.049733Z 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.
2016-02-25T13:53:19.050735Z 0 [Note] C:\UwAmp\bin\database\mysql-5.7.11\bin\mysqld.exe (mysqld 5.7.11) starting as process 6552 ...
2016-02-25T13:53:19.117843Z 0 [ERROR] Can't open shared library 'C:\UwAmp\bin\database\mysql-5.7.11\lib\plugin\keyring_file.dll' (errno: 126 Le module spécifié est introuvable.)
2016-02-25T13:53:19.122851Z 0 [ERROR] Couldn't load plugin named 'keyring_file' with soname 'keyring_file.dll'.
2016-02-25T13:53:19.127856Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-02-25T13:53:19.130861Z 0 [Note] InnoDB: Uses event mutexes
2016-02-25T13:53:19.132864Z 0 [Note] InnoDB: Memory barrier is not used
2016-02-25T13:53:19.134867Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-02-25T13:53:19.137871Z 0 [Note] InnoDB: Number of pools: 1
2016-02-25T13:53:19.139875Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2016-02-25T13:53:21.056091Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2016-02-25T13:53:21.087354Z 0 [Note] InnoDB: Completed initialization of buffer pool
2016-02-25T13:53:21.234144Z 0 [Note] InnoDB: Setting log file .\ib_logfile101 size to 48 MB
2016-02-25T13:53:22.659215Z 0 [Note] InnoDB: Setting log file .\ib_logfile1 size to 48 MB
2016-02-25T13:53:24.176685Z 0 [Note] InnoDB: Renaming log file .\ib_logfile101 to .\ib_logfile0
2016-02-25T13:53:24.176685Z 0 [Warning] InnoDB: New log files created, LSN=2602779
2016-02-25T13:53:24.176685Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2016-02-25T13:53:24.192315Z 0 [ERROR] InnoDB: Operating system error number 87 in a file operation.
2016-02-25T13:53:24.192315Z 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
2016-02-25T13:53:24.192315Z 0 [ERROR] InnoDB: File .\ib_logfile0: 'aio read' returned OS error 187. Cannot continue operation
2016-02-25T13:53:24.192315Z 0 [ERROR] InnoDB: Cannot continue operation.

In the uwAmp control panel, click on XDebug client and select "Remove MySql log".Then try to start MySQL in the top of control panel. It must works fine.

I had the same issue. Try the following://in my case it worked
Step 1: Download and install the wamp server app from the http://www.wampserver.com/
Step 2: Open the wamp server installation folder of the wamp server app. In my case is C:\wamp64
Step 3: Once inside the wamp folder, open the folders in the following sequence bin\mysql\mysql5.7.14
Step 4: You should find in here a folder called lib
Step 5: Copy the folder lib to your UwAmp folder but not just to folder but to the UwAmp\bin\database\mysql-5.7.11- here.
Step 6: Restart the UwAmp or stop the server and restart it again.
Step 7: At this stage the MySQl should work.

Related

I get the follow LOG Error in XAMPP, How do I fix this

I get this error code shown, below how to I fix this,if not fixed I need to copy my coding that is in the htp folder and saved them in a different file, and reinstall it again.
2023-02-08 8:52:13 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-02-08 8:52:13 0 [Note] InnoDB: Uses event mutexes
2023-02-08 8:52:13 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-02-08 8:52:13 0 [Note] InnoDB: Number of pools: 1
2023-02-08 8:52:13 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-02-08 8:52:13 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-02-08 8:52:13 0 [Note] InnoDB: Completed initialization of buffer pool
2023-02-08 8:52:13 0 [ERROR] InnoDB: Missing MLOG_CHECKPOINT at 80837091 between the checkpoint 80837091 and the end 80837082.
2023-02-08 8:52:13 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2023-02-08 8:52:14 0 [Note] InnoDB: Starting shutdown...
2023-02-08 8:52:14 0 [ERROR] Plugin 'InnoDB' init function returned error.
2023-02-08 8:52:14 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2023-02-08 8:52:14 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-02-08 8:52:14 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2023-02-08 8:52:14 0 [ERROR] Aborting
Maybe you got another MySQL/MariaDB Server running already?
What is the full contents of your XAMPP control panel log?
Step 1: Open Xampp Control Panel
Xampp Control Panel
Step 2: Click on Config -> Click on Service and Port Settings
Click Configure Button
Step 3: Click on MySQL Tab and change port to 3307 (Note: any other port which is free in your system)
Step 4: Click on Save -> Save.
Save Service Settings
Step 5: Restart your Xampp Control Panel

MariaDB shutdown unexpectedly. mysqld.exe: Aria recovery failed

mysqld.exe: Aria recovery failed. Please run aria_chk -r on all Aria tables and delete all aria_log.######## files
I am using xampp and it was working perfectly. Today when I started my Windows computer and tried to start the MariaDB Server from xampp control panel v3.3.0 the xampp showed the following error:
9:37:34 AM [mysql] Error: MySQL shutdown unexpectedly.
9:37:34 AM [mysql] This may be due to a blocked port, missing dependencies,
9:37:34 AM [mysql] improper privileges, a crash, or a shutdown by another method.
9:37:34 AM [mysql] Press the Logs button to view error logs and check
9:37:34 AM [mysql] the Windows Event Viewer for more clues
9:37:34 AM [mysql] If you need more help, copy and post this
9:37:34 AM [mysql] entire log window on the forums
And when I checked the log file mysql_error.log the following error was displayed:
2022-09-09 9:37:32 0 [ERROR] mysqld.exe: Aria recovery failed. Please run aria_chk -r on all Aria tables and delete all aria_log.######## files
2022-09-09 9:37:32 0 [ERROR] Plugin 'Aria' init function returned error.
2022-09-09 9:37:32 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2022-09-09 9:37:32 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2022-09-09 9:37:32 0 [Note] InnoDB: Uses event mutexes
2022-09-09 9:37:32 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-09-09 9:37:32 0 [Note] InnoDB: Number of pools: 1
2022-09-09 9:37:32 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-09-09 9:37:32 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2022-09-09 9:37:32 0 [Note] InnoDB: Completed initialization of buffer pool
2022-09-09 9:37:33 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-09-09 9:37:33 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-09-09 9:37:33 0 [Note] InnoDB: Setting file 'D:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-09-09 9:37:33 0 [Note] InnoDB: File 'D:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2022-09-09 9:37:33 0 [Note] InnoDB: Waiting for purge to start
2022-09-09 9:37:33 0 [Note] InnoDB: 10.4.24 started; log sequence number 35377535; transaction id 5422
2022-09-09 9:37:33 0 [Note] InnoDB: Loading buffer pool(s) from D:\xampp\mysql\data\ib_buffer_pool
2022-09-09 9:37:33 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-09-09 9:37:33 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2022-09-09 9:37:33 0 [ERROR] Failed to initialize plugins.
2022-09-09 9:37:33 0 [ERROR] Aborting
The main problem is with Plugin 'Aria' which is not starting as shown in the first line of the log above
mysqld.exe: Aria recovery failed. Please run aria_chk -r on all Aria tables and delete all aria_log.######## files
I had a similar issue and the method mentioned in this link fixed mine.
Delete all files named as aria_log.######## where ######## is any number from xampp\mysql\data folder.
I deleted the following file
aria_log.00000001
From xampp\mysql\data and the MySql server started successfully.

Error when attempting to run mariadb server on console background in raspberry pi

I keep getting an error when attempting to run a mariadb server on my raspberry pi and not really sure how to proceed.
I started a terminal window and these are the steps I have to follow for my class, however I can't even get past sudo mysqld -console :(
Installation of mariadb and simple exercise of CRUD:
sudo apt-get update
sudo apt-get install mariadb-server
sudo mysqld –console (to start the DB in the background)
(on a different terminal) sudo mysql (to log in as root)
create user ‘john’#’localhost’ identified by ‘password’;
select host, user from mysql.user;
Error Message:
e2022-05-25 12:49:20 0 [Note] mysqld (mysqld 10.5.15-MariaDB-0+deb11u1) starting
as process 19643 ...
2022-05-25 12:49:20 0 [Note] InnoDB: Uses event mutexes
2022-05-25 12:49:20 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-05-25 12:49:20 0 [Note] InnoDB: Number of pools: 1
2022-05-25 12:49:20 0 [Note] InnoDB: Using generic crc32 instructions
2022-05-25 12:49:20 0 [Note] InnoDB: Using Linux native AIO
2022-05-25 12:49:20 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2022-05-25 12:49:20 0 [Note] InnoDB: Completed initialization of buffer pool
2022-05-25 12:49:21 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=45178,45178
2022-05-25 12:49:21 0 [ERROR] InnoDB: Malformed log record; set innodb_force_recovery=1 to ignore.
2022-05-25 12:49:21 0 [Note] InnoDB: Dump from the start of the mini-transaction (LSN=45178) to 100 bytes after the record:
len 106; hex 73733130312e69626400120500b20108b20f05b50400000004b50400000015c30804ffc30204ffc30604ffc30204ffc30604ffc30204ffc30e04ffc30204ffc30604ffc30204ff34050075013405003540120501b20105460500802e10ff350500802d01b200fe350500; asc ss101.ibd 4 u 4 5# F . 5 - 5 ;
2022-05-25 12:49:21 0 [Warning] InnoDB: Log scan aborted at LSN 51712
2022-05-25 12:49:21 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2022-05-25 12:49:21 0 [Note] InnoDB: Starting shutdown...
2022-05-25 12:49:21 0 [ERROR] Plugin 'InnoDB' init function returned error.
2022-05-25 12:49:21 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-05-25 12:49:21 0 [Note] Plugin 'FEEDBACK' is disabled.
mysqld: Too many arguments (first extra is '–console').
2022-05-25 12:49:21 0 [ERROR] Aborting

XAMPP – MySQL shutdown unexpectedly

I've just installed XAMPP, and when I try to start my Apache and MySQL in the XAMPP Control Panel, I now get the following errors:
19:27:08 [mysql] Error: MySQL shutdown unexpectedly.
19:27:08 [mysql] This may be due to a blocked port, missing dependencies,
19:27:08 [mysql] improper privileges, a crash, or a shutdown by another method.
19:27:08 [mysql] Press the Logs button to view error logs and check
19:27:08 [mysql] the Windows Event Viewer for more clues
19:27:08 [mysql] If you need more help, copy and post this
19:27:08 [mysql] entire log window on the forums
InnoDB: using atomic writes.
2020-03-17 19:10:21 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2020-03-17 19:10:21 0 [Note] InnoDB: Uses event mutexes
2020-03-17 19:10:21 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-03-17 19:10:21 0 [Note] InnoDB: Number of pools: 1
2020-03-17 19:10:21 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-03-17 19:10:21 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2020-03-17 19:10:21 0 [Note] InnoDB: Completed initialization of buffer pool
2020-03-17 19:10:21 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=300288
2020-03-17 19:10:22 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2020-03-17 19:10:22 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2020-03-17 19:10:22 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-03-17 19:10:22 0 [Note] InnoDB: Setting file 'D:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-03-17 19:10:22 0 [Note] InnoDB: File 'D:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2020-03-17 19:10:22 0 [Note] InnoDB: Waiting for purge to start
2020-03-17 19:10:22 0 [Note] InnoDB: 10.4.11 started; log sequence number 300297; transaction id 171
2020-03-17 19:10:22 0 [Note] InnoDB: Loading buffer pool(s) from D:\xampp\mysql\data\ib_buffer_pool
2020-03-17 19:10:22 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-03-17 19:10:22 0 [Note] Server socket created on IP: '::'.
This is as a result of some files in C:\xampp\mysql\data\mysql getting corrupted.
first of all, try to end the task in task manager mysqlid.exe end and start again MySQL in Xampp, if there is the same error try this below solution. please backup that data.
Solution:
Back up C:\xampp\mysql\data
Copy all file C:\xampp\mysql\backup
Paste and replace existing file in: C:\xampp\mysql\data, except for
the ibdata1 file. Leaving ibdata1 will help against table does not
exist error.
this solution work for me its link here
I think you can check the ports were used by some application on your windows.
You can change the port:
Go to your xampp folder, find the mysql.cnf or mysql.ini to change the port 3306 to others
Then restart again.
If in your XAMPP control panel when you try to start the mysql it starts by getting PID and port number(3306) and then shutdowns unexpectedly.
The solution which worked for me is just go to your "C:\xampp\mysql\bin" directory (If you have installed on other location go to bin folder of mysql in that) and doubleclick the
mysqld.exe file.It will start working.
It also works using cmd (If you have installed XAMMP in other directory change the path accordingly.)
cd C:\xampp\mysql\bin
mysqld
Follow the steps this may resolve your issue
Close Xampp.
Go to \xampp\mysql\backup.
Copy all files in directory except ibdata1.
Go to \xampp\mysql\data.
Paste the files that you copied from \xampp\mysql\ backup (Replace the files when asked).
Start Xampp.

mysql server on xampp do not works

I know that some questions like mine is in this site and i try all of Those questions to solve my problem But I failed, so i ask new question.
When I open XAMPP and click start MySQL button and it gives me some errors. I had started it just before, but now it isn't working.
4:29:11 PM [mysql] Error: MySQL shutdown unexpectedly.
4:29:11 PM [mysql] This may be due to a blocked port, missing dependencies,
4:29:11 PM [mysql] improper privileges, a crash, or a shutdown by another method.
4:29:11 PM [mysql] Press the Logs button to view error logs and check
4:29:11 PM [mysql] the Windows Event Viewer for more clues
4:29:11 PM [mysql] If you need more help, copy and post this
4:29:11 PM [mysql] entire log window on the forums
Here is the contents of the error log:
2019-12-17 16:25:22 0 [ERROR] mysqld.exe: Aria engine: log data error last_log_page: (1,0x2000) is
less than checkpoint page: (1,0x4000)
2019-12-17 16:25:22 0 [ERROR] mysqld.exe: Aria engine: log initialization failed
2019-12-17 16:25:22 0 [ERROR] Plugin 'Aria' init function returned error.
2019-12-17 16:25:22 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. InnoDB: using atomic writes.
2019-12-17 16:25:22 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-12-17 16:25:22 0 [Note] InnoDB: Uses event
2019-12-17 16:25:22 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-12-17 16:25:22 0 [Note] InnoDB: Number of pools: 1
2019-12-17 16:25:22 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-12-17 16:25:22 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2019-12-17 16:25:22 0 [Note] InnoDB: Completed initialization of buffer pool
2019-12-17 16:25:23 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-12-17 16:25:23 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-12-17 16:25:23 0 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibtmp1' size to 12 MB.Physically writing the file full; Please wait ...
2019-12-17 16:25:23 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2019-12-17 16:25:23 0 [Note] InnoDB: Waiting for purge to start
2019-12-17 16:25:23 0 [Note] InnoDB: 10.4.8 started; log sequence number 113962; transaction id 9
2019-12-17 16:25:23 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2019-12-17 16:25:23 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-12-17 16:25:23 0 [Note] InnoDB: Buffer pool(s) load completed at 191217 16:25:23
2019-12-17 16:25:23 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2019-12-17 16:25:23 0 [ERROR] Failed to initialize plugins.
2019-12-17 16:25:23 0 [ERROR] Aborting
I have tried these solutions before but my problem was not solved
delete the ibdata1 file.
Delete all random files (except the actual database folders) in mysql/data/
Add innodb_force_recovery = 4 below the [mysqld] in the mysql config file (my.ini)
delete the ibdata1 & ib_logfile*(ib_logfile0,ib_logfile1,ib_logfile101) file
Change the location of all files (like test_db) in C:\xampp\mysql\data location for test
change the mysql server port to "3307,3308,9999,6542"
in this places-->
[mysqld]
port=3306
and
[client]
port=3306
socket="C:/xampp/mysql/mysql.sock"
thanks for your help.
The solution is Removing the "aria_log.00000001" file. You can find this file in \xampp\mysql\data. Then restart or start xampp. Also Please run aria_chk -r on all Aria tables and delete all aria_log.######## files’
Possibilties:
incorrect config - try to restore some known good config
blocked port - quite often its skype(especially older versions of skype), try changing MySQL port
If you're not running XAMPP as an administrator, shutting down MySQL
can cause corruption which means you have to repair or delete your
tables. This can easily be avoided by running XAMPP as administrator.

Resources