Foros del Web » Programación para mayores de 30 ;) » Bases de Datos General » Mysql »

Problema al iniciar MySQL al cambiar motor almacenamiento

Estas en el tema de Problema al iniciar MySQL al cambiar motor almacenamiento en el foro de Mysql en Foros del Web. Hola a todos, tengo un problema que agradeceria me ayudarais a resolver, resulta que necesito que mi motor de almacenamiento sea InnoDB, por lo que ...
  #1 (permalink)  
Antiguo 28/02/2011, 15:18
Fecha de Ingreso: febrero-2011
Mensajes: 2
Antigüedad: 11 años, 5 meses
Puntos: 0
Problema al iniciar MySQL al cambiar motor almacenamiento

Hola a todos, tengo un problema que agradeceria me ayudarais a resolver, resulta que necesito que mi motor de almacenamiento sea InnoDB, por lo que en my.cnf le descomento la siguiente linea
y cuando hago
/etc/init.d/mysql restart
al parar bien, pero al iniciar, como que no, me pone failed!
si entro de nuevo a my.cnf y comento la susodicha linea, arranca sin problemas, en el archivo de configuracion pone que InnoDB esta por defecto, peroooo, cuando crea tablas las crea como MyISAM
al hacer
SHOW TABLE STATUS LIKE 'nombre_tabla' \G
en Engine me pone MyISAM

¿porque cuando cambio el motor de almacenamiento NO ME DEJA ARRANCAR NI RESETEAR MYSQL?????
Datos OP=Debian 6 stable server a base de pura consola
MySQL=5.1.49 3 (Debian)
para mas info pongo aqui mi my.cnf (modificado por mi, no es el que viene por defecto, seguro que aqui es donde he hecho algo mal... lo presiento, soy muy torpe )
# The MySQL database server configuration file.
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
# For explanations see

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
port		= 3306
socket		= /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
socket		= /var/run/mysqld/mysqld.sock
nice		= 0

# * Basic Settings
user		= mysql
pid-file	= /var/run/mysqld/
socket		= /var/run/mysqld/mysqld.sock
port		= 3306
basedir		= /usr
datadir		= /var/lib/mysql
tmpdir		= /tmp
language	= /usr/share/mysql/english

# The default storage engine that will be used when create new tables when

# Set the SQL mode to strict

# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.

# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.

# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]

# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.

# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before.  This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)

#*** MyISAM Specific options

# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method.  This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.

# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.

# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.

# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.

#*** INNODB Specific options ***

# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.

# Additional memory pool that is used by InnoDB to store metadata
# information.  If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS.  As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.

# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.

# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).

# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system.  Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.

# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.

# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.


!includedir /etc/mysql/conf.d/
Desde ya un saludo, esperando respuestas y gracias.
  #2 (permalink)  
Antiguo 01/03/2011, 14:54
Fecha de Ingreso: febrero-2011
Mensajes: 2
Antigüedad: 11 años, 5 meses
Puntos: 0
Respuesta: Problema al iniciar MySQL al cambiar motor almacenamiento

ya he descubierto porque, pero me genera mas dudas, eesta linea:
es la causante de todo, no me inicia mysql, y he probado con muchos valos, desde 1M hasta 3000M, simplemente si esta linea esta sin comentar, Mysql no reinicia
Asi funciona sin problemas, alguien sabria explicarme porque?, significa que no podre asignar un valor a los logs de Inoodb? o que pasa? (raro verda?)
Saludos y gracias.

Etiquetas: almacenamiento, iniciar, motor
Atención: Estás leyendo un tema que no tiene actividad desde hace más de 6 MESES, te recomendamos abrir un Nuevo tema en lugar de responder al actual.

La zona horaria es GMT -6. Ahora son las 21:43.