Messages

31

Kloxo-MR Technical Helps / PHP Config page showing blank

« on: 2014-10-09, 07:20:24 »

Hi
i am using latest build  7.0.0.b-2014100804 php config page is showing up blank

this link
ip:7778/display.php?frm_action=show&frm_o_o[0][class]=phpini

32

Kloxo-MR Technical Helps / Re: Today update crashed my system!

« on: 2014-10-06, 20:33:23 »

is panel working?

33

Kloxo-MR Technical Helps / Re: Today update crashed my system!

« on: 2014-10-06, 19:29:27 »

do
sh /script/restart-all

if not then
sh /script/cleanup

34

Kloxo-MR Technical Helps / Re: Nginx with Varnish Why doesnt it work?

« on: 2014-10-06, 19:24:22 »

any fix for nginx with varnish?

35

Kloxo-MR Technical Helps / Re: Nginx with Varnish Why doesnt it work?

« on: 2014-10-06, 12:05:45 »

hmm waiting....

36

Kloxo-MR Technical Helps / Re: Nginx with Varnish Why doesnt it work?

« on: 2014-10-05, 18:05:22 »

how to install/use openlitespeed?

37

Kloxo-MR Technical Helps / Re: Nginx with Varnish Why doesnt it work?

« on: 2014-10-05, 17:32:48 »

yes cache is working with hiawatha and lighttpd

38

Kloxo-MR Technical Helps / Re: Nginx with Varnish Why doesnt it work?

« on: 2014-10-05, 16:01:09 »

Using any cache with nginx will cause this issue

39

Kloxo-MR Technical Helps / Re: Nginx with Varnish Why doesnt it work?

« on: 2014-10-05, 13:03:24 »

sh /script/restart-all
Stopping mysqld:                                           [  OK  ]
Starting mysqld:                                           [  OK  ]
Stopping named: .                                          [  OK  ]
Starting named:                                            [  OK  ]
Stopping Varnish Cache:                                    [  OK  ]
Starting Varnish Cache:                                    [  OK  ]
Stopping nginx:                                            [  OK  ]
Starting nginx:                                            [  OK  ]
Stopping qmail-toaster: svscan qmail logging.
qmail-send: no process killed
Starting qmail-toaster: svscan.
Stopping xinetd:                                           [  OK  ]
Starting xinetd:                                           [  OK  ]
Execute fixlxphpexe for php53s...
Stopping kloxo-phpcgi:                                     [  OK  ]
Starting kloxo-phpcgi:                                     [  OK  ]
Starting kloxo-hiawatha:                                   [  OK  ]
Stopping php54m-fpm:                                       [  OK  ]
Starting php54m-fpm:                                       [  OK  ]





sh /script/sysinfo

A. Kloxo-MR: 7.0.0.b-2014100502

B. OS: CentOS release 6.5 (Final) x86_64

C. Apps:
   1. MySQL: mysql55-5.5.39-1.ius.el6.x86_64
   2. PHP: php54-5.4.32-2.ius.el6.x86_64
   3. Httpd: httpd-2.2.29-1.mr.el6.x86_64
   4. Lighttpd: --uninstalled--
   5. Hiawatha: hiawatha-9.8.0-f.2.mr.el6.x86_64
   6. Nginx: nginx-1.7.6-1.el6.ngx.x86_64
   7. Cache: varnish-3.0.5-1.el6.x86_64
   8. Dns: bind-9.9.5-1.el6.x86_64
   9. Qmail: qmail-toaster-1.03-1.3.38.mr.el6.x86_64
      - with: courier-imap-toaster-4.1.2-1.3.16.mr.el6.x86_64

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

E. Memory:
                total       used       free     shared    buffers     cached
   Mem:           512        458         53          0          0        112
   -/+ buffers/cache:        346        165
   Swap:          512        159        352

40

Kloxo-MR Technical Helps / Nginx with Varnish Why doesnt it work?

