Messages

16

Indonesia Users / Re: Cara memindahkan (change owner) domain ke client selain admin

« on: 2014-06-29, 07:45:56 »

saya sebenarnya pingin mengubah nilai 'Number Of FastCGI Children'. Saat ini saya menggunakan nginxproxy, dan pada "limit" yang ada cuma:

Number Of Domains
 Unlimited   
Number Of Subdomains
 Unlimited   
Traffic (MB/Month)
 Unlimited   
Total Disk Usage (MB)
 Unlimited   
Number Of Ruby Process
 Unlimited   
Number Of Ftp Users
 Unlimited   
Number Of Rails Apps
 Unlimited   
Mail Disk Usage (MB)
 Unlimited   
Mail Account Num
 Unlimited   
Number Of Mailing Lists
 Unlimited   
Mysql Databases
 Unlimited   
Number Of Pointer Domains
 Unlimited   

Dibagian mana saya bisa menemukan 'Number Of FastCGI Children'?

17

Indonesia Users / Cara memindahkan (change owner) domain ke client selain admin

« on: 2014-06-29, 06:52:20 »

Mas Musthafa, saya mau tanya nih. Bagaimana cara memindahkan (change owner) domain ke client selain admin dengan mudah ya? Apakah harus melakukan del domain kemudian menambahkan domain tersebut ke client yang baru saja dibuat? Makasih..

18

Indonesia Users / Re: Arti Log Secure pada kloxo MR

« on: 2014-06-09, 11:22:11 »

Baik, saya sudah mengganti menjadi 10. namun, saya tidak menggunakan whitelist karena IP saya dinamis. Makasih ya om

19

Indonesia Users / Re: Arti Log Secure pada kloxo MR

« on: 2014-06-09, 10:50:54 »

di Lxguard sendiri ada banyak sekali IP Address yang diblokir. Saya menduga ada yang mencoba masuk melalui ssh menggunakan brute force.

Untuk pencegahan saya mengubah nilai pada "Disable When This Many Wrong Attempts" pada bagian Lxguard menjadi 2. Kemudian mengganti port ssh selain 22. Apakah yang saya lakukan sudah benar? langkah apa lagi yang harus saya lakukan untuk pencegahan brute force ssh?

20

Indonesia Users / Arti Log Secure pada kloxo MR

« on: 2014-06-09, 09:56:34 »

Mohon bantuannya, beberapa waktu yang lalu website saya loadingnya sangat lambat. Ketika saya cek di log manager bagian Secure muncul log seperti berikut:

Code: [Select]

