17-02-2016, 04:26 PM
Tras copiar el archivo lo he ejecutado y ha generado un archivo de error cuyo contenido es
160217 16:22:08 InnoDB: Operating system error number 32 in a file operation.
InnoDB: The error means that another program is using InnoDB's files.
InnoDB: This might be a backup or antivirus software or another instance
InnoDB: of MySQL. Please close it to get rid of this error.
160217 16:22:18 InnoDB: Operating system error number 32 in a file operation.
InnoDB: The error means that another program is using InnoDB's files.
InnoDB: This might be a backup or antivirus software or another instance
InnoDB: of MySQL. Please close it to get rid of this error.
160217 16:22:28 InnoDB: Operating system error number 32 in a file operation.
InnoDB: The error means that another program is using InnoDB's files.
InnoDB: This might be a backup or antivirus software or another instance
InnoDB: of MySQL. Please close it to get rid of this error.
160217 16:22:38 InnoDB: Operating system error number 32 in a file operation.
InnoDB: The error means that another program is using InnoDB's files.
InnoDB: This might be a backup or antivirus software or another instance
InnoDB: of MySQL. Please close it to get rid of this error.
160217 16:22:48 InnoDB: Operating system error number 32 in a file operation.
InnoDB: The error means that another program is using InnoDB's files.
InnoDB: This might be a backup or antivirus software or another instance
InnoDB: of MySQL. Please close it to get rid of this error.
Da la impresión de que "tropieza" con una versión ya abierta de mysql, supongo que será porque arranca como un servicio o algo así, así que he eliminado la tarea de mysql existente y he repetido las instrucciones y ha generado el archivo de error siguiente
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160217 16:25:08 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...
160217 16:25:09 InnoDB: Started; log sequence number 31 3911254923
160217 16:25:09 [Note] mysqld-nt: ready for connections.
Version: '5.0.51b-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
¿Que hacemos ahora?
Gracias
160217 16:22:08 InnoDB: Operating system error number 32 in a file operation.
InnoDB: The error means that another program is using InnoDB's files.
InnoDB: This might be a backup or antivirus software or another instance
InnoDB: of MySQL. Please close it to get rid of this error.
160217 16:22:18 InnoDB: Operating system error number 32 in a file operation.
InnoDB: The error means that another program is using InnoDB's files.
InnoDB: This might be a backup or antivirus software or another instance
InnoDB: of MySQL. Please close it to get rid of this error.
160217 16:22:28 InnoDB: Operating system error number 32 in a file operation.
InnoDB: The error means that another program is using InnoDB's files.
InnoDB: This might be a backup or antivirus software or another instance
InnoDB: of MySQL. Please close it to get rid of this error.
160217 16:22:38 InnoDB: Operating system error number 32 in a file operation.
InnoDB: The error means that another program is using InnoDB's files.
InnoDB: This might be a backup or antivirus software or another instance
InnoDB: of MySQL. Please close it to get rid of this error.
160217 16:22:48 InnoDB: Operating system error number 32 in a file operation.
InnoDB: The error means that another program is using InnoDB's files.
InnoDB: This might be a backup or antivirus software or another instance
InnoDB: of MySQL. Please close it to get rid of this error.
Da la impresión de que "tropieza" con una versión ya abierta de mysql, supongo que será porque arranca como un servicio o algo así, así que he eliminado la tarea de mysql existente y he repetido las instrucciones y ha generado el archivo de error siguiente
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160217 16:25:08 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...
160217 16:25:09 InnoDB: Started; log sequence number 31 3911254923
160217 16:25:09 [Note] mysqld-nt: ready for connections.
Version: '5.0.51b-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
¿Que hacemos ahora?
Gracias
(17-02-2016, 03:54 PM)sysme escribió: Bueno pues ahí está el primer problema, es posible que si tienes un antivirus se lo haya cargado (no sería la primera vez, a los antivirus no les suelen gustar los .bat).
Te lo adjunto con la extensión .txt (para que el foro me permita adjuntarlo), copialo en la carpeta dicha y renombralo a .bat
Con esto debería arrancar, ya me dices.