Nie jesteś zalogowany.
Jeśli nie posiadasz konta, zarejestruj je już teraz! Pozwoli Ci ono w pełni korzystać z naszego serwisu. Spamerom dziękujemy!

Ogłoszenie

Prosimy o pomoc dla małej Julki — przekaż 1% podatku na Fundacji Dzieciom zdazyć z Pomocą.
Więcej informacji na dug.net.pl/pomagamy/.

#1  2012-01-14 16:54:05

  szewczyk - Stary wyjadacz :P

szewczyk
Stary wyjadacz :P
Zarejestrowany: 2006-12-03

Mysql 5.1 po upgrade nie wstaje :(

Z początku miałem mysql-5.0 ale pewnych opcji mi brakowało z mysql-5.1 więc postanowiłem wykonać upgrade z repo debiana squeeze
i instalacja przebiega tak:

Kod:

Czytanie list pakietów... Gotowe
Budowanie drzewa zależności
Odczyt informacji o stanie... Gotowe
Note, selecting 'mysql-server-5.1' instead of 'mysql-server-5.0'
mysql-server-5.1 jest już w najnowszej wersji.
0 aktualizowanych, 0 nowo instalowanych, 0 usuwanych i 0 nieaktualizowanych.
1 nie w pełni zainstalowanych lub usuniętych.
Po tej operacji zostanie dodatkowo użyte 0 B miejsca na dysku.
Kontynuować [T/n]? t
Konfigurowanie mysql-server-5.1 (5.1.49-3) ...
Stopping MySQL database server: mysqld.
Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: błąd przetwarzania mysql-server-5.1 (--configure):
 podproces zainstalowany skrypt post-installation zwrócił kod błędu 1
configured to not write apport reports
                                      Wystąpiły błędy podczas przetwarzania:
 mysql-server-5.1
E: Sub-process /usr/bin/dpkg returned an error code (1)

oraz mój syslog:

Kod:

Jan 14 16:50:50 localhost mysqld_safe[31612]: 120114 16:50:49 [ERROR] /usr/sbin/mysqld: unknown option '--skip-bdb'
Jan 14 16:50:50 localhost mysqld_safe[31612]: 120114 16:50:49 [ERROR] Aborting
Jan 14 16:50:50 localhost mysqld_safe[31612]:
Jan 14 16:50:50 localhost mysqld_safe[31612]: 120114 16:50:49 [Note] /usr/sbin/mysqld: Shutdown complete
Jan 14 16:50:50 localhost mysqld_safe[31612]:
Jan 14 16:50:50 localhost mysqld_safe[31612]:
Jan 14 16:50:50 localhost mysqld_safe[31612]: Installation of system tables failed!  Examine the logs in
Jan 14 16:50:50 localhost mysqld_safe[31612]: /var/lib/mysql for more information.
Jan 14 16:50:50 localhost mysqld_safe[31612]:
Jan 14 16:50:50 localhost mysqld_safe[31612]: You can try to start the mysqld daemon with:
Jan 14 16:50:50 localhost mysqld_safe[31612]:
Jan 14 16:50:50 localhost mysqld_safe[31612]:     shell> /usr/sbin/mysqld --skip-grant &
Jan 14 16:50:50 localhost mysqld_safe[31612]:
Jan 14 16:50:50 localhost mysqld_safe[31612]: and use the command line tool /usr/bin/mysql
Jan 14 16:50:50 localhost mysqld_safe[31612]: to connect to the mysql database and look at the grant tables:
Jan 14 16:50:50 localhost mysqld_safe[31612]:
Jan 14 16:50:50 localhost mysqld_safe[31612]:     shell> /usr/bin/mysql -u root mysql
Jan 14 16:50:50 localhost mysqld_safe[31612]:     mysql> show tables
Jan 14 16:50:50 localhost mysqld_safe[31612]:
Jan 14 16:50:50 localhost mysqld_safe[31612]: Try 'mysqld --help' if you have problems with paths.  Using --log
Jan 14 16:50:50 localhost mysqld_safe[31612]: gives you a log in /var/lib/mysql that may be helpful.
Jan 14 16:50:50 localhost mysqld_safe[31612]:
Jan 14 16:50:50 localhost mysqld_safe[31612]: Please consult the MySQL manual section
Jan 14 16:50:50 localhost mysqld_safe[31612]: 'Problems running mysql_install_db', and the manual section that
Jan 14 16:50:50 localhost mysqld_safe[31612]: describes problems on your OS.  Another information source are the
Jan 14 16:50:50 localhost mysqld_safe[31612]: MySQL email archives available at http://lists.mysql.com/.
Jan 14 16:50:50 localhost mysqld_safe[31612]:
Jan 14 16:50:50 localhost mysqld_safe[31612]: Please check all of the above before mailing us!  And remember, if
Jan 14 16:50:50 localhost mysqld_safe[31612]: you do mail us, you MUST use the /usr/scripts/mysqlbug script!
Jan 14 16:50:50 localhost mysqld_safe[31612]:
Jan 14 16:50:50 localhost mysqld_safe[31651]: 120114 16:50:50 [Note] Plugin 'FEDERATED' is disabled.
Jan 14 16:50:50 localhost mysqld_safe[31651]: 120114 16:50:50  InnoDB: Started; log sequence number 0 1553340028
Jan 14 16:50:50 localhost mysqld_safe[31651]: 120114 16:50:50 [ERROR] /usr/sbin/mysqld: unknown option '--skip-bdb'
Jan 14 16:50:50 localhost mysqld_safe[31651]: 120114 16:50:50 [ERROR] Aborting
Jan 14 16:50:50 localhost mysqld_safe[31651]:
Jan 14 16:50:50 localhost mysqld_safe[31651]: 120114 16:50:50  InnoDB: Starting shutdown...
Jan 14 16:50:55 localhost mysqld_safe[31651]: 120114 16:50:55  InnoDB: Shutdown completed; log sequence number 0 1553340028
Jan 14 16:50:55 localhost mysqld_safe[31651]: 120114 16:50:55 [Note] /usr/sbin/mysqld: Zako czenie dzia ania wykonane
Jan 14 16:50:55 localhost mysqld_safe[31651]:
Jan 14 16:50:55 localhost mysqld_safe[31670]: 120114 16:50:55 [Note] Plugin 'FEDERATED' is disabled.
Jan 14 16:50:55 localhost mysqld_safe[31670]: 120114 16:50:55  InnoDB: Started; log sequence number 0 1553340028
Jan 14 16:50:55 localhost mysqld_safe[31670]: 120114 16:50:55 [ERROR] /usr/sbin/mysqld: unknown option '--skip-bdb'
Jan 14 16:50:55 localhost mysqld_safe[31670]: 120114 16:50:55 [ERROR] Aborting
Jan 14 16:50:55 localhost mysqld_safe[31670]:
Jan 14 16:50:55 localhost mysqld_safe[31670]: 120114 16:50:55  InnoDB: Starting shutdown...
Jan 14 16:51:00 localhost mysqld_safe[31670]: 120114 16:51:00  InnoDB: Shutdown completed; log sequence number 0 1553340028
Jan 14 16:51:00 localhost mysqld_safe[31670]: 120114 16:51:00 [Note] /usr/sbin/mysqld: Zako czenie dzia ania wykonane
Jan 14 16:51:00 localhost mysqld_safe[31670]:
Jan 14 16:51:00 localhost mysqld_safe[31686]: 120114 16:51:00 [Note] Plugin 'FEDERATED' is disabled.
Jan 14 16:51:00 localhost mysqld_safe[31686]: 120114 16:51:00  InnoDB: Started; log sequence number 0 1553340028
Jan 14 16:51:00 localhost mysqld_safe[31686]: 120114 16:51:00 [ERROR] /usr/sbin/mysqld: unknown option '--skip-bdb'
Jan 14 16:51:00 localhost mysqld_safe[31686]: 120114 16:51:00 [ERROR] Aborting
Jan 14 16:51:00 localhost mysqld_safe[31686]:
Jan 14 16:51:00 localhost mysqld_safe[31686]: 120114 16:51:00  InnoDB: Starting shutdown...
Jan 14 16:51:05 localhost mysqld_safe[31686]: 120114 16:51:05  InnoDB: Shutdown completed; log sequence number 0 1553340028
Jan 14 16:51:05 localhost mysqld_safe[31686]: 120114 16:51:05 [Note] /usr/sbin/mysqld: Zako czenie dzia ania wykonane
Jan 14 16:51:05 localhost mysqld_safe[31686]:
Jan 14 16:51:05 localhost mysqld_safe[31701]: 120114 16:51:05 [Note] Plugin 'FEDERATED' is disabled.
Jan 14 16:51:06 localhost mysqld_safe[31701]: 120114 16:51:06  InnoDB: Started; log sequence number 0 1553340028
Jan 14 16:51:06 localhost mysqld_safe[31701]: 120114 16:51:06 [ERROR] /usr/sbin/mysqld: unknown option '--skip-bdb'
Jan 14 16:51:06 localhost mysqld_safe[31701]: 120114 16:51:06 [ERROR] Aborting
Jan 14 16:51:06 localhost mysqld_safe[31701]:
Jan 14 16:51:06 localhost mysqld_safe[31701]: 120114 16:51:06  InnoDB: Starting shutdown...
Jan 14 16:51:11 localhost mysqld_safe[31701]: 120114 16:51:11  InnoDB: Shutdown completed; log sequence number 0 1553340028
Jan 14 16:51:11 localhost mysqld_safe[31701]: 120114 16:51:11 [Note] /usr/sbin/mysqld: Zako czenie dzia ania wykonane
Jan 14 16:51:11 localhost mysqld_safe[31701]:
Jan 14 16:51:11 localhost mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Jan 14 16:51:11 localhost mysqld: 120114 16:51:11 [Note] Plugin 'FEDERATED' is disabled.
Jan 14 16:51:11 localhost mysqld: /usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist
Jan 14 16:51:11 localhost mysqld: 120114 16:51:11 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
Jan 14 16:51:11 localhost mysqld: 120114 16:51:11  InnoDB: Started; log sequence number 0 1553340028
Jan 14 16:51:11 localhost mysqld: 120114 16:51:11 [ERROR] /usr/sbin/mysqld: unknown option '--skip-bdb'
Jan 14 16:51:11 localhost mysqld: 120114 16:51:11 [ERROR] Aborting
Jan 14 16:51:11 localhost mysqld:
Jan 14 16:51:11 localhost mysqld: 120114 16:51:11  InnoDB: Starting shutdown...
Jan 14 16:51:16 localhost mysqld: 120114 16:51:16  InnoDB: Shutdown completed; log sequence number 0 1553340028
Jan 14 16:51:16 localhost mysqld: 120114 16:51:16 [Note] /usr/sbin/mysqld: Zako czenie dzia ania wykonane
Jan 14 16:51:16 localhost mysqld:
Jan 14 16:51:16 localhost mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
Jan 14 16:51:26 localhost /etc/init.d/mysql[32038]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Jan 14 16:51:26 localhost /etc/init.d/mysql[32038]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed
Jan 14 16:51:26 localhost /etc/init.d/mysql[32038]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Jan 14 16:51:26 localhost /etc/init.d/mysql[32038]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Jan 14 16:51:26 localhost /etc/init.d/mysql[32038]:

jak postawić go na nogi?
jak duże jest prawdopodobieństwo że bazy z poprzedniej wersji mysql są jeszcze?

Offline

 

#2  2012-01-14 17:44:07

  szewczyk - Stary wyjadacz :P

szewczyk
Stary wyjadacz :P
Zarejestrowany: 2006-12-03

Re: Mysql 5.1 po upgrade nie wstaje :(

Offline

 

Stopka forum

Powered by PunBB
© Copyright 2002–2005 Rickard Andersson
Nas ludzie lubią po prostu, a nie klikając w przyciski ;-)