Jun  8 03:38:46 vps sshd[3998]: refused connect from 95.253.198.178 (95.253.198.178)
Jun  8 03:39:38 vps Rootkit Hunter: Rootkit hunter check started (version 1.4.0)
Jun  8 03:46:21 vps sshd[7763]: refused connect from 95.253.198.178 (95.253.198.178)
Jun  8 03:46:35 vps Rootkit Hunter: Scanning took 6 minutes and 55 seconds
Jun  8 03:46:35 vps Rootkit Hunter: Please inspect this machine, because it may be infected.
Jun  8 03:53:55 vps sshd[10427]: refused connect from 95.253.198.178 (95.253.198.178)
Jun  8 04:01:42 vps sshd[10469]: refused connect from 95.253.198.178 (95.253.198.178)
Jun  8 04:16:50 vps sshd[10590]: refused connect from 95.253.198.178 (95.253.198.178)
Jun  8 04:24:24 vps sshd[10647]: refused connect from 95.253.198.178 (95.253.198.178)
Jun  8 04:32:06 vps sshd[10665]: refused connect from 95.253.198.178 (95.253.198.178)
Jun  8 04:39:46 vps sshd[10692]: refused connect from 95.253.198.178 (95.253.198.178)
Jun  8 04:47:16 vps sshd[10714]: refused connect from 95.253.198.178 (95.253.198.178)
Jun  8 04:53:54 vps sshd[10730]: refused connect from 116.10.191.169 (116.10.191.169)
Jun  8 04:54:31 vps sshd[10733]: refused connect from 95.253.198.178 (95.253.198.178)
Jun  8 05:02:16 vps sshd[10768]: refused connect from 95.253.198.178 (95.253.198.178)
Jun  8 05:09:54 vps sshd[10790]: refused connect from 95.253.198.178 (95.253.198.178)
Jun  8 05:17:19 vps sshd[10820]: refused connect from 95.253.198.178 (95.253.198.178)
Jun  8 05:25:29 vps sshd[10859]: refused connect from 116.10.191.166 (116.10.191.166)
Jun  8 05:32:03 vps sshd[10891]: refused connect from 95.253.198.178 (95.253.198.178)
Jun  8 05:39:45 vps sshd[10927]: refused connect from 95.253.198.178 (95.253.198.178)
Jun  8 05:46:15 vps sshd[1617]: Received disconnect from 125.164.2.161: 11: User exit
Jun  8 05:46:15 vps sshd[1617]: pam_unix(sshd:session): session closed for user root
Jun  8 05:46:16 vps sshd[979]: Received signal 15; terminating.
Jun  8 05:46:16 vps sshd[10969]: Server listening on 0.0.0.0 port 22000.
Jun  8 05:46:16 vps sshd[10969]: Server listening on :: port 22000.
Jun  8 05:46:32 vps sshd[10972]: reverse mapping checking getaddrinfo for 161.subnet125-164-2.speedy.telkom.net.id [125.164.2.161] failed - POSSIBLE BREAK-IN ATTEMPT!
Jun  8 05:46:32 vps sshd[10972]: Accepted password for root from 125.164.2.161 port 54370 ssh2
Jun  8 05:46:32 vps sshd[10972]: pam_unix(sshd:session): session opened for user root by (uid=0)
Jun  8 05:46:32 vps sshd[10972]: subsystem request for sftp
Jun  8 05:46:32 vps sshd[10972]: subsystem request for sftp
Jun  8 05:46:32 vps sshd[10976]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory
Jun  8 05:46:32 vps sshd[10976]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory
Jun  8 06:46:44 vps sshd[10972]: Received disconnect from 125.164.2.161: 11: User exit
Jun  8 06:46:44 vps sshd[10972]: pam_unix(sshd:session): session closed for user root
Jun  8 07:18:03 vps sshd[11571]: reverse mapping checking getaddrinfo for 161.subnet125-164-2.speedy.telkom.net.id [125.164.2.161] failed - POSSIBLE BREAK-IN ATTEMPT!
Jun  8 07:18:06 vps sshd[11571]: Accepted password for root from 125.164.2.161 port 60346 ssh2
Jun  8 07:18:08 vps sshd[11571]: pam_unix(sshd:session): session opened for user root by (uid=0)
Jun  8 07:18:08 vps sshd[11571]: subsystem request for sftp
Jun  8 07:18:08 vps sshd[11574]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory
Jun  8 07:18:08 vps sshd[11574]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory
Jun  8 07:21:38 vps sshd[11571]: Received disconnect from 125.164.2.161: 11: User exit
Jun  8 07:21:38 vps sshd[11571]: pam_unix(sshd:session): session closed for user root
Jun  8 07:22:28 vps sshd[11663]: reverse mapping checking getaddrinfo for 161.subnet125-164-2.speedy.telkom.net.id [125.164.2.161] failed - POSSIBLE BREAK-IN ATTEMPT!
Jun  8 07:22:28 vps sshd[11663]: Accepted password for root from 125.164.2.161 port 60595 ssh2
Jun  8 07:22:28 vps sshd[11663]: pam_unix(sshd:session): session opened for user root by (uid=0)
Jun  8 07:22:29 vps sshd[11663]: subsystem request for sftp
Jun  8 07:22:29 vps sshd[11666]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory
Jun  8 07:22:29 vps sshd[11666]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory
Jun  8 07:23:00 vps sshd[11663]: Received disconnect from 125.164.2.161: 11: User exit
Jun  8 07:23:00 vps sshd[11663]: pam_unix(sshd:session): session closed for user root
Jun  9 03:43:47 vps Rootkit Hunter: Rootkit hunter check started (version 1.4.0)
Jun  9 03:47:45 vps Rootkit Hunter: Scanning took 3 minutes and 57 seconds
Jun  9 03:47:45 vps Rootkit Hunter: Please inspect this machine, because it may be infected.

21

Indonesia Users / bagaimana cara mengganti nama hostname?

« on: 2014-05-23, 13:16:15 »

bagaimana ya caranya mengganti hostname ya? Domain saya mau expired, jadi malas memperpanjang

Sebelumnya: vps.blablabla.com
diganti menjadi: vps.bliblibli.com

