Me recuerdas a alguien

Me recuerdas a alguien

a quien?!

En Flatpak ?

La app?

y en Snap ?

y en AppImagen ?

a quien?!

Un amigo que quiso hacer lo mismo

ajajajaja y le paso lo mismo por ( noob) jajajajaja como ami?!

jajajaja

En Flatpak ?

Snap y te lo compro :v

ajajajaja y le paso lo mismo por ( noob) jajajajaja como ami?!

Más o menos

Le interesa mucho seguridad de redes, quería comenzar con kali pero es un rollo la cosa del uefi

Le dije que esas herramientas las podía correr en otro Linux

Like Manjaro

con cualquier distro corre esas herramientas

si estan en algun repo

con cualquier distro corre esas herramientas

See

y en la de su distro pereferida

igual yo tenia w"#$os y instale kali en una particion lo utilizaba de ahi..

si bien soy amateur jugaba mucho en windows y esas cosas asi.....

pero al fin y al cabo me arte del otro y formate todo a la mierda e instale este manjaro.....

*harté

:v

sisis

con muda.

porque arte es otra cosa

:P

Dónde?

Dónde?

Me parece que llegaste un poco tarde

Jajaja

Me parece que llegaste un poco tarde

No importa, iré a jugar

No importa, iré a jugar

dichoso de vos

Una media hora

Me cancelaron una cita

Hola a todos, alguien sabe como se podria recuperar una bd mysql innodb con los archivos binarios (Estan intactos), Les comento mi dilema: Mi jefe iba a actualizar de mysql 5.5 a 5.6 en el vps pero por n razon se actualizo fue a mariadb 10.0 por eso las bd no las reconocia estamos intentando recuperarlas localmente en un server mysql 5.6 pero aun no encuentro la manera

Perdon mysql 5.5.49

Ok el archivo de la base de dato esta intacto. Era de MySQL

Ok el archivo de la base de dato esta intacto. Era de MySQL

Son aprox. 6 bd, pero sí estan intactos son de mysql 5.5

Y intentas recuperarlo pero como estas haciendo el proceso exactamente ?

creando una nueva instancia de mysql para recuperarlas tal cual este tuto: https://oscargascon.es/recuperar-bases-de-datos-desde-los-archivos-binarios-de-otra-instalacion-de-mysqlmariadb/ pero no me carga el my.conf

y en los logs solo me aparece que no se pudo cargar, ya miré permisos propietario grupo y todo esta bien

Lo más importante es que el servidor de MySQL debe ser la misma versión del que tenías

Si no te va a dar problemas

Debes instalar MySQL 5.5 no 5.5.49

Buena tarde para todos

Debes instalar MySQL 5.5 no 5.5.49

Pues ya revisé el mysql que estaba disponible en el vps y es la misma versión en ambos 5.5.49

Buena tarde para todos

Buenas tardes.

son los estables tanto de los repos de centOS (S.O del VPS y el ubuntu que estoy manejando)

Buena tarde para todos

Buenas tardes compa

Ok que error te lanza al cargar los .config?

Con van ?

Con van ?

Relativamente bien

Ok que error te lanza al cargar los .config?

Ya le digo un momento porfa

Una ves trate de recuperar una bd así y perdí dos horas de datos del servidor pero es menos que todos los datos

si, menos mal el lio es que los sistemas que manejan esas bd llevan casi 2 meses trabajando a medias y ya nos estan presionando

se alargo el log pero ya me dejo cargar el archivo

160714 14:13:48 mysqld_safe A mysqld process already exists 160714 14:13:57 mysqld_safe A mysqld process already exists 160714 14:15:33 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 160714 14:15:33 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead. 160714 14:15:33 [Note] /usr/sbin/mysqld (mysqld 5.5.49-0ubuntu0.14.04.1) starting as process 24259 ... 160714 14:15:33 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead. 160714 14:15:33 [Note] Plugin 'FEDERATED' is disabled. 160714 14:15:33 InnoDB: The InnoDB memory heap is disabled 160714 14:15:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins 160714 14:15:33 InnoDB: Compressed tables use zlib 1.2.8 160714 14:15:33 InnoDB: Using Linux native AIO 160714 14:15:33 InnoDB: Initializing buffer pool, size = 128.0M 160714 14:15:33 InnoDB: Completed initialization of buffer pool 160714 14:15:33 InnoDB: highest supported file format is Barracuda. 160714 14:15:33 InnoDB: Error: page 7 log sequence number 1594208 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 1 log sequence number 1592465 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 3 log sequence number 10675 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 2 log sequence number 885968 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 4 log sequence number 10675 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 11 log sequence number 1595668 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 5 log sequence number 1595685 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 6 log sequence number 39267 InnoDB: is in the future! Current system log sequence number 8204. 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.