« on: 2014-10-05, 08:18:15 »

Hi whenever i enable nginx with varnish i get this page

Code: [Select]

Welcome to nginx!

If you see this page, the nginx web server is successfully installed and working. Further configuration is required.

For online documentation and support please refer to nginx.org.
Commercial support is available at nginx.com.

Thank you for using nginx.
it works fine when only using nginx

41

Kloxo-MR Technical Helps / Re: Problem with installing on CentOS

« on: 2014-08-24, 18:26:10 »

ur welcome

42

Kloxo-MR Technical Helps / Re: Problem with installing on CentOS

« on: 2014-08-24, 17:52:46 »

reinstall centos 6.5

do the following

yum update -y
yum install yum-utils yum-priorities vim-minimal subversion curl zip unzip -y
yum install telnet wget -y

setenforce 0
echo 'SELINUX=disabled' > /etc/selinux/config

cd /tmp
wget https://github.com/mustafaramadhan/kloxo/raw/rpms/release/neutral/noarch/mratwork-release-0.0.1-1.noarch.rpm --no-check-certificate
rpm -ivh mratwork-release-0.0.1-1.noarch.rpm

cd /
yum clean all
yum update -y
yum install kloxomr -y
sh /script/upcp -y (when asked)

43

Kloxo-MR Technical Helps / Cant Send Email to Live / Hotmail / Outlook

« on: 2014-08-24, 17:47:16 »

Hi

I am getting this error any fix?

Connected to 65.55.33.135 but sender was rejected.
Remote host said: 550 SC-001 (COL004-MC6F35) Unfortunately, messages from 23.226.148.548 weren't sent. Please contact your Internet service provider since part of their network is on our block list. You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors.

44

Kloxo-MR Technical Helps / Repo Issue when installing

« on: 2013-07-11, 14:05:35 »

Code: [Select]

Loaded plugins: fastestmirror, priorities, protectbase, replace
Loading mirror speeds from cached hostfile
 * base: ftp.hosteurope.de
 * extras: ftp.hosteurope.de
 * kloxo-mr-epel: ftp.fi.muni.cz
 * kloxo-mr-ius: ftp.astral.ro
 * updates: ftp.hosteurope.de
