+ Responder ao Tópico

  1. À todos,

    Após descomentar as linhas referente ao innoDB no arquivo my.cnf e salvá-lo, tento iniciar o Mysql-5.1.37 e recebo o seguinte erro:

    "Starting Mysql. ERROR! Manager of pid-file quit without updating file."

    Abaixo segue o arquivo my.cnf.

    # Example MySQL config file for medium systems.
    # This is for a system with little memory (32M - 64M) where MySQL plays
    # an important part, or systems up to 128M where MySQL is used together with
    # other programs (such as a web server)
    # You can copy this file to
    # /etc/my.cnf to set global options,
    # mysql-data-dir/my.cnf to set server-specific options (in this
    # installation this directory is /usr/local/mysql/var) or
    # ~/.my.cnf to set user-specific options.
    # In this file, you can use all long options that a program supports.
    # If you want to know which options a program supports, run the program
    # with the "--help" option.

    # The following options will be passed to all MySQL clients
    #password = your_password
    port = 3306
    socket = /tmp/mysql.sock
    #bind-address =

    # Here follows entries for some specific programs

    # The MySQL server
    port = 3306
    socket = /tmp/mysql.sock
    key_buffer_size = 16M
    max_allowed_packet = 1M
    table_open_cache = 64
    sort_buffer_size = 512K
    net_buffer_length = 8K
    read_buffer_size = 256K
    read_rnd_buffer_size = 512K
    myisam_sort_buffer_size = 8M

    # Don't listen on a TCP/IP port at all. This can be a security enhancement,
    # if all processes that need to connect to mysqld run on the same host.
    # All interaction with mysqld must be made via Unix sockets or named pipes.
    # Note that using this option without enabling named pipes on Windows
    # (via the "enable-named-pipe" option) will render mysqld useless!

    # Replication Master Server (default)
    # binary logging is required for replication

    # binary logging format - mixed recommended

    # required unique id between 1 and 2^32 - 1
    # defaults to 1 if master-host is not set
    # but will not function as a master if omitted
    server-id = 1

    # Replication Slave (comment out master section to use this)
    # To configure this host as a replication slave, you can choose between
    # two methods :
    # 1) Use the CHANGE MASTER TO command (fully described in our manual) -
    # the syntax is:
    # MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
    # where you replace <host>, <user>, <password> by quoted strings and
    # <port> by the master's port number (3306 by default).
    # Example:
    # CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
    # MASTER_USER='joe', MASTER_PASSWORD='secret';
    # OR
    # 2) Set the variables below. However, in case you choose this method, then
    # start replication for the first time (even unsuccessfully, for example
    # if you mistyped the password in master-password and the slave fails to
    # connect), the slave will create a master.info file, and any later
    # change in this file to the variables' values below will be ignored and
    # overridden by the content of the master.info file, unless you shutdown
    # the slave server, delete master.info and restart the slaver server.
    # For that reason, you may want to leave the lines below untouched
    # (commented) and instead use CHANGE MASTER TO (see above)
    # required unique id between 2 and 2^32 - 1
    # (and different from the master)
    # defaults to 2 if master-host is set
    # but will not function as a slave if omitted
    #server-id = 2
    # The replication master for this slave - required
    #master-host = <hostname>
    # The username the slave will use for authentication when connecting
    # to the master - required
    #master-user = <username>
    # The password the slave will authenticate with when connecting to
    # the master - required
    #master-password = <password>
    # The port the master is listening on.
    # optional - defaults to 3306
    #master-port = <port>
    # binary logging - not required for slaves, but recommended

    # Point the following paths to different dedicated disks
    #tmpdir = /tmp/
    #log-update = /path-to-dedicated-directory/hostname

    # Uncomment the following if you are using InnoDB tables
    innodb_data_home_dir = /usr/local/mysql/var/
    innodb_data_file_path = ibdata1:10M:autoextend
    innodb_log_group_home_dir = /usr/local/mysql/var/
    # You can set .._buffer_pool_size up to 50 - 80 %
    # of RAM but beware of setting memory usage too high
    innodb_buffer_pool_size = 16M
    innodb_additional_mem_pool_size = 2M
    # Set .._log_file_size to 25 % of buffer pool size
    innodb_log_file_size = 5M
    innodb_log_buffer_size = 8M
    innodb_flush_log_at_trx_commit = 1
    innodb_lock_wait_timeout = 50

    max_allowed_packet = 16M

    # Remove the next comment character if you are not familiar with SQL

    key_buffer_size = 20M
    sort_buffer_size = 20M
    read_buffer = 2M
    write_buffer = 2M



  2. Tente excluir o arquivo mysql pid em /var/run, mate todo o processo do mysql (comando killall ), tenha certeza que está definido com stick bit o tmp/ (ls-ld /tmp) e inicie o MySQL novamente. O que pode ajudar é dar uma olhada em /var/log para os logs de erro do mysql.

    Os caminhos dos diretórios podem variar de acordo com a distribuição.

    Pode ser que te ajude.


  3. A distro em que o mysql-5.1.37 estah instalado eh o Slackware 13.1.

    # /etc/my.cnf -> arquivo de configuracao
    # /usr/local/mysql -> diretorio padrao
    # /usr/local/mysql/var -> diretorio onde ficam os logs

    Abaixo segue o log de erro gerado apos ativar o innoDB.

    110405 11:48:18 mysqld_safe mysqld from pid file /usr/local/mysql/var/ibc102.pid ended
    110405 11:51:43 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
    110405 11:51:43 [ERROR] /usr/local/mysql/libexec/mysqld: unknown variable 'innodb_data_home_dir=/usr/local/mysql/var/'
    110405 11:51:43 [ERROR] Aborting

    110405 11:51:43 [Note] /usr/local/mysql/libexec/mysqld: Shutdown complete

    Pelo que entendi o diretorio jah estah criado (/usr/local/mysql/var), certo?


Tópicos Similares

  1. Problema ao tentar instalar o Mysql no Debian 7 multiarch
    Por Dervilkiller no fórum Sistemas Operacionais
    Respostas: 7
    Último Post: 23-09-2013, 07:20
  2. Problemas ao levantar Heartbeat no Conectiva 10
    Por Gilberto Russo no fórum Servidores de Rede
    Respostas: 1
    Último Post: 15-07-2004, 15:38
  3. Problema ao enviar mail no Mozilla 1.6
    Por vonlinkerstain no fórum Servidores de Rede
    Respostas: 0
    Último Post: 15-07-2004, 08:47
  4. Problemas ao abrir disquete no Linux
    Por no fórum Servidores de Rede
    Respostas: 1
    Último Post: 03-02-2004, 15:18
  5. Problemas ao conectar php com mysql
    Por Lili no fórum Servidores de Rede
    Respostas: 44
    Último Post: 12-11-2002, 09:19

Visite: BR-Linux ·  VivaOLinux ·  Dicas-L