mysql pid not found


Status
Not open for further replies.

mas.satriyo

Hosting Guru
barusan iseng2 ngecek log mysql (/var/lib/mysq/hostname.err) dan baru ngeh log file berhenti mencatat beberapa hari yg lalu

coba cek status (service mysql status / systemctl status mysql) muncul error
ERROR! MySQL is not running, but PID file exists

coba run manual pakai mysqld_safe bisa jalan normal, tapi kalau pakai (service mysql start / systemctl start mysql), log file tidak mencatat dan kalo di cek status pasti muncul error di atas

saya pakai cloudlinux 7, mariadb-10.1, dan db_governor

trims
 

GPLHosting

Hosting Guru
Code:
# rm /var/lib/mysql/mysql.sock

# service mysqld restart

file mysql.sock mungkin berbeda path dari yang di atas, silakan cari dahulu, kemudian hapus.
 

idnix

Hosting Guru
Verified Provider
menunggu log dulu deh.
 

mas.satriyo

Hosting Guru
cd /var/lib/mysql

cp hostname.err{,.bak}
echo "" > hostname.err
/scripts/restartsrv_mysql
tail -n 20 hostname.err atau cat hostname.err
output paste disini

buat log baru isinya kosong

Code:
# rm /var/lib/mysql/mysql.sock
# service mysqld restart
file mysql.sock mungkin berbeda path dari yang di atas, silakan cari dahulu, kemudian hapus.

masih sama bu

menunggu log dulu deh.

Code:
2017-03-22  7:39:23 140295174404288 [Note] All governors lve functions found too
2017-03-22  7:39:23 140295174404288 [Note] /usr/sbin/mysqld (mysqld 10.1.21-MariaDB-cll-lve) starting as process 652399 ...
2017-03-22  7:39:23 140295174404288 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-03-22  7:39:23 140295174404288 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-22  7:39:23 140295174404288 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-22  7:39:23 140295174404288 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-03-22  7:39:23 140295174404288 [Note] InnoDB: Compressed tables use zlib 1.2.7
2017-03-22  7:39:23 140295174404288 [Note] InnoDB: Using Linux native AIO
2017-03-22  7:39:23 140295174404288 [Note] InnoDB: Using generic crc32 instructions
2017-03-22  7:39:23 140295174404288 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-03-22  7:39:23 140295174404288 [Note] InnoDB: Completed initialization of buffer pool
2017-03-22  7:39:23 140295174404288 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-22  7:39:23 140295174404288 [Note] InnoDB: 128 rollback segment(s) are active.
2017-03-22  7:39:23 140295174404288 [Note] InnoDB: Waiting for purge to start
2017-03-22  7:39:23 140295174404288 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 24287890
2017-03-22  7:39:23 140294276237056 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-03-22  7:39:23 140295174404288 [Note] Plugin 'FEEDBACK' is disabled.
2017-03-22  7:39:23 140295174404288 [Note] Server socket created on IP: '::'.
2017-03-22  7:39:23 140295174404288 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.1.21-MariaDB-cll-lve'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server

log-nya berhenti di jam 7:39 mas, waktu saya run pakai 'mysqld_safe'
di log tidak ada error mas, hanya saja log berhenti mencatat
log baru mencatat kalo mysql di run dengan 'mysqld_safe'
kalo pake 'service mysql start' log tidak mencatat apa2
 

junior riau

Hosting Guru
Verified Provider
Code:
# mv /etc/my.cnf{,.bak}
# cp /var/lib/ibdata1{,.bak}
# cp /var/lib/ib_logfile0{,.bak}
# cp /var/lib/ib_logfile1{,.bak}

cara 1
# /scripts/restartsrv_mysqld

jika belum sehat
cara 2
# rm /var/lib/ib_logfile1
# rm /var/lib/ib_logfile0
# /scripts/restartsrv_mysql

jika belum sehat, hapus ibdata1 dan restart lagi

infokan log 20 - 30 bari terakhir
 
Status
Not open for further replies.

Top