base                                                     | 3.7 kB     00:00
extras                                                   | 3.4 kB     00:00
kloxo-mr-centalt                                         |  951 B     00:00
kloxo-mr-epel                                            | 4.2 kB     00:00
kloxo-mr-ius                                             | 2.2 kB     00:00
kloxo-mr-ius/primary_db                                  | 126 kB     00:00
kloxo-mr-ius-c5                                          | 2.2 kB     00:00
kloxo-mr-ius-c5/primary_db                               | 188 kB     00:00
kloxo-mr-release-neutral-arch                            |  951 B     00:00
kloxo-mr-release-neutral-noarch                          |  951 B     00:00
kloxo-mr-release-version-arch                            |  951 B     00:00
kloxo-mr-release-version-noarch                          |  951 B     00:00
updates                                                  | 3.4 kB     00:00
updates/primary_db                                       | 3.2 MB     00:00
vz-base                                                  |  951 B     00:00
vz-updates                                               |  951 B     00:00
0 packages excluded due to repository protections
Setting up Upgrade Process
Resolving Dependencies
--> Running transaction check
---> Package mysql-libs.x86_64 0:5.1.69-1.el6_4 will be updated
--> Processing Dependency: libmysqlclient.so.16()(64bit) for package: php53u-mysql-5.3.26-2.ius.el6.x86_64
--> Processing Dependency: libmysqlclient.so.16()(64bit) for package: lxlighttpd-1.4.32-2.mr.el6.x86_64
--> Processing Dependency: libmysqlclient.so.16()(64bit) for package: pure-ftpd-1.0.36-5.mr.el6.x86_64
--> Processing Dependency: libmysqlclient.so.16()(64bit) for package: lxphp-5.2.17-10.mr.el6.x86_64
--> Processing Dependency: libmysqlclient.so.16(libmysqlclient_16)(64bit) for package: php53u-mysql-5.3.26-2.ius.el6.x86_64
--> Processing Dependency: libmysqlclient.so.16(libmysqlclient_16)(64bit) for package: lxlighttpd-1.4.32-2.mr.el6.x86_64
--> Processing Dependency: libmysqlclient.so.16(libmysqlclient_16)(64bit) for package: pure-ftpd-1.0.36-5.mr.el6.x86_64
--> Processing Dependency: libmysqlclient.so.16(libmysqlclient_16)(64bit) for package: lxphp-5.2.17-10.mr.el6.x86_64
---> Package mysql-libs.x86_64 0:5.5.29-1.el6 will be an update
---> Package python.x86_64 0:2.6.6-36.el6 will be updated
---> Package python.x86_64 0:2.6.6-37.el6_4 will be an update
---> Package python-libs.x86_64 0:2.6.6-36.el6 will be updated
---> Package python-libs.x86_64 0:2.6.6-37.el6_4 will be an update
--> Finished Dependency Resolution
Error: Package: pure-ftpd-1.0.36-5.mr.el6.x86_64 (@kloxo-mr-release-version-arch)
           Requires: libmysqlclient.so.16()(64bit)
           Removing: mysql-libs-5.1.69-1.el6_4.x86_64 (@updates)
               libmysqlclient.so.16()(64bit)
           Updated By: mysql-libs-5.5.29-1.el6.x86_64 (kloxo-mr-centalt)
               Not found
           Available: mysql-libs-5.1.66-2.el6_3.x86_64 (base)
               libmysqlclient.so.16()(64bit)
           Available: mysql-libs-5.1.67-1.el6_3.x86_64 (updates)
               libmysqlclient.so.16()(64bit)
Error: Package: php53u-mysql-5.3.26-2.ius.el6.x86_64 (@kloxo-mr-ius)
           Requires: libmysqlclient.so.16(libmysqlclient_16)(64bit)
           Removing: mysql-libs-5.1.69-1.el6_4.x86_64 (@updates)
               libmysqlclient.so.16(libmysqlclient_16)(64bit)
           Updated By: mysql-libs-5.5.29-1.el6.x86_64 (kloxo-mr-centalt)
               Not found
           Available: mysql-libs-5.1.66-2.el6_3.x86_64 (base)
               libmysqlclient.so.16(libmysqlclient_16)(64bit)
           Available: mysql-libs-5.1.67-1.el6_3.x86_64 (updates)
               libmysqlclient.so.16(libmysqlclient_16)(64bit)
Error: Package: lxlighttpd-1.4.32-2.mr.el6.x86_64 (@kloxo-mr-release-version-arch)
           Requires: libmysqlclient.so.16(libmysqlclient_16)(64bit)
           Removing: mysql-libs-5.1.69-1.el6_4.x86_64 (@updates)
               libmysqlclient.so.16(libmysqlclient_16)(64bit)
           Updated By: mysql-libs-5.5.29-1.el6.x86_64 (kloxo-mr-centalt)
               Not found
           Available: mysql-libs-5.1.66-2.el6_3.x86_64 (base)
               libmysqlclient.so.16(libmysqlclient_16)(64bit)
           Available: mysql-libs-5.1.67-1.el6_3.x86_64 (updates)
               libmysqlclient.so.16(libmysqlclient_16)(64bit)
Error: Package: lxphp-5.2.17-10.mr.el6.x86_64 (@kloxo-mr-release-version-arch)
           Requires: libmysqlclient.so.16(libmysqlclient_16)(64bit)
           Removing: mysql-libs-5.1.69-1.el6_4.x86_64 (@updates)
               libmysqlclient.so.16(libmysqlclient_16)(64bit)
           Updated By: mysql-libs-5.5.29-1.el6.x86_64 (kloxo-mr-centalt)
               Not found
           Available: mysql-libs-5.1.66-2.el6_3.x86_64 (base)
               libmysqlclient.so.16(libmysqlclient_16)(64bit)
           Available: mysql-libs-5.1.67-1.el6_3.x86_64 (updates)
               libmysqlclient.so.16(libmysqlclient_16)(64bit)
