Conforme eu já havia dito, estou mandando alguns logs e resultados
que rodei aqui:
# dpkg -l | grep mysql
ii libdbd-mysql-p 2.9006-1 A Perl5 database interface to the MySQL data
ii libmysqlclient 4.0.24-10sarge mysql database client library
ii mysql-client 4.0.24-10sarge mysql database client binaries
ii mysql-common 4.0.24-10sarge mysql database common files (e.g. /etc/mysql
ii mysql-server 4.0.24-10sarge mysql database server binaries
# /etc/init.d/mysql start
Starting MySQL database server: mysqld...failed.
Please take a look at the syslog.
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (111)'
Check that mysqld is running and that the socket:
'/var/run/mysqld/mysqld.sock' exists!
# mysqld
InnoDB: Error: auto-extending data file ./ibdata1 is of a different size
InnoDB: 0 pages (rounded down to MB) than specified in the .cnf file:
InnoDB: initial 640 pages, max 0 (relevant if non-zero) pages!
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
070417 12:59:48 Can't init databases
070417 12:59:48 Aborting
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.
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.
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_connections = 233983 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x842a638
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...
Cannot determine thread, fp=0x4261b7d8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x810e48b
0x40037af8
(nil)
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html
and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x676f6c6e is invalid pointer
thd->thread_id=138587896
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
# rm /var/lib/mysql/ibdata1 ; mysqld
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
070417 13:00:41 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
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.
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.
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_connections = 233983 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x842a638
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...
Cannot determine thread, fp=0x4261b7d8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x810e48b
0x40037af8
(nil)
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html
and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x676f6c6e is invalid pointer
thd->thread_id=138587896
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
E ae? alguém já viu algo parecido?
Fabio.
On 4/17/07, Fabio A Mazzarino <[EMAIL PROTECTED]> wrote:
Oéslei:
eu removi tudo, na verdade fiz uma instalação completamente nova,
tentando instalar somente o pacote mysql-server (nada de 4.1 ou 5.0).
Ainda assim o problema persiste.
Vou pegar alguns logs e manda na lista pra vcs verem.
Fabio.
On 4/16/07, oeslei taborda ribas <[EMAIL PROTECTED]> wrote:
> Olá.
>
> O problema provavelmente deve estar sendo ocasionado porque vocês está
> rodando duas versões
> do mysql ao mesmo tempo:
> **mysql-server-4.1
> **mysql-server-5.0
> Ai vai dar problemas mesmo porque quando tentar startar vai dar conflito,
> desistale as duas versões e instale de
> novo! ou a 4.1 ou a 5.0 lembrando que o sarge só possui a 4.1 a 5.0 é só no
> etch ou via backport's
>
> At+
> Oéslei
>
> Em 16/04/07, Fabio A Mazzarino <[EMAIL PROTECTED]> escreveu:
> > Pessoal:
> >
> > Depois de instalar o mysql encontrei o seguinte problema:
> >
> >
> > Starting MySQL database server: mysqld...failed.
> > Please take a look at the syslog.
> > /usr/bin/mysqladmin: connect to server at 'localhost' failed
> > error: 'Can't connect to local MySQL server through socket
> > '/var/run/mysqld/mysqld.sock' (111)'
> > Check that mysqld is running and that the socket:
> > '/var/run/mysqld/mysqld.sock' exists!
> >
> >
> > E mesmo depois de instalado com erro, o erro continua
> >
> > # /etc/init.d/mysql start
> > Starting MySQL database server: mysqld...failed.
> > Please take a look at the syslog.
> > /usr/bin/mysqladmin: connect to server at 'localhost' failed
> > error: 'Can't connect to local MySQL server through socket
> > '/var/run/mysqld/mysqld.sock' (111)'
> > Check that mysqld is running and that the socket:
> > '/var/run/mysqld/mysqld.sock' exists!
> >
> > Não mechi em nada, só mandei instalar direto. A instalação é padrão
> > (3.1r4 - sarge), eu só instalei php5, que instalou o apache2
> > automaticamente, não houveram problemas, além disso eu tb instalei o
> > openssh-server, que tb está funcionando sem problemas.
> >
> > Acho que deu pra perceber que eu tô querendo instalar um servidor
> > LAMP, só que o MySQL não tá indo.
> >
> > Ah, só pra constar, o erro aconteceu com os pacotes:
> > . mysql-server
> > . mysql-server-4.1
> > . mysql-server-5.0
> >
> > o sources.list é este:
> >
> > deb http://mirrors.kernel.org/debian/ sarge main
> > deb-src http://mirrors.kernel.org/debian/ sarge main
> >
> > deb http://security.debian.org/ sarge/updates main
> >
> > deb http://ftp.us.debian.org/debian/ sarge main
> > deb-src http://ftp.us.debian.org/debian/ sarge main
> >
> > Alguém já encontrou algum problema.
> >
> > Ah, não tenho medo de instalar a partir dos fontes, só preciso saber
> > como que o apt lida com isso, se eu não me engano é preciso puxar os
> > fontes pelo apt, mas não sei o procedimento todo.
> >
> > Aguardo resposta ;o)
> >
> > Fabio
> >
> >
> >
> > --
> > Doses Diárias - Achados de um Programador na Internet
> > http://dosesdiarias.seucaminho.com
> >
> >
>
>
--
Doses Diárias - Achados de um Programador na Internet
http://dosesdiarias.seucaminho.com
--
Doses Diárias - Achados de um Programador na Internet
http://dosesdiarias.seucaminho.com
