Em Ter, 2007-05-15 às 17:20 -0300, Davi escreveu: > Não. > > /etc/init.d/mysql start > > é uma coisa. > > cd /etc/init.d/; mysql start > > é outra... *Completamente* diferente.
obs.: o "apontado anteriormente" refere-se ao e-mail enviado que começou a thread e não ao comando imediatamente acima da resposta. > > Dá uma olhada em: > > /var/log/messages > /var/log/daemon Nada de bom... > > Se não achar nada interessante: > > grep "mysql" /var/log/* Iiiixii... Resultado abaixo: /var/log/daemon.log:May 14 16:51:27 localhost mysqld_safe[4247]: started /var/log/daemon.log:May 14 16:51:27 localhost mysqld[4250]: 070514 16:51:27 InnoDB: Started; log sequence number 0 43675 /var/log/daemon.log:May 14 16:51:27 localhost mysqld[4250]: 070514 16:51:27 [Note] /usr/sbin/mysqld: ready for connections. /var/log/daemon.log:May 14 16:51:27 localhost mysqld[4250]: Version: '5.0.32-Debian_7etch1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian etch distribution /var/log/daemon.log:May 14 16:51:28 localhost /etc/mysql/debian-start[4285]: Upgrading MySQL tables if necessary. /var/log/daemon.log:May 14 16:51:31 localhost /etc/mysql/debian-start[4303]: Checking for crashed MySQL tables. /var/log/daemon.log:May 14 17:08:37 localhost mysqld_safe[6362]: PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! /var/log/daemon.log:May 14 17:08:37 localhost mysqld_safe[6362]: To do so, start the server, then issue the following commands: /var/log/daemon.log:May 14 17:08:37 localhost mysqld_safe[6362]: /usr/bin/mysqladmin -u root password 'new-password' /var/log/daemon.log:May 14 17:08:37 localhost mysqld_safe[6362]: /usr/bin/mysqladmin -u root -h ledfis password 'new-password' /var/log/daemon.log:May 14 17:08:37 localhost mysqld_safe[6362]: See the manual for more instructions. /var/log/daemon.log:May 14 17:08:37 localhost mysqld_safe[6362]: /var/log/daemon.log:May 14 17:08:37 localhost mysqld_safe[6362]: NOTE: If you are upgrading from a MySQL <= 3.22.10 you should run /var/log/daemon.log:May 14 17:08:37 localhost mysqld_safe[6362]: the /usr/bin/mysql_fix_privilege_tables. Otherwise you will not be /var/log/daemon.log:May 14 17:08:37 localhost mysqld_safe[6362]: able to use the new GRANT command! /var/log/daemon.log:May 14 17:08:37 localhost mysqld_safe[6362]: /var/log/daemon.log:May 14 17:08:37 localhost mysqld_safe[6362]: Please report any problems with the /usr/bin/mysqlbug script! /var/log/daemon.log:May 14 17:08:37 localhost mysqld_safe[6362]: /var/log/daemon.log:May 14 17:08:37 localhost mysqld_safe[6362]: The latest information about MySQL is available on the web at /var/log/daemon.log:May 14 17:08:37 localhost mysqld_safe[6362]: http://www.mysql.com /var/log/daemon.log:May 14 17:08:37 localhost mysqld_safe[6362]: Support MySQL by buying support/licenses at http://shop.mysql.com /var/log/daemon.log:May 14 17:08:43 localhost mysqld_safe[6517]: started /var/log/daemon.log:May 14 17:08:43 localhost mysqld[6520]: InnoDB: e vai... /var/log/syslog.0:May 15 17:37:46 localhost mysqld[6461]: InnoDB: Check that you do not already have another mysqld process /var/log/syslog.0:May 15 17:37:46 localhost mysqld[6461]: InnoDB: using the same InnoDB data or log files. /var/log/syslog.0:May 15 17:37:46 localhost mysqld[6461]: 070515 17:37:46 InnoDB: Unable to open the first data file /var/log/syslog.0:May 15 17:37:46 localhost mysqld[6461]: InnoDB: Error in opening ./ibdata1 /var/log/syslog.0:May 15 17:37:46 localhost mysqld[6461]: 070515 17:37:46 InnoDB: Operating system error number 11 in a file operation. /var/log/syslog.0:May 15 17:37:46 localhost mysqld[6461]: InnoDB: Error number 11 means 'Resource temporarily unavailable'. /var/log/syslog.0:May 15 17:37:46 localhost mysqld[6461]: InnoDB: Some operating system error numbers are described at /var/log/syslog.0:May 15 17:37:46 localhost mysqld[6461]: InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html /var/log/syslog.0:May 15 17:37:46 localhost mysqld[6461]: InnoDB: Could not open or create data files. /var/log/syslog.0:May 15 17:37:46 localhost mysqld[6461]: InnoDB: If you tried to add new data files, and it failed here, /var/log/syslog.0:May 15 17:37:46 localhost mysqld[6461]: InnoDB: you should now edit innodb_data_file_path in my.cnf back /var/log/syslog.0:May 15 17:37:46 localhost mysqld[6461]: InnoDB: to what it was, and remove the new ibdata files InnoDB created /var/log/syslog.0:May 15 17:37:46 localhost mysqld[6461]: InnoDB: in this failed attempt. InnoDB only wrote those files full of /var/log/syslog.0:May 15 17:37:46 localhost mysqld[6461]: InnoDB: zeros, but did not yet use them in any way. But be careful: do not /var/log/syslog.0:May 15 17:37:46 localhost mysqld[6461]: InnoDB: remove old data files which contain your precious data! /var/log/syslog.0:May 15 17:37:47 localhost mysqld[6461]: 070515 17:37:47 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use /var/log/syslog.0:May 15 17:37:47 localhost mysqld[6461]: 070515 17:37:47 [ERROR] Do you already have another mysqld server running on port: 3306 ? /var/log/syslog.0:May 15 17:37:47 localhost mysqld[6461]: 070515 17:37:47 [ERROR] Aborting /var/log/syslog.0:May 15 17:37:47 localhost mysqld[6461]: /var/log/syslog.0:May 15 17:37:47 localhost mysqld[6461]: 070515 17:37:47 [Note] /usr/sbin/mysqld: Shutdown complete /var/log/syslog.0:May 15 17:37:47 localhost mysqld[6461]: /var/log/syslog.0:May 15 17:37:47 localhost mysqld_safe[6688]: ended Acho que vou começar do zero... Obrigado pelas informações. Abraço. Marcelo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
