Page 2 of 2

Re: Mysql stop after reboot vps

Posted: Sat Nov 29, 2014 2:16 pm
by joem
vestacp89 wrote:anyone explain ? how to see mysql log file ?

Thanks.
Check all of these

Code: Select all

nano /var/log/vesta/system.log
nano /var/log/mysql.log
nano /var/log/mysql/error.log 
if you get this as an output and only this then the file is blank
^G Get Help ^O WriteOut ^R Read File ^Y Prev Page ^K Cut Text ^C Cur Pos
^X Exit ^J Justify ^W Where Is ^V Next Page ^U UnCut Text ^T To Spell
nano basics
Ctrl + X: Exit
Copy Text: Highlight everything -> right click your mouse -> Ctrl + X -> N - > Enter -> The highlighted text is now saved your you clipboard.

Re: Mysql stop after reboot vps

Posted: Tue Dec 02, 2014 3:14 pm
by vestacp89
joem wrote:
vestacp89 wrote:anyone explain ? how to see mysql log file ?

Thanks.
Check all of these

Code: Select all

nano /var/log/vesta/system.log
nano /var/log/mysql.log
nano /var/log/mysql/error.log 
if you get this as an output and only this then the file is blank
^G Get Help ^O WriteOut ^R Read File ^Y Prev Page ^K Cut Text ^C Cur Pos
^X Exit ^J Justify ^W Where Is ^V Next Page ^U UnCut Text ^T To Spell
nano basics
Ctrl + X: Exit
Copy Text: Highlight everything -> right click your mouse -> Ctrl + X -> N - > Enter -> The highlighted text is now saved your you clipboard.
yes file is blank and there not error.

Thanks.

Re: Mysql stop after reboot vps

Posted: Tue May 12, 2015 2:04 am
by laviepc
I meet same error .
How to fix or auto reboot server when meet this error

This is my log :

InnoDB: in total 3 row operations to undo
InnoDB: Trx id counter is 9B6A000
150511 12:14:25 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Starting in background the rollback of uncommitted transactions
150511 12:14:25 InnoDB: Rolling back trx with id 9B69D7D, 1 rows to undo
150511 12:14:25 InnoDB: Waiting for the background threads to start

InnoDB: Rolling back of trx id 9B69D7D completed
150511 12:14:25 InnoDB: Rolling back trx with id 9B69D37, 1 rows to undo

InnoDB: Rolling back of trx id 9B69D37 completed
150511 12:14:25 InnoDB: Rolling back trx with id 9B69D0E, 1 rows to undo

InnoDB: Rolling back of trx id 9B69D0E completed
150511 12:14:25 InnoDB: Rollback of non-prepared transactions completed
150511 12:14:26 InnoDB: 5.5.41 started; log sequence number 3682617281
150511 12:14:26 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
150511 12:14:26 [Note] - '0.0.0.0' resolves to '0.0.0.0';
150511 12:14:26 [Note] Server socket created on IP: '0.0.0.0'.
150511 12:14:26 [Note] Event Scheduler: Loaded 0 events
150511 12:14:26 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.41' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Remi

Re: Mysql stop after reboot vps

Posted: Sun May 17, 2015 5:06 am
by bestony
Why Not Use Cat ?

Code: Select all

cat  /var/log/mysql.log