MRatWork Forum by Mustafa Ramadhan - Alert: mailaccount_add_failed...

Sponsor:
Server and Web Integrator
Link:
6.5.0 or 7.0.0
Click for "How to install"
Donation/Sponsorship:
Kloxo-MR is open-source.
Donate and or Sponsorship always welcome.
Click to:

MRatWork Forum | Please login or register. | 2017-11-07, 21:37:33

- MRatWork Forum by Mustafa Ramadhan »
- Language Specific Discussions »
- Indonesia Users »
- Alert: mailaccount_add_failed...

« previous next »

- Print

Pages: [1] 2 Go Down

### Author Topic: Alert: mailaccount_add_failed... (Read 4173 times)

0 Members and 1 Guest are viewing this topic.

#### anasmcguire

- Junior Member
- Posts: 37
- Karma: +0/-0
- Gender:

##### Alert: mailaccount_add_failed...

« on: 2014-05-22, 09:20:57 »
Saya gagal menambahkan akun email,
Pesan errornya cuma "Alert: mailaccount_add_failed...". bagaimana cara memperbaikinya sehingga saya dapat menambahkan akun email?
Logged
Kloxo-MR emang markotop!!!

#### MRatWork

- Administrator
- The Elite
- Posts: 15,381
- Karma: +112/-9
- Gender:

##### Re: Alert: mailaccount_add_failed...

« Reply #1 on: 2014-05-22, 09:22:37 »
Mestinya kalau anda coba akan berhasil (karena mekanisme 'perbaikan').
Tapi, untuk lebih yakin, jalankan 'sh /script/fixmail-all' (2x).
Logged
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

#### anasmcguire

- Junior Member
- Posts: 37
- Karma: +0/-0
- Gender:

##### Re: Alert: mailaccount_add_failed...

« Reply #2 on: 2014-05-22, 09:41:14 »
Saya sudah mencoba, hasilnya tetap sama untuk semua domain.
---
Alert: mailaccount_add_failed
---
Logged
Kloxo-MR emang markotop!!!

#### MRatWork

- Administrator
- The Elite
- Posts: 15,381
- Karma: +112/-9
- Gender:

##### Re: Alert: mailaccount_add_failed...

« Reply #3 on: 2014-05-22, 10:17:40 »
Informasikan 'sh /script/sysinfo; yum list postfix* exim*; id -u postfix'.
Logged
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

#### anasmcguire

- Junior Member
- Posts: 37
- Karma: +0/-0
- Gender:

##### Re: Alert: mailaccount_add_failed...

« Reply #4 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
Logged
Kloxo-MR emang markotop!!!

#### MRatWork

- Administrator
- The Elite
- Posts: 15,381
- Karma: +112/-9
- Gender:

##### Re: Alert: mailaccount_add_failed...

« Reply #5 on: 2014-05-22, 10:49:06 »
Coba lakukan 'sh /script/reset-mysql-root-password PASSWORDANDA; sh /script/fixmail-all; sh /script/restart-mail'.
Logged
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

#### anasmcguire

- Junior Member
- Posts: 37
- Karma: +0/-0
- Gender:

##### Re: Alert: mailaccount_add_failed...

« Reply #6 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 ~]#
Logged
Kloxo-MR emang markotop!!!

#### MRatWork

- Administrator
- The Elite
- Posts: 15,381
- Karma: +112/-9
- Gender:

##### Re: Alert: mailaccount_add_failed...

« Reply #7 on: 2014-05-22, 11:44:37 »
Berarti masalahnya berawal dari mysql. Apa hasil dari 'service mysqld service'?.
Coba infokan juga 20 baris terakhir dari 'cat /var/log/mysqld.log'.
Logged
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

#### zenkul

- Global Moderator
- Master
- Posts: 383
- Karma: +3/-0

##### Re: Alert: mailaccount_add_failed...

« Reply #8 on: 2014-05-22, 12:05:26 »
my.cnf
mungkin ?
saya lebih suka my.cnf lama : "cp -f /usr/share/mysql/my-medium.cnf /etc/my.cnf"
minggu kemarin saya juga nggak bisa login dan ngga bisa reset password gara-gara my.cnf
dan barusan untuk convert ke mariadb perlu waktu 2 jam juga gara-gara my.cnf
(nggak tahu salahnya dimana)
mungkin ?
Logged
easy, secure and speed up web panel ===> Kloxo-MR

#### anasmcguire

- Junior Member
- Posts: 37
- Karma: +0/-0
- Gender:

##### Re: Alert: mailaccount_add_failed...

« Reply #9 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;
« Last Edit: 2014-05-22, 12:44:06 by anasmcguire »
Logged
Kloxo-MR emang markotop!!!

#### MRatWork

- Administrator
- The Elite
- Posts: 15,381
- Karma: +112/-9
- Gender:

##### Re: Alert: mailaccount_add_failed...

« Reply #10 on: 2014-05-22, 12:51:33 »
Quote from: zenkul on 2014-05-22, 12:05:26

> my.cnf
> mungkin ?
> saya lebih suka my.cnf lama : "cp -f /usr/share/mysql/my-medium.cnf /etc/my.cnf"
> minggu kemarin saya juga nggak bisa login dan ngga bisa reset password gara-gara my.cnf
> dan barusan untuk convert ke mariadb perlu waktu 2 jam juga gara-gara my.cnf
> (nggak tahu salahnya dimana)
> mungkin ?

Tolong bandingkan isi my.cnf dari mysql55 bawaan IUS dengan mysql dari cp -f /usr/share/mysql/my-medium.cnf
Logged
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

#### anasmcguire

- Junior Member
- Posts: 37
- Karma: +0/-0
- Gender:

##### Re: Alert: mailaccount_add_failed...

« Reply #11 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
Logged
Kloxo-MR emang markotop!!!

#### anasmcguire

- Junior Member
- Posts: 37
- Karma: +0/-0
- Gender:

##### Re: Alert: mailaccount_add_failed...

« Reply #12 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
Logged
Kloxo-MR emang markotop!!!

#### anasmcguire

- Junior Member
- Posts: 37
- Karma: +0/-0
- Gender:

##### Re: Alert: mailaccount_add_failed...

« Reply #13 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?
Logged
Kloxo-MR emang markotop!!!

#### MRatWork

- Administrator
- The Elite
- Posts: 15,381
- Karma: +112/-9
- Gender:

##### Re: Alert: mailaccount_add_failed...

« Reply #14 on: 2014-05-22, 13:41:43 »
Coba ubah storage-engine utk mysql dengan 'sh /script/mysql-convert --engine=myisam'.
Logged
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

- Print

Pages: [1] 2 Go Up
« previous next »

- MRatWork Forum by Mustafa Ramadhan »
- Language Specific Discussions »
- Indonesia Users »
- Alert: mailaccount_add_failed...

Top 10 Social Networking: Facebook Twitter LinkedIn Pinterest Google Plus Tumblr Instagram VK Flickr Vine

..:: Monetize your Website or Blog with BidVertiser ::.. ..:: Sell your ad space with BidVertiser ::..

- Design By SMFSimple.com
- SMF 2.0.14 | SMF © 2017, Simple Machines

Page created in 0.046 seconds with 17 queries.

Mirror created by MasterkinG32.CoM