Saya mencoba mengganti hostname malalui Control Panel yang disediakan oleh pihak hosting, namun ketika saya ganti vps.bliblibli.com, kemudian reboot. Malah IP tidak bisa diakses, login Kloxo-MR pun tidak bisa. Apakah ada settingan pada Kloxo-MR yang perlu diubah juga??

22

Indonesia Users / Re: Alert: mailaccount_add_failed...

« on: 2014-05-22, 14:31:13 »

sudah mas.. Makasih ya mas..

23

Indonesia Users / Re: Error saat Switch Program nginxproxy ke httpd

« on: 2014-05-22, 13:53:34 »

saya belum pernah mengalami mas..

24

Indonesia Users / Re: Alert: mailaccount_add_failed...

« on: 2014-05-22, 13:49:10 »

Saya mencoba "sh /script/fixwebmail" dan berhasil login email dengan benar. Masihkah perlu mengubah menjadi MyIsam??

@zenkul: Iya, gpp mas..

25

Indonesia Users / Re: Alert: mailaccount_add_failed...

« on: 2014-05-22, 13:36:12 »

Alhamdulillah setelah reset mysql password kini saya bisa menambah email akun.. namun, ketika mengakses roundcube. Ada peringatan

DATABASE ERROR: CONNECTION FAILED!
Unable to connect to the database!

ini harus gimana ya mas musthafa?

26

Indonesia Users / Re: Alert: mailaccount_add_failed...

« on: 2014-05-22, 13:16:11 »

Ini barusan saya reboot kemudian dikasih perintah 'sh /script/restart-all', balik OK lagi. Hmmmmmmmm...

[root@vps ~]# sh /script/restart-all
Stopping mysqld:                                           [  OK  ]
Starting mysqld:                                           [  OK  ]
Stopping Djbdns for:
  - axfrdns    [  OK  ]
  - tinydns    [  OK  ]
Starting Djbdns for:
  - axfrdns    [  OK  ]
  - tinydns    [  OK  ]
Stopping qmail-toaster: svscan qmail logging.
qmail-send: no process killed
Starting qmail-toaster: svscan.
Stopping kloxo-phpcgi:                                     [  OK  ]
Starting kloxo-phpcgi:                                     [  OK  ]
Stopping kloxo-hiawatha:                                   [  OK  ]
Starting kloxo-hiawatha:                                   [  OK  ]
Stopping php-fpm:                                          [  OK  ]
Starting php-fpm:                                          [  OK  ]
[root@vps ~]#

Saya mau lanjutkan reset mysql password

27

Indonesia Users / Re: Alert: mailaccount_add_failed...

« on: 2014-05-22, 13:11:08 »

Hasil sh /script/cleanup belum memuaskan:

*** Restart services - BEGIN ***
Stopping mysqld:                                           [  OK  ]
MySQL Daemon failed to start.
Starting mysqld:                                           [FAILED]
Stopping Djbdns for:
  - axfrdns    [  OK  ]
  - tinydns    [  OK  ]
Starting Djbdns for:
  - axfrdns    [FAILED]
  - tinydns    [FAILED]
Stopping Hiawatha web server:                              [FAILED]
Stopping qmail-toaster: svscan qmail logging.
qmail-send: no process killed
Starting qmail-toaster: svscan.
Stopping kloxo-phpcgi:                                     [  OK  ]
Starting kloxo-phpcgi:                                     [  OK  ]
Stopping kloxo-hiawatha:                                   [  OK  ]
Starting kloxo-hiawatha:                                   [  OK  ]
Stopping php-fpm:                                          [  OK  ]
Starting php-fpm:                                          [  OK  ]
*** Restart services - END ***

Process Time: 00:01:58:31.7111750 (dd:hh:mm:ss:xxxxxx)

Ini hasil 'cat /var/log/mysqld.log'

InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140522 11:05:26  InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140522 11:07:07  InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
140522 11:07:07  InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
140522 11:07:07 InnoDB: Could not open or create data files.
140522 11:07:07 InnoDB: If you tried to add new data files, and it failed here,
140522 11:07:07 InnoDB: you should now edit innodb_data_file_path in my.cnf back
140522 11:07:07 InnoDB: to what it was, and remove the new ibdata files InnoDB created
140522 11:07:07 InnoDB: in this failed attempt. InnoDB only wrote those files full of
140522 11:07:07 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
140522 11:07:07 InnoDB: remove old data files which contain your precious data!
140522 11:07:07 [ERROR] Plugin 'InnoDB' init function returned error.
140522 11:07:07 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
140522 11:07:07 [ERROR] Failed to initialize plugins.
140522 11:07:07 [ERROR] Aborting