160714 14:15:33 InnoDB: Error: page 45 log sequence number 1588999 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 301 log sequence number 1595675 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 46 log sequence number 71291 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 47 log sequence number 82466 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 48 log sequence number 93625 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 49 log sequence number 104800 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 50 log sequence number 115975 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 51 log sequence number 127150 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 52 log sequence number 138325 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 53 log sequence number 149484 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 54 log sequence number 160659 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 55 log sequence number 171834

InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 56 log sequence number 183009 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 57 log sequence number 194184 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 58 log sequence number 205359 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 59 log sequence number 216518 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 60 log sequence number 227693 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 61 log sequence number 238868 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 62 log sequence number 250043 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 63 log sequence number 261332 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 192 log sequence number 273682 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 193 log sequence number 285927 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 194 log sequence number 298172 InnoDB: is in the future! Current system log sequence number 8204.

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. 160714 14:15:33 InnoDB: Error: page 195 log sequence number 310417 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 196 log sequence number 322662 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 197 log sequence number 334907 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 198 log sequence number 347152 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 199 log sequence number 359381 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 200 log sequence number 371626 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 201 log sequence number 383871 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 202 log sequence number 396116 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 203 log sequence number 408361 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 204 log sequence number 420606 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 205 log sequence number 432851 InnoDB: is in the future! Current system log sequence number 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB

ERROR: S client not available

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. 160714 14:15:33 InnoDB: Error: page 206 log sequence number 445096 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 207 log sequence number 457341 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 208 log sequence number 469586 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 209 log sequence number 481831 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 210 log sequence number 494060 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 211 log sequence number 506305 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 212 log sequence number 518550 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 213 log sequence number 530795 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 214 log sequence number 543040 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 215 log sequence number 555285 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 216 log sequence number 567530 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 217 log sequence number 579775 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 218 log sequence number 592020 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 219 log sequence number 604265 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 220 log sequence number 616510 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 221 log sequence number 628755 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 222 log sequence number 640984 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 223 log sequence number 653229 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 224 log sequence number 665474 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 225 log sequence number 677719 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 226 log sequence number 689964 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 227 log sequence number 702209 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 228 log sequence number 714454 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 229 log sequence number 726699 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 230 log sequence number 738944 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 231 log sequence number 751189 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 232 log sequence number 763434 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 233 log sequence number 775663 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 234 log sequence number 787908 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 235 log sequence number 800153 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 236 log sequence number 812398 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 237 log sequence number 824643 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 238 log sequence number 836888 InnoDB: is in the future! Current system log sequence number 8204. 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.

160714 14:15:33 InnoDB: Error: page 239 log sequence number 849133 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 240 log sequence number 861378 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 241 log sequence number 873623 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 242 log sequence number 885968 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 244 log sequence number 899323 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 245 log sequence number 911620 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 246 log sequence number 923917 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 247 log sequence number 936214 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 248 log sequence number 948511 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 249 log sequence number 960808 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 250 log sequence number 973105 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 251 log sequence number 985402

InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 252 log sequence number 997699 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 253 log sequence number 1009996 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 254 log sequence number 1022293 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 255 log sequence number 1034701 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 256 log sequence number 1047122 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 257 log sequence number 1059426 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 258 log sequence number 1071723 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 259 log sequence number 1084020 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 260 log sequence number 1096317 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 261 log sequence number 1108614 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 262 log sequence number 1120911 InnoDB: is in the future! Current system log sequence number 8204.

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. 160714 14:15:33 InnoDB: Error: page 263 log sequence number 1133208 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 264 log sequence number 1145505 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 265 log sequence number 1157802 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 266 log sequence number 1170099 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 267 log sequence number 1182396 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 268 log sequence number 1194693 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 269 log sequence number 1206990 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 270 log sequence number 1219287 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 271 log sequence number 1231584 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 272 log sequence number 1243881 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 273 log sequence number 1256178 InnoDB: is in the future! Current system log sequence number 8204.

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. 160714 14:15:33 InnoDB: Error: page 274 log sequence number 1268475 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 275 log sequence number 1280772 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 276 log sequence number 1293069 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 277 log sequence number 1305366 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 278 log sequence number 1317663 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 279 log sequence number 1329960 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 280 log sequence number 1342257 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 281 log sequence number 1354554 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 282 log sequence number 1366851 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 283 log sequence number 1379148 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 284 log sequence number 1391445 InnoDB: is in the future! Current system log sequence number 8204.

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. 160714 14:15:33 InnoDB: Waiting for the background threads to start 160714 14:15:34 InnoDB: 5.5.49 started; log sequence number 8204 160714 14:15:34 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3307 160714 14:15:34 [Note] - '127.0.0.1' resolves to '127.0.0.1'; 160714 14:15:34 [Note] Server socket created on IP: '127.0.0.1'. 160714 14:15:34 [ERROR] Can't start server : Bind on unix socket: Permission denied 160714 14:15:34 [ERROR] Do you already have another mysqld server running on socket: /var/run/mysqld/mysqld2.sock ? 160714 14:15:34 [ERROR] Aborting 160714 14:15:34 InnoDB: Starting shutdown... 160714 14:15:35 InnoDB: Shutdown completed; log sequence number 8204 160714 14:15:35 [Note] /usr/sbin/mysqld: Shutdown complete 160714 14:15:35 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

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. 160714 14:15:33 InnoDB: Error: page 285 log sequence number 1403742 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 286 log sequence number 1416039 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 287 log sequence number 1428336 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 288 log sequence number 1440633 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 289 log sequence number 1452930 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 290 log sequence number 1465227 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 291 log sequence number 1477524 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 292 log sequence number 1489821 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 293 log sequence number 1502118 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 294 log sequence number 1514415 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 295 log sequence number 1526712 InnoDB: is in the future! Current system log sequence number 8204.

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. 160714 14:15:33 InnoDB: Error: page 296 log sequence number 1539009 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 297 log sequence number 1551306 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 298 log sequence number 1563603 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 299 log sequence number 1575900 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 300 log sequence number 1588197 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 0 log sequence number 1595668 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 8 log sequence number 1593788 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 10 log sequence number 1594198 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 12 log sequence number 1594468 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 303 log sequence number 1592308 InnoDB: is in the future! Current system log sequence number 8204. 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. 160714 14:15:33 InnoDB: Error: page 304 log sequence number 1593665 InnoDB: is in the future! Current system log sequence number 8204. InnoDB: Your database may be corrupt or you may have copied the InnoDB

Si ese error sólo te dice que puedes estar corrupto la base porque no coincide los números de log

Pero deberías poder ver la base de datos ya !

no me deja acceder a la nueva instancia de mysql o ejecutar el comando mysql_upgrade

Modifica los archivos de log para que coincida el número

esa parte si ni idea

Bienvenido

gracias

@JuaniGeekDroid ??

esa parte si ni idea

Lástima que. No esté en una pc para intentarlo y mostrarte estoy en la calle

me invito @Neo

esa parte si ni idea

No tengo una pc a la mano

Gente, tenemos un casi nuevo usuario de Manjaro

@NeoRanger

Bienvenido

Bienvenido compa

gracias johan

Gente, tenemos un casi nuevo usuario de Manjaro

Genial!!

Tenemos que ver si puede instalar Manjaro porque Ubuntu no le reconoce el dongle wifi que tiene

Esperemos que Manjaro si

estoy por probar Manjaro Gnome, vengo con mala experiencia en Ubuntu

Lástima que. No esté en una pc para intentarlo y mostrarte estoy en la calle

Tranquilo, por ahora seguire buscando si le queda un tiempo libre porfa le agradeceria si me puede ayudar un poco mas