Welcome Guest. Please Login or Register  


You are here: Index > AMPPS > General Support > Topic : MySQL not starting up


Poll
Poll Question : g
solucion mysql para ampps (0) (0%)
w (0) (0%)
w (0) (0%)
w (0) (0%)
w (0) (0%)
w (0) (0%)
w (0) (0%)
w (0) (0%)
w (0) (0%)
w (0) (0%)

Total Votes : 0


2


Threaded Mode | Print  

MySQL not starting up
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Hi,

Close MySQL Server before shutting down your machine.


-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

MySQL not starting up
bluesky_c3
Group: Member
Post Group: Newbie
Posts: 10
Status:
Allright, guys! I got it! :)

Thanks!
IP: --   

MySQL not starting up
sdowns
Group: Member
Post Group: Newbie
Posts: 6
Status:
I'm getting the same error after upgrading to 2.4 on Mavericks 10.9.2.

2014-05-13 13:36:11 8225 [Note] Plugin 'FEDERATED' is disabled.
2014-05-13 13:36:11 8225 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-05-13 13:36:11 8225 [Note] InnoDB: The InnoDB memory heap is disabled
2014-05-13 13:36:11 8225 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-05-13 13:36:11 8225 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-05-13 13:36:11 8225 [Note] InnoDB: Not using CPU crc32 instructions
2014-05-13 13:36:11 8225 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-05-13 13:36:11 8225 [Note] InnoDB: Completed initialization of buffer pool
2014-05-13 13:36:11 8225 [Note] InnoDB: Highest supported file format is Barracuda.
2014-05-13 13:36:11 8225 [Note] InnoDB: 128 rollback segment(s) are active.
2014-05-13 13:36:11 8225 [Note] InnoDB: Waiting for purge to start
2014-05-13 13:36:11 8225 [Note] InnoDB: 5.6.17 started; log sequence number 1600627
2014-05-13 13:36:12 8225 [Note] Server hostname (bind-address): '*'; port: 3306
2014-05-13 13:36:12 8225 [Note] IPv6 is available.
2014-05-13 13:36:12 8225 [Note]  - '::' resolves to '::';
2014-05-13 13:36:12 8225 [Note] Server socket created on IP: '::'.
2014-05-13 13:36:12 8225 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-05-13 13:36:12 8225 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2014-05-13 13:36:12 8225 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2014-05-13 13:36:12 8225 [Note] Event Scheduler: Loaded 0 events
2014-05-13 13:36:12 8225 [Note] /Applications/AMPPS/mysql/bin/mysqld: ready for connections.
Version: '5.6.17-log'  socket: '/Applications/AMPPS/mysql/tmp/mysql.sock'  port: 3306  Source distribution

I have tried the following from this post and the other post mentioned:

1. adding innodb_force_recovery = 1 to config file
2. backup and move log files and mysql-bin files from /ampss/var
3. backup and move innodb files from /ampps/var/mysql
IP: --   

MySQL not starting up
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Quote From : sdowns May 13, 2014, 12:41 pm
I'm getting the same error after upgrading to 2.4 on Mavericks 10.9.2.

2014-05-13 13:36:11 8225 [Note] Plugin 'FEDERATED' is disabled.
2014-05-13 13:36:11 8225 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-05-13 13:36:11 8225 [Note] InnoDB: The InnoDB memory heap is disabled
2014-05-13 13:36:11 8225 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-05-13 13:36:11 8225 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-05-13 13:36:11 8225 [Note] InnoDB: Not using CPU crc32 instructions
2014-05-13 13:36:11 8225 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-05-13 13:36:11 8225 [Note] InnoDB: Completed initialization of buffer pool
2014-05-13 13:36:11 8225 [Note] InnoDB: Highest supported file format is Barracuda.
2014-05-13 13:36:11 8225 [Note] InnoDB: 128 rollback segment(s) are active.
2014-05-13 13:36:11 8225 [Note] InnoDB: Waiting for purge to start
2014-05-13 13:36:11 8225 [Note] InnoDB: 5.6.17 started; log sequence number 1600627
2014-05-13 13:36:12 8225 [Note] Server hostname (bind-address): '*'; port: 3306
2014-05-13 13:36:12 8225 [Note] IPv6 is available.
2014-05-13 13:36:12 8225 [Note]  - '::' resolves to '::';
2014-05-13 13:36:12 8225 [Note] Server socket created on IP: '::'.
2014-05-13 13:36:12 8225 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-05-13 13:36:12 8225 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2014-05-13 13:36:12 8225 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2014-05-13 13:36:12 8225 [Note] Event Scheduler: Loaded 0 events
2014-05-13 13:36:12 8225 [Note] /Applications/AMPPS/mysql/bin/mysqld: ready for connections.
Version: '5.6.17-log'  socket: '/Applications/AMPPS/mysql/tmp/mysql.sock'  port: 3306  Source distribution