140522 11:07:07 [Note] /usr/libexec/mysqld: Shutdown complete

140522 11:07:07 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

28

Indonesia Users / Re: Alert: mailaccount_add_failed...

« on: 2014-05-22, 12:32:35 »

Aduh mas musthafa, maaf saya baru membaca

Ini tadi gara2 pingin reset mysql password dengan cara di atas tidak berhasil, saya mencoba menggunakan perintah:

sh /script/restart-all;
chmod -R 777 /script;
sh /script/cleanup; (masih nyampe sini, belum kelar-kelar dr jam 4an tadi. Mungkin karena trafik pengunjungnya lagi puncak-puncaknya)

Rencananya habis dari ini, mau lanjut ke:
sh /script/reset-mysql-root-password blablabla;

29

Indonesia Users / Re: Alert: mailaccount_add_failed...

« on: 2014-05-22, 10:54:46 »

Ada pesan error muncul

[root@vps ~]# sh /script/reset-mysql-root-password blablabla
Stop MySQL service...
MySQL ROOT password reset...
Start MySQL service...
Connect failed: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
[root@vps ~]#

30

Indonesia Users / Re: Alert: mailaccount_add_failed...

« on: 2014-05-22, 10:44:38 »

[root@vps ~]# sh /script/sysinfo

A. Kloxo-MR: 6.5.0.f-2014051901

B. OS: CentOS release 6.5 (Final) i686

C. Apps:
   1. MySQL: mysql55-5.5.37-1.ius.el6.i686
   2. PHP: php53u-5.3.28-3.ius.el6.i686
   3. Httpd: httpd-2.2.27-1.el6.i686
   4. Lighttpd: --uninstalled--
   5. Nginx: nginx-1.7.0-1.el6.i686
   6. Qmail: qmail-toaster-1.03-1.3.38.mr.el6.i386
      - with: courier-imap-toaster-4.1.2-1.3.16.mr.el6.i386
   7. Dns: djbdns-1.05-17.3.mr.el6.i686

D. Php-type (for Httpd/proxy): php-fpm_event

E. Memory:
                total       used       free     shared    buffers     cached
   Mem:          1003        499        504          0          2        215
   -/+ buffers/cache:        280        722
   Swap:         1023          0       1023


[root@vps ~]# yum list postfix* exim*; id -u postfix

Loaded plugins: fastestmirror, priorities, protectbase, replace
Loading mirror speeds from cached hostfile
 * base: centos.mirror.rafal.ca
 * extras: centos.mirror.rafal.ca
 * kloxo-mr-centalt: rpms.mratwork.com
 * kloxo-mr-epel: mirrors.syringanetworks.net
 * kloxo-mr-ius: dfw.mirror.rackspace.com
 * kloxo-mr-ius-c5: dl.iuscommunity.org
 * kloxo-mr-release-neutral-arch: github.com
 * kloxo-mr-release-neutral-noarch: github.com
 * kloxo-mr-release-version-arch: github.com
 * kloxo-mr-release-version-noarch: github.com
 * mratwork-epel: mirrors.syringanetworks.net
 * mratwork-ius-stable: dfw.mirror.rackspace.com
 * rpmforge: mirror.team-cymru.org
 * updates: centos.mirror.rafal.ca
0 packages excluded due to repository protections
Available Packages
exim.i686                            4.82-1.el6                 kloxo-mr-centalt
exim-doc.noarch                      4.69-4.el6                 kloxo-mr-epel
exim-greylist.i686                   4.82-1.el6                 kloxo-mr-centalt
exim-mon.i686                        4.82-1.el6                 kloxo-mr-centalt
exim-mysql.i686                      4.82-1.el6                 kloxo-mr-centalt
exim-pgsql.i686                      4.82-1.el6                 kloxo-mr-centalt
exim-sa.i686                         4.82-1.el6                 kloxo-mr-centalt
postfix.i686                         2:2.10.2-1.el6             kloxo-mr-centalt
postfix-perl-scripts.i686            2:2.10.2-1.el6             kloxo-mr-centalt
id: postfix: No such user