Error: Package: pure-ftpd-1.0.36-5.mr.el6.x86_64 (@kloxo-mr-release-version-arch)
           Requires: libmysqlclient.so.16(libmysqlclient_16)(64bit)
           Removing: mysql-libs-5.1.69-1.el6_4.x86_64 (@updates)
               libmysqlclient.so.16(libmysqlclient_16)(64bit)
           Updated By: mysql-libs-5.5.29-1.el6.x86_64 (kloxo-mr-centalt)
               Not found
           Available: mysql-libs-5.1.66-2.el6_3.x86_64 (base)
               libmysqlclient.so.16(libmysqlclient_16)(64bit)
           Available: mysql-libs-5.1.67-1.el6_3.x86_64 (updates)
               libmysqlclient.so.16(libmysqlclient_16)(64bit)
Error: Package: php53u-mysql-5.3.26-2.ius.el6.x86_64 (@kloxo-mr-ius)
           Requires: libmysqlclient.so.16()(64bit)
           Removing: mysql-libs-5.1.69-1.el6_4.x86_64 (@updates)
               libmysqlclient.so.16()(64bit)
           Updated By: mysql-libs-5.5.29-1.el6.x86_64 (kloxo-mr-centalt)
               Not found
           Available: mysql-libs-5.1.66-2.el6_3.x86_64 (base)
               libmysqlclient.so.16()(64bit)
           Available: mysql-libs-5.1.67-1.el6_3.x86_64 (updates)
               libmysqlclient.so.16()(64bit)
Error: Package: lxlighttpd-1.4.32-2.mr.el6.x86_64 (@kloxo-mr-release-version-arch)
           Requires: libmysqlclient.so.16()(64bit)
           Removing: mysql-libs-5.1.69-1.el6_4.x86_64 (@updates)
               libmysqlclient.so.16()(64bit)
           Updated By: mysql-libs-5.5.29-1.el6.x86_64 (kloxo-mr-centalt)
               Not found
           Available: mysql-libs-5.1.66-2.el6_3.x86_64 (base)
               libmysqlclient.so.16()(64bit)
           Available: mysql-libs-5.1.67-1.el6_3.x86_64 (updates)
               libmysqlclient.so.16()(64bit)
Error: Package: lxphp-5.2.17-10.mr.el6.x86_64 (@kloxo-mr-release-version-arch)
           Requires: libmysqlclient.so.16()(64bit)
           Removing: mysql-libs-5.1.69-1.el6_4.x86_64 (@updates)
               libmysqlclient.so.16()(64bit)
           Updated By: mysql-libs-5.5.29-1.el6.x86_64 (kloxo-mr-centalt)
               Not found
           Available: mysql-libs-5.1.66-2.el6_3.x86_64 (base)
               libmysqlclient.so.16()(64bit)
           Available: mysql-libs-5.1.67-1.el6_3.x86_64 (updates)
               libmysqlclient.so.16()(64bit)
 You could try using --skip-broken to work around the problem
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
cronie-1.4.4-7.el6.x86_64 has missing requires of /usr/sbin/sendmail

45

Kloxo-MR Technical Helps / Re: Need Help Urgent MYSQL Error

« on: 2013-07-10, 18:17:36 »

Code: [Select]