I have tried the following from this post and the other post mentioned:

1. adding innodb_force_recovery = 1 to config file
2. backup and move log files and mysql-bin files from /ampss/var
3. backup and move innodb files from /ampps/var/mysql


Hi,

Is you MySQL server not working ? Because I cannot find the error in the logs. Please open a ticket, we will look into it.


-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

MySQL not starting up
sdowns
Group: Member
Post Group: Newbie
Posts: 6
Status:
I can see now that despite the error messages about slave tables, mysql has actually started.

However when I try to access any of my Drupal database tables, mysql says they do not exist.

Prior to the 2.4 upgrade, Drupal was running fine so I'm going to go back to a backup and make sure it is working prior to the upgrade.
IP: --   

MySQL not starting up
sdowns
Group: Member
Post Group: Newbie
Posts: 6
Status:
Right, I've restored my AMPPS installation back to 2.3, prior to the 2.4 upgrade. I can now run my local website again.

However when I look at the mysql error log I'm still seeing these errors.

2014-05-14 08:23:30 3098 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-05-14 08:23:30 3098 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2014-05-14 08:23:30 3098 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-05-14 08:23:30 3098 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-05-14 08:23:30 3098 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.

In fact these errors have been occurring since I first installed AMPPS 2.2 back in January.

Checking the database named 'mysql', the following tables appear in the list of tables but if I try to view them, my SQL client (Sequel Pro) says they do not exist.

innodb_index_stats, innodb_table_stats, slave_master_info, slave_relay_log_info and slave_worker_info.

How do I recreate these tables and does it matter?
IP: --   

MySQL not starting up
z0quete
Group: Member
Post Group: Newbie
Posts: 2
Status:
hi everybody!

i have the same problem, mysql doesent start.
the first time i used it it worked well, but on the next day it just didnt start anymore.

i've tried reinstalling it and also deleting the files in path/to/Ampps/mysql/data
but none of those solutions did work.

this is what the error log file sais:

http://pastebin.com/pypure0G

