Jump to content
metin2dev
  • 0
Sign in to follow this  
mTw

mysql is not running error.

Question

Hey, Metin2Dev community.

I've recently started to work on a metin2 server project and Im facing issues on my mysql server.

when i use  service mysql-server restart 

and then check the status it says mysql is not runnning.

here is the .err file details:- 

 

190104 06:40:47 mysqld_safe Logging to '/var/db/mysql/librion.metin2.err'.
190104 06:40:48 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2019-01-04 06:40:49 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-01-04 06:40:49 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.42) starting as process 13071 ...
2019-01-04 06:40:49 13071 [Note] Plugin 'FEDERATED' is disabled.
2019-01-04 06:40:49 13071 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-01-04 06:40:49 13071 [Note] InnoDB: The InnoDB memory heap is disabled
2019-01-04 06:40:49 13071 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-01-04 06:40:49 13071 [Note] InnoDB: Memory barrier is not used
2019-01-04 06:40:49 13071 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-01-04 06:40:49 13071 [Note] InnoDB: Not using CPU crc32 instructions
2019-01-04 06:40:49 13071 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-01-04 06:40:49 13071 [Note] InnoDB: Completed initialization of buffer pool
2019-01-04 06:40:49 13071 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2019-01-04 06:40:49 13071 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2019-01-04 06:40:49 13071 [Note] InnoDB: Database physically writes the file full: wait...
2019-01-04 06:40:49 13071 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2019-01-04 06:40:49 13071 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2019-01-04 06:40:49 13071 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2019-01-04 06:40:49 13071 [Warning] InnoDB: New log files created, LSN=45781
2019-01-04 06:40:49 13071 [Note] InnoDB: Doublewrite buffer not found: creating new
2019-01-04 06:40:49 13071 [Note] InnoDB: Doublewrite buffer created
2019-01-04 06:40:49 13071 [Note] InnoDB: 128 rollback segment(s) are active.
2019-01-04 06:40:49 13071 [Warning] InnoDB: Creating foreign key constraint system tables.
2019-01-04 06:40:49 13071 [Note] InnoDB: Foreign key constraint system tables created
2019-01-04 06:40:49 13071 [Note] InnoDB: Creating tablespace and datafile system tables.
2019-01-04 06:40:49 13071 [Note] InnoDB: Tablespace and datafile system tables created.
2019-01-04 06:40:49 13071 [Note] InnoDB: Waiting for purge to start
2019-01-04 06:40:49 13071 [Note] InnoDB: 5.6.42 started; log sequence number 0
Warning: World-writable config file './auto.cnf' is ignored
2019-01-04 06:40:49 13071 [Warning] World-writable config file './auto.cnf' has been removed.

2019-01-04 06:40:49 13071 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 4ab1eb51-0fe3-11e9-8a76-000434b359f3.
2019-01-04 06:40:49 13071 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2019-01-04 06:40:49 13071 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2019-01-04 06:40:49 13071 [Note] Server hostname (bind-address): '*'; port: 3306
2019-01-04 06:40:49 13071 [Note] IPv6 is available.
2019-01-04 06:40:49 13071 [Note]   - '::' resolves to '::';
2019-01-04 06:40:49 13071 [Note] Server socket created on IP: '::'.
2019-01-04 06:40:49 13071 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
2019-01-04 06:40:49 13071 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2019-01-04 06:40:49 13071 [ERROR] Aborting

2019-01-04 06:40:49 13071 [Note] Binlog end
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'partition'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_METRICS'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_CMPMEM'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_CMP'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_LOCKS'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'INNODB_TRX'
2019-01-04 06:40:49 13071 [Note] Shutting down plugin 'InnoDB'
2019-01-04 06:40:49 13071 [Note] InnoDB: FTS optimize thread exiting.
2019-01-04 06:40:49 13071 [Note] InnoDB: Starting shutdown...
2019-01-04 06:40:50 13071 [Note] InnoDB: Shutdown completed; log sequence number 1600607
2019-01-04 06:40:50 13071 [Note] Shutting down plugin 'BLACKHOLE'
2019-01-04 06:40:50 13071 [Note] Shutting down plugin 'ARCHIVE'
2019-01-04 06:40:50 13071 [Note] Shutting down plugin 'MRG_MYISAM'
2019-01-04 06:40:50 13071 [Note] Shutting down plugin 'MyISAM'
2019-01-04 06:40:50 13071 [Note] Shutting down plugin 'MEMORY'
2019-01-04 06:40:50 13071 [Note] Shutting down plugin 'CSV'
2019-01-04 06:40:50 13071 [Note] Shutting down plugin 'sha256_password'
2019-01-04 06:40:50 13071 [Note] Shutting down plugin 'mysql_old_password'
2019-01-04 06:40:50 13071 [Note] Shutting down plugin 'mysql_native_password'
2019-01-04 06:40:50 13071 [Note] Shutting down plugin 'binlog'
2019-01-04 06:40:50 13071 [Note] /usr/local/libexec/mysqld: Shutdown complete

190104 06:40:50 mysqld_safe mysqld from pid file /var/db/mysql/librion.metin2.pid ended

to see what's already listening on the port 3306 I used the command  sudo lsof -i TCP:3306 and got 

COMMAND   PID  USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
mysqld  12565 mysql   10u  IPv6 0xfffff8005115f000      0t0  TCP *:mysql (LISTEN)
 

then I killed this process id using 

kill 12565 

and then again tried to start the mysql by using 

service mysql-server start 

and this time it gave :- 

mysql is running as pid 13318.

but now when I tried to start my game by using 

/usr/game 

sh start.sh 

and then again tried to check the status of my mysql it wasn't running, it gave

mysql is not running.

I've tried everything to fix thing thing but couldn't 

any help would be greatly appreciated.

 


 

 

 

Share this post


Link to post
Share on other sites

4 answers to this question

Recommended Posts

  • 0
Can't start server: Bind on TCP/IP port: Address already in use
2019-01-04 06:40:49 13071 [ERROR] Do you already have another mysqld server running on port: 3306 ?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×