Control Web Panel
WebPanel => CentOS-WebPanel GUI => Topic started by: huyduong.1231991 on August 29, 2017, 02:54:34 AM
-
I need help
Continuously crash Error Establishing A Database Connection with all websites on VPS
-
you should check mysql logs, location:
/var/lib/mysql/
-
you should check mysql logs, location:
/var/lib/mysql/
Can you give me more detailed instructions
-
you need to find log file in that folder, usually its called the same as your hostname with .err extension
-
Also, how many CPU's and RAM available on your VPS?
-
Also, how many CPU's and RAM available on your VPS?
When I restarted mysql in the dashboard, I fixed the error
-
you need to find log file in that folder, usually its called the same as your hostname with .err extension
https://drive.google.com/open?id=0B6Hy6OCfYwedR0J5dW9vRGpqTlE (https://drive.google.com/open?id=0B6Hy6OCfYwedR0J5dW9vRGpqTlE) I find this file
-
by checking your mysql logs looks like you have low memory issues and you should consider about memory upgrade
-
you need to find log file in that folder, usually its called the same as your hostname with .err extension
I have the same problem. This is my log now, what is the problem?
I have 8GB Ram.
190110 21:33:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2019-01-10 21:33:52 140203948259584 [Note] /usr/sbin/mysqld (mysqld 10.1.29-MariaDB) starting as process 31634 ...
2019-01-10 21:33:53 140203948259584 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-01-10 21:33:53 140203948259584 [Note] InnoDB: The InnoDB memory heap is disabled
2019-01-10 21:33:53 140203948259584 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-01-10 21:33:53 140203948259584 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-01-10 21:33:53 140203948259584 [Note] InnoDB: Compressed tables use zlib 1.2.7
2019-01-10 21:33:53 140203948259584 [Note] InnoDB: Using Linux native AIO
2019-01-10 21:33:53 140203948259584 [Note] InnoDB: Using SSE crc32 instructions
2019-01-10 21:33:53 140203948259584 [Note] InnoDB: Initializing buffer pool, size = 5.0G
2019-01-10 21:33:53 140203948259584 [Note] InnoDB: Completed initialization of buffer pool
2019-01-10 21:33:53 140203948259584 [Note] InnoDB: Highest supported file format is Barracuda.
2019-01-10 21:33:53 140203948259584 [Note] InnoDB: 128 rollback segment(s) are active.
2019-01-10 21:33:53 140203948259584 [Note] InnoDB: Waiting for purge to start
2019-01-10 21:33:53 140203948259584 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 42812232888
2019-01-10 21:33:53 140203948259584 [Note] Plugin 'FEEDBACK' is disabled.
2019-01-10 21:33:53 140197475874560 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-01-10 21:33:53 140203948259584 [Note] Server socket created on IP: '::'.
2019-01-10 21:33:53 140203948259584 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.1.29-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
2019-01-10 21:33:57 140203869195008 [Note] /usr/sbin/mysqld: Normal shutdown
2019-01-10 21:33:57 140197501052672 [Note] InnoDB: FTS optimize thread exiting.
2019-01-10 21:33:57 140203869195008 [Note] InnoDB: Starting shutdown...
2019-01-10 21:33:58 140203869195008 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
2019-01-10 21:34:00 140203869195008 [Note] InnoDB: Shutdown completed; log sequence number 42812926013
2019-01-10 21:34:00 140203869195008 [Note] /usr/sbin/mysqld: Shutdown complete
190110 21:34:00 mysqld_safe mysqld from pid file /var/lib/mysql/server.*******.es.pid ended