MySQL (Webuzo) Sering Mati

pradjadj · 30 Apr 2016

GPLHosting said:
Spek servernya sama atau tidak?
Lalu jumlah visitornya sama atau tidak ?

yg 2 sih engga.. yg 3 sih rata2 sama.. malah salah satunya ada yg sampai 10rb/hari visitors

pangeran1995 · 30 Apr 2016

ramnya naikin ke 2Gb atau 3Gb..dan cpunya usahakan 2 core kalo mau hasil yg terbaik

A43SJ · 30 Apr 2016

GPLHosting said:
Kemungkinan besar itu error di InnoDB nya, karena kekurangan Memory. Default storage engine nya webuzo adalah InnoDB.

Coba cek log nya dgn cara di bawah, lalu pastekan disini ya :

Code:

more /var/log/mysqld.log | grep error

Code:

160430  0:11:20 [Warning] IP address '118.193.155.25' could not be resolved: Nam
e or service not known
160430 00:11:46 mysqld_safe Number of processes running now: 0
160430 00:11:46 mysqld_safe mysqld restarted
160430  0:11:47 [Note] /usr/local/apps/mysql/bin/mysqld (mysqld 5.5.47) starting
as process 30820 ...
160430  0:11:47 InnoDB: The InnoDB memory heap is disabled
160430  0:11:47 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160430  0:11:47 InnoDB: Compressed tables use zlib 1.2.3
160430  0:11:48 InnoDB: Initializing buffer pool, size = 128.0M
160430  0:11:48 InnoDB: Completed initialization of buffer pool
160430  0:11:49 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 84282020
160430  0:11:49  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160430 00:11:50 mysqld_safe mysqld from pid file /var/lib/mysql/mysqld.pid ended
160430 00:16:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/
mysql
160430  0:16:02 [Note] /usr/local/apps/mysql/bin/mysqld (mysqld 5.5.47) starting
as process 32187 ...
160430  0:16:02 InnoDB: The InnoDB memory heap is disabled
160430  0:16:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160430  0:16:02 InnoDB: Compressed tables use zlib 1.2.3
160430  0:16:02 InnoDB: Initializing buffer pool, size = 128.0M
160430  0:16:02 InnoDB: Completed initialization of buffer pool
160430  0:16:02 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 84282020
160430  0:16:02  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 84282241
160430  0:16:02  InnoDB: Starting an apply batch of log records to the database.
..
InnoDB: Progress in percents: 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
160430  0:16:02  InnoDB: Waiting for the background threads to start
160430  0:16:03 InnoDB: 5.5.47 started; log sequence number 84282241
160430  0:16:03 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
160430  0:16:03 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
160430  0:16:03 [Note] Server socket created on IP: '0.0.0.0'.
160430  0:16:03 [Note] Event Scheduler: Loaded 0 events
160430  0:16:03 [Note] /usr/local/apps/mysql/bin/mysqld: ready for connections.
Version: '5.5.47'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distr
ibution
160430 01:03:58 mysqld_safe Number of processes running now: 0
160430 01:03:58 mysqld_safe mysqld restarted
160430  1:04:00 [Note] /usr/local/apps/mysql/bin/mysqld (mysqld 5.5.47) starting
as process 13033 ...
160430  1:04:01 InnoDB: The InnoDB memory heap is disabled
160430  1:04:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160430  1:04:01 InnoDB: Compressed tables use zlib 1.2.3
160430  1:04:02 InnoDB: Initializing buffer pool, size = 128.0M
160430  1:04:03 InnoDB: Completed initialization of buffer pool
160430  1:04:03 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160430  1:04:03  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160430 01:04:04 mysqld_safe mysqld from pid file /var/lib/mysql/mysqld.pid ended
160430 01:08:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/
mysql
160430  1:08:02 [Note] /usr/local/apps/mysql/bin/mysqld (mysqld 5.5.47) starting
as process 14373 ...
160430  1:08:02 InnoDB: The InnoDB memory heap is disabled
160430  1:08:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160430  1:08:02 InnoDB: Compressed tables use zlib 1.2.3
160430  1:08:02 InnoDB: Initializing buffer pool, size = 128.0M
160430  1:08:02 InnoDB: Completed initialization of buffer pool
160430  1:08:02 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160430  1:08:02  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160430  1:08:02  InnoDB: Waiting for the background threads to start
160430  1:08:03 InnoDB: 5.5.47 started; log sequence number 84600437
160430  1:08:03 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
160430  1:08:03 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
160430  1:08:03 [Note] Server socket created on IP: '0.0.0.0'.
160430  1:08:03 [Note] Event Scheduler: Loaded 0 events
160430  1:08:03 [Note] /usr/local/apps/mysql/bin/mysqld: ready for connections.
Version: '5.5.47'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distr
ibution

Ini hasilnya Tuan..

