According to the daemon.log file: Sep 3 22:40:10 test mysqld_safe[6037]: Number of processes running now: 1 Sep 3 22:40:10 test mysqld_safe[6045]: mysqld process hanging, pid 2586 - killed Sep 3 22:40:10 test mysqld_safe[6048]: restarted Sep 3 22:40:10 test mysqld[6051]: 090903 22:40:10 InnoDB: Started; log sequence number 0 43655 Sep 3 22:40:10 test mysqld[6051]: 090903 22:40:10 [Note] /usr/sbin/mysqld: ready for connections. Sep 3 22:40:10 test mysqld[6051]: Version: '5.0.75-0ubuntu10' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Sep 3 22:40:11 test /etc/init.d/mysql[6075]: 1 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in Sep 3 22:40:11 test /etc/init.d/mysql[6075]: mysqld is alive Sep 3 22:40:11 test /etc/init.d/mysql[6075]: Sep 3 22:40:14 test NetworkManager: <info> HAL disappeared Sep 3 22:40:17 test acpid: client connected from 6389[114:124] Sep 3 22:40:17 test NetworkManager: <info> HAL re-appeared Sep 3 22:40:17 test NetworkManager: <info> (ttyS0): ignoring due to lack of mobile broadband capabilties Sep 3 22:41:50 test mysqld[6051]: 090903 22:41:50 [Note] /usr/sbin/mysqld: Normal shutdown Sep 3 22:41:50 test mysqld[6051]: Sep 3 22:41:50 test mysqld[6051]: 090903 22:41:50 InnoDB: Starting shutdown... Sep 3 22:41:50 test mysqld[6051]: 090903 22:41:50 InnoDB: Shutdown completed; log sequence number 0 43655 Sep 3 22:41:50 test mysqld[6051]: 090903 22:41:50 [Note] /usr/sbin/mysqld: Shutdown complete Sep 3 22:41:50 test mysqld[6051]: Sep 3 22:41:50 test mysqld_safe[13296]: ended
************** Mysql was successfully stopped. Sep 3 22:42:17 test acpid: exiting Sep 3 22:42:23 test dbus-daemon: Reloaded configuration Sep 3 22:42:28 test NetworkManager: <info> HAL disappeared Sep 3 22:42:28 test dbus-daemon: Reloaded configuration Sep 3 22:42:45 test jsvc.exec[3437]: 3-set-2009 22.42.45 org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8080 Sep 3 22:42:46 test jsvc.exec[3437]: 3-set-2009 22.42.46 org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Sep 3 22:42:46 test jsvc.exec[3437]: 3-set-2009 22.42.46 org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080 Sep 3 22:43:00 test mysqld_safe[16099]: PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! Sep 3 22:43:00 test mysqld_safe[16099]: To do so, start the server, then issue the following commands: Sep 3 22:43:00 test mysqld_safe[16099]: /usr/bin/mysqladmin -u root password 'new-password' Sep 3 22:43:00 test mysqld_safe[16099]: /usr/bin/mysqladmin -u root -h test password 'new-password' Sep 3 22:43:00 test mysqld_safe[16099]: Sep 3 22:43:00 test mysqld_safe[16099]: Alternatively you can run: Sep 3 22:43:00 test mysqld_safe[16099]: /usr/bin/mysql_secure_installation Sep 3 22:43:00 test mysqld_safe[16099]: Sep 3 22:43:00 test mysqld_safe[16099]: which will also give you the option of removing the test Sep 3 22:43:00 test mysqld_safe[16099]: databases and anonymous user created by default. This is Sep 3 22:43:00 test mysqld_safe[16099]: strongly recommended for production servers. Sep 3 22:43:00 test mysqld_safe[16099]: Sep 3 22:43:00 test mysqld_safe[16099]: See the manual for more instructions. Sep 3 22:43:00 test mysqld_safe[16099]: Sep 3 22:43:00 test mysqld_safe[16099]: Please report any problems with the /usr/bin/mysqlbug script! Sep 3 22:43:00 test mysqld_safe[16099]: Sep 3 22:43:00 test mysqld_safe[16099]: The latest information about MySQL is available on the web at Sep 3 22:43:00 test mysqld_safe[16099]: http://www.mysql.com Sep 3 22:43:00 test mysqld_safe[16099]: Support MySQL by buying support/licenses at http://shop.mysql.com Sep 3 22:43:00 test mysqld_safe[16169]: ERROR: 1046 No database selected Sep 3 22:43:00 test mysqld_safe[16169]: 090903 22:43:00 [ERROR] Aborting Sep 3 22:43:00 test mysqld_safe[16169]: Sep 3 22:43:00 test mysqld_safe[16169]: 090903 22:43:00 [Note] /usr/sbin/mysqld: Shutdown complete Sep 3 22:43:00 test mysqld_safe[16169]: Sep 3 22:43:01 test mysqld_safe[16357]: started Sep 3 22:43:01 test mysqld[16360]: 090903 22:43:01 InnoDB: Started; log sequence number 0 43655 Sep 3 22:43:01 test mysqld[16360]: 090903 22:43:01 [Note] /usr/sbin/mysqld: ready for connections. Sep 3 22:43:01 test mysqld[16360]: Version: '5.0.75-0ubuntu10.2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) ********************** mysqld was successfully started. Sep 3 22:43:02 test /etc/mysql/debian-start[16398]: Upgrading MySQL tables if necessary. Sep 3 22:43:02 test /etc/mysql/debian-start[16409]: Looking for 'mysql' as: /usr/bin/mysql Sep 3 22:43:02 test /etc/mysql/debian-start[16409]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Sep 3 22:43:02 test /etc/mysql/debian-start[16409]: This installation of MySQL is already upgraded to 5.0.75, use --force if you still need to run mysql_upgrade Sep 3 22:43:02 test /etc/mysql/debian-start[16413]: Checking for insecure root accounts. Sep 3 22:43:02 test /etc/mysql/debian-start[16417]: Triggering myisam-recover for all MyISAM tables And subsequent logs show that mysqld is running properly. Could you confirm that mysqld is running properly now? -- package mysql-server 5.1.30really5.0.75-0ubuntu10.2 failed to install/upgrade: il sottoprocesso pre-installation script ha restituito un codice di errore 1 https://bugs.launchpad.net/bugs/423996 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