(sorry for my crappy english, it's not my first language)
IP: --   

MySQL not starting up
z0quete
Group: Member
Post Group: Newbie
Posts: 2
Status:
Quote From : z0quete August 17, 2014, 2:17 pm
hi everybody!

i have the same problem, mysql doesent start.
the first time i used it it worked well, but on the next day it just didnt start anymore.

i've tried reinstalling it and also deleting the files in path/to/Ampps/mysql/data
but none of those solutions did work.

this is what the error log file sais:

http://pastebin.com/pypure0G

(sorry for my crappy english, it's not my first language)


ok guys i found the solution to my problem.
the problem was that i had also WAMP on my computer and somehow i didnt let AMPPS work properly. i never unistalled WAMP because every time i tried i got a an "error 5: acces denied" message.
if someone has the se same problem, the solution that i found was deleteng WAMP from an other partion.
IP: --   

MySQL not starting up
imike
Group: Member
Post Group: Newbie
Posts: 2
Status:
Hey guys.  So I had the issue of MySQL not starting up today.  So I followed the instructions here and deleted the files that weren't folders from the AMPPS/var folder on OSX. 

After this I started MySQL and it worked.  But then I noticed that 1 of my databases tables were not there any longer.  So, I just restored the deleted files immediately.  Now I am back to MySQL not starting. 

My log shows "Innodb: Cannot open table swmandrill/participants from the internal data dictionary of InnoDB though the .frm file for the table exists."  It shows this for error for every table inside that database.

My logfile:
http://pastebin.com/yYFCBbSM

How can I get these tables back and get MySQL running.  Thanks for your time.
IP: --   

MySQL not starting up
imike
Group: Member
Post Group: Newbie
Posts: 2
Status:
I should add that MySQL is now running but my tables are missing.  I have the .frm and .ibd files.  I have no idea what to do with them. 
IP: --   

MySQL not starting up
azarzag
Group: Member
Post Group: Newbie
Posts: 1
Status:
I seem to have a similar problem. Here's my mysql error log

2014-09-01 08:50:14 31003 [Warning] You need to use --log-bin to make --binlog-format work.
2014-09-01 08:50:14 31003 [Note] Plugin 'FEDERATED' is disabled.
2014-09-01 08:50:14 31003 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-09-01 08:50:14 31003 [Note] InnoDB: The InnoDB memory heap is disabled
2014-09-01 08:50:14 31003 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-09-01 08:50:14 31003 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-09-01 08:50:14 31003 [Note] InnoDB: Not using CPU crc32 instructions
2014-09-01 08:50:14 31003 [Note] InnoDB: Initializing buffer pool, size = 160.0M
2014-09-01 08:50:14 31003 [Note] InnoDB: Completed initialization of buffer pool
2014-09-01 08:50:14 31003 [Note] InnoDB: Highest supported file format is Barracuda.
2014-09-01 08:50:14 31003 [Note] InnoDB: 128 rollback segment(s) are active.
2014-09-01 08:50:14 31003 [Note] InnoDB: Waiting for purge to start
2014-09-01 08:50:14 31003 [Note] InnoDB: 5.6.17 started; log sequence number 1600657
2014-09-01 08:50:14 31003 [ERROR] /Applications/AMPPS/mysql/bin/mysqld: unknown variable 'table_cache=16'
2014-09-01 08:50:14 31003 [ERROR] Aborting

2014-09-01 08:50:14 31003 [Note] Binlog end
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'partition'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_METRICS'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_CMPMEM'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_CMP'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_LOCKS'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'INNODB_TRX'
2014-09-01 08:50:14 31003 [Note] Shutting down plugin 'InnoDB'
2014-09-01 08:50:14 31003 [Note] InnoDB: FTS optimize thread exiting.
2014-09-01 08:50:14 31003 [Note] InnoDB: Starting shutdown...
2014-09-01 08:50:16 31003 [Note] InnoDB: Shutdown completed; log sequence number 1600667
2014-09-01 08:50:16 31003 [Note] Shutting down plugin 'BLACKHOLE'
2014-09-01 08:50:16 31003 [Note] Shutting down plugin 'ARCHIVE'
2014-09-01 08:50:16 31003 [Note] Shutting down plugin 'MRG_MYISAM'
2014-09-01 08:50:16 31003 [Note] Shutting down plugin 'MyISAM'
2014-09-01 08:50:16 31003 [Note] Shutting down plugin 'MEMORY'
2014-09-01 08:50:16 31003 [Note] Shutting down plugin 'CSV'
2014-09-01 08:50:16 31003 [Note] Shutting down plugin 'sha256_password'
2014-09-01 08:50:16 31003 [Note] Shutting down plugin 'mysql_old_password'
2014-09-01 08:50:16 31003 [Note] Shutting down plugin 'mysql_native_password'
2014-09-01 08:50:16 31003 [Note] Shutting down plugin 'binlog'
2014-09-01 08:50:16 31003 [Note] /Applications/AMPPS/mysql/bin/mysqld: Shutdown complete
IP: --   

SOLUCION PARA PROBLEMA DE INICIAR MYSQL EN AMPPS
codebrono
Group: Member
Post Group: Newbie
Posts: 1
Status:
HOLA AMIGOS TUVE EL MISMO PROBLEMA CON EL MYSQL DE AMPPS Y LA SOLUCIÓN FUE MUY SIMPLE  ....  :)

EN : \Ampps\mysql\data

HAY UNOS ARCHIVOS LLAMADOS
AUTO.CNF
IB_LOGFILE
IBLOGFILE1
IBDATA
Y HAY OTROS ARCHIVOS QUE TERMINAN EN  :  .ERR Y .PID

LES CUENTO ESOS ARCHIVOS SON LOS QUE CREA AUTOMÁTICAMENTE AMPPS PARA ARRANCAR EL SISTEMA MYSQL  Y AL MOMENTO DE TENER UN FALLO ESOS ARCHIVOS SE MODIFICAN AUTOMÁTICAMENTE  ... LA SOLUCIÓN ES ELIMINAR ESOS ARCHIVOS REINICIAR AMPPS Y ABRIR NUEVAMENTE AMPPS Y INICIAR EL MYSQL

AMI ASÍ ME FUNCIONO .. YA QUE YO APAGUE EL COMPUTADOR SIN HABER CERRADO PRIMERO AMPPS

RECUERDEN DETENER TODOS LOS ACTIVOS DE AMPPS : MYSQL Y APACHE ANTES DE APAGAR LA COMPUTADORA

OJALAS LES AYA SERVIDO SALUDOS WEBMASTERS  ;-D

CODEBRONO.COM    ;-D  :angel: 
IP: --   

MySQL not starting up
knkr
Group: Member
Post Group: Newbie
Posts: 2
Status:
MYSQL DB is shuting down continuosaly with the below error

150624 08:30:06 mysqld_safe mysqld from pid file /mi/files/mysql/mbluaac1.statestreet.com.pid ended
150624 08:33:09 mysqld_safe Starting mysqld daemon with databases from /mi/files/mysql
150624  8:33:10 [Note] Plugin 'FEDERATED' is disabled.
150624  8:33:10 InnoDB: The InnoDB memory heap is disabled
150624  8:33:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150624  8:33:10 InnoDB: Compressed tables use zlib 1.2.3
150624  8:33:10 InnoDB: Initializing buffer pool, size = 2.0G
150624  8:33:10 InnoDB: Completed initialization of buffer pool
150624  8:33:10 InnoDB: highest supported file format is Barracuda.
150624  8:33:10  InnoDB: Waiting for the background threads to start
150624  8:33:11 InnoDB: 1.1.8 started; log sequence number 1378545354
150624  8:33:11 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
150624  8:33:11 [Note]  - '127.0.0.1' resolves to '127.0.0.1';
150624  8:33:11 [Note] Server socket created on IP: '127.0.0.1'.
150624  8:33:11 [Note] Event Scheduler: Loaded 0 events
150624  8:33:11 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.29'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)
150624  8:43:54 [Note] /usr/sbin/mysqld: Normal shutdown

150624  8:43:54 [Note] Event Scheduler: Purging the queue. 0 events
150624  8:43:54  InnoDB: Starting shutdown...
150624  8:43:55  InnoDB: Shutdown completed; log sequence number 1380198543
150624  8:43:55 [Note] /usr/sbin/mysqld: Shutdown complete
IP: --   

MySQL not starting up
knkr
Group: Member
Post Group: Newbie
Posts: 2
Status:
MYSQL DB is shuting down continuosaly with the below error

150624 08:30:06 mysqld_safe mysqld from pid file /mi/files/mysql/mbluaac1.statestreet.com.pid ended
150624 08:33:09 mysqld_safe Starting mysqld daemon with databases from /mi/files/mysql
150624  8:33:10 [Note] Plugin 'FEDERATED' is disabled.
150624  8:33:10 InnoDB: The InnoDB memory heap is disabled
150624  8:33:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150624  8:33:10 InnoDB: Compressed tables use zlib 1.2.3
150624  8:33:10 InnoDB: Initializing buffer pool, size = 2.0G
150624  8:33:10 InnoDB: Completed initialization of buffer pool
150624  8:33:10 InnoDB: highest supported file format is Barracuda.
150624  8:33:10  InnoDB: Waiting for the background threads to start
150624  8:33:11 InnoDB: 1.1.8 started; log sequence number 1378545354
150624  8:33:11 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
150624  8:33:11 [Note]  - '127.0.0.1' resolves to '127.0.0.1';
150624  8:33:11 [Note] Server socket created on IP: '127.0.0.1'.
150624  8:33:11 [Note] Event Scheduler: Loaded 0 events
150624  8:33:11 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.29'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)
150624  8:43:54 [Note] /usr/sbin/mysqld: Normal shutdown

150624  8:43:54 [Note] Event Scheduler: Purging the queue. 0 events
150624  8:43:54  InnoDB: Starting shutdown...
150624  8:43:55  InnoDB: Shutdown completed; log sequence number 1380198543
150624  8:43:55 [Note] /usr/sbin/mysqld: Shutdown complete
IP: --   

MySQL not starting up
faraweilyas
Group: Member
Post Group: Newbie
Posts: 1
Status:
Hello,

I'm using AMPPS 3.8 on BigSur 11.4

AMPPS stopped working but I was able to start AMPPS apache and MySQL to get by, until recently after I restarted my mac MySQL is no longer starting but I can access localhost which means Apache is working.

Here is the error MySQL Server is giving:

2021-08-19T09:56:16.670667Z 0 [System] [MY-010116] [Server] /Applications/AMPPS/mysql/bin/mysqld (mysqld 8.0.18) starting as process 9395
2021-08-19T09:56:16.673548Z 0 [Warning] [MY-010339] [Server] Using pre 5.5 semantics to load error messages from /Applications/AMPPS/mysql/share/mysql/english/. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.
2021-08-19T09:56:17.824565Z 1 [Warning] [MY-010005] [Server] Skip re-populating collations and character sets tables in InnoDB read-only mode.
2021-08-19T09:56:17.828877Z 2 [Warning] [MY-011018] [Server] Skip updating information_schema metadata in InnoDB read-only mode.
2021-08-19T09:56:17.881045Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2021-08-19T09:56:17.940132Z 0 [System] [MY-010931] [Server] /Applications/AMPPS/mysql/bin/mysqld: ready for connections. Version: '8.0.18'  socket: '/Applications/AMPPS/var/mysql.sock'  port: 0  Source distribution.
2021-08-19T09:56:18.083227Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/Applications/AMPPS/var/mysqlx.sock'
2021-08-19T09:57:51.207105Z 0 [System] [MY-010910] [Server] /Applications/AMPPS/mysql/bin/mysqld: Shutdown complete (mysqld 8.0.18)  Source distribution.
IP: --   

« Previous    Next »

Threaded Mode | Print  

2


Jump To :


Users viewing this topic
7 guests, 0 users.


All times are GMT. The time now is October 25, 2021, 11:05 am.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 12  |  Page Created In:3.043