pangeran1995 said:
ramnya naikin ke 2Gb atau 3Gb..dan cpunya usahakan 2 core kalo mau hasil yg terbaik

Seperti yg saya bilang sebelumnya mas, modal masih belum cukup buat beli spek yg besar

Jadi butuh solusi dari masalah ini, meskipun website skarang masih adem ayem takutnya nanti tiba-tiba error lagi lagi dan lagi..

GPLHosting · 30 Apr 2016

Tuh, bener kan innodb nya

Kurang memory itu Om...

Waktu install VPS nya, bikin partisi swap ngga ?

Ini kyknya ngga bikin partisi swap, trus pake webuzo ... Rakus memory..

InnoDB nya ga kebagian memory dah ...

A43SJ · 30 Apr 2016

GPLHosting said:
Tuh, bener kan innodb nya
Kurang memory itu Om...

Waktu install VPS nya, bikin partisi swap ngga ?

Ini kyknya ngga bikin partisi swap, trus pake webuzo ... Rakus memory..

InnoDB nya ga kebagian memory dah ...

Positif InnoDB ya Om ?

Kagak, waktu install VPS langsung install OS lanjut langsung ke Webuzo.
Berarti mesti buat partisi Swap dulu ya om ?

Tapi waktu saya pake VPS yg 1Gb RAM nya masalahnya juga sama.
Berarti saya asumsikan website saya pake VPS 1Gb pun belum cukup yah ? Kecuali pake Swap ?

pangeran1995 · 30 Apr 2016

saran saya usahakan 2x lipat ram dari total cpu
misalkan 1core ram nya 2Gb..
karena yg akan di proses banyak untuk ram apa lagi masalah cache

GPLHosting · 30 Apr 2016

A43SJ said:
Positif InnoDB ya Om ?

Kagak, waktu install VPS langsung install OS lanjut langsung ke Webuzo.
Berarti mesti buat partisi Swap dulu ya om ?

Tapi waktu saya pake VPS yg 1Gb RAM nya masalahnya juga sama.
Berarti saya asumsikan website saya pake VPS 1Gb pun belum cukup yah ? Kecuali pake Swap ?

Lho itu jelas2 lognya Om... Innodb crash..

Partisi swap itu pas install/load/deploy OS di VPS nya Om.

Cb aja dicek dulu om, kl blm ada... Ya bikin deh swap partisinya... Bisa kan?

A43SJ · 30 Apr 2016

pangeran1995 said:
saran saya usahakan 2x lipat ram dari total cpu
misalkan 1core ram nya 2Gb..
karena yg akan di proses banyak untuk ram apa lagi masalah cache

Siap Om. Thanks sudah membantu masalah saya

GPLHosting said:
Lho itu jelas2 lognya Om... Innodb crash..

Partisi swap itu pas install/load/deploy OS di VPS nya Om.

Cb aja dicek dulu om, kl blm ada... Ya bikin deh swap partisinya... Bisa kan?

Saya beli VPS nya di "V", waktu deploy seingat saya ga ada pilihan buat Swap Memory deh.
Atau saya yg tidak lihat ?

saya cek pake

Code:

sudo swapon -s

sih ga ada yg muncul, yg berarti ga ada Swap nya ya ?

Saya searching sih dapet tutor nya, bisa dicek valid apa tidaknya tutor ini http://ads.id/forums/archive/index.php/t-188600.html

Oh, dan satu lagi.
Ga perlu reinstall VPS kan untuk buat Swap nya ? Soalnya web udah jalan di VPS ini.

GPLHosting · 30 Apr 2016

Kl jalankan swaop ga muncul, bener.. Ga ada swap partisinya.

Untuk link, saya rasa URL berikut akan mewakili, silakan dipelajari :
https://www.hardinal.com/blog/solusi-untuk-mysql-yang-tiba-tiba-mati-pada-webuzo/

VPS ga perlu di reinstall, swap bisa dibikin on-the-fly

pluto01 · 30 Apr 2016

A43SJ said:
Ga perlu reinstall VPS kan untuk buat Swap nya ? Soalnya web udah jalan di VPS ini.

Yupz ga perlu, tinggal dicreated swap lalu dionkan dan diedit fstabnya,
Dan kalo bisa dicoba tunning dikit2 mysqlnya dan dipantau, jika masih kena coba upgrade saja RAMnya misal ke 2048

Jika sakit berlanjut (setelah usaha maksimal sama sj) mungkin virtualmin/kloxo-mr bs dicoba2

MySQL (Webuzo) Sering Mati

pradjadj

Apprentice 1.0

pangeran1995

Hosting Guru

A43SJ

Beginner 2.0

GPLHosting

Hosting Guru

A43SJ

Beginner 2.0

pangeran1995

Hosting Guru

GPLHosting

Hosting Guru

A43SJ

Beginner 2.0

GPLHosting

Hosting Guru

pluto01

Hosting Guru