130710 10:12:47 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130710 10:12:47 InnoDB: The InnoDB memory heap is disabled
130710 10:12:47 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130710 10:12:47 InnoDB: Compressed tables use zlib 1.2.3
130710 10:12:47 InnoDB: Using Linux native AIO
130710 10:12:47  InnoDB: Warning: io_setup() failed with EAGAIN. Will make 5 attempts before giving up.
InnoDB: Warning: io_setup() attempt 1 failed.
InnoDB: Warning: io_setup() attempt 2 failed.
InnoDB: Warning: io_setup() attempt 3 failed.
InnoDB: Warning: io_setup() attempt 4 failed.
InnoDB: Warning: io_setup() attempt 5 failed.
130710 10:12:50  InnoDB: Error: io_setup() failed with EAGAIN after 5 attempts.
InnoDB: You can disable Linux Native AIO by setting innodb_use_native_aio = 0 in my.cnf
  InnoDB: Warning: Linux Native AIO disabled because os_aio_linux_create_io_ctx() failed. To get rid of this warning you can try increasing system fs.aio-max-nr to 1048576 or larger or setting innodb_use_native_aio = 0 in my.cnf
130710 10:12:50 InnoDB: Initializing buffer pool, size = 128.0M
130710 10:12:50 InnoDB: Completed initialization of buffer pool
130710 10:12:50 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 686643840
130710 10:12:50  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 686645510
130710 10:12:50  InnoDB: Error: page 1166 log sequence number 686664698
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 1051 log sequence number 686659258
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 58 log sequence number 686645929
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 60 log sequence number 686659678
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 63 log sequence number 686646348
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 560 log sequence number 686647460
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 203 log sequence number 686652381
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 205 log sequence number 686657221
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 588 log sequence number 686657221
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 208 log sequence number 686652804
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 211 log sequence number 686660928
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 402 log sequence number 686648288
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 542 log sequence number 686661772
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 225 log sequence number 686654072
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 545 log sequence number 686654072
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 227 log sequence number 686648753
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 230 log sequence number 686654495
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 546 log sequence number 686654495
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 233 log sequence number 686649176
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 235 log sequence number 686654902
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 248 log sequence number 686655748
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 1547 log sequence number 686655748
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 250 log sequence number 686657658
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 252 log sequence number 686656376
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 537 log sequence number 686662195
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 275 log sequence number 686662602
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 279 log sequence number 686651527
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 280 log sequence number 686663025
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 1569 log sequence number 686663448
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 297 log sequence number 686664294
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 591 log sequence number 686664294
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 299 log sequence number 686658418
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 538 log sequence number 686658418
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 38 130710 10:12:50  InnoDB: Error: page 2298 log sequence number 686663772
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
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
130710 10:12:50 Percona XtraDB (http://www.percona.com) 5.5.31-MariaDB-30.2 started; log sequence number 686645510
130710 10:12:50 [Note] Plugin 'FEEDBACK' is disabled.
130710 10:12:50  InnoDB: Error: page 998 log sequence number 686657235
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50  InnoDB: Error: page 1019 log sequence number 686647129
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 5.5.31-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466711 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x48000
??:0(??)[0x7f9f6b95703e]
??:0(??)[0x7f9f6b5a21dc]
??:0(??)[0x7f9f6acd7500]
??:0(??)[0x7f9f6b8c67e8]
??:0(??)[0x7f9f6b8c68f5]
??:0(??)[0x7f9f6b8c6b3c]
??:0(??)[0x7f9f6b80a4b7]
??:0(??)[0x7f9f6b80a52d]
??:0(??)[0x7f9f6b80eab6]
??:0(??)[0x7f9f6b7f5502]
??:0(??)[0x7f9f6b8f24a5]
??:0(??)[0x7f9f6b8390da]
??:0(??)[0x7f9f6b7e6507]
??:0(??)[0x7f9f6b8f25e6]
??:0(??)[0x7f9f6b8f3a0a]
??:0(??)[0x7f9f6b8e7867]
??:0(??)[0x7f9f6b807947]
??:0(??)[0x7f9f6b7fc32c]
??:0(??)[0x7f9f6accf851]
??:0(??)[0x7f9f6964390d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
130710 10:12:50 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended