Impossible d'installer mySQL

Fermé
Utilisateur anonyme - 28 mai 2012 à 15:13
mamiemando Messages postés 33401 Date d'inscription jeudi 12 mai 2005 Statut Modérateur Dernière intervention 28 novembre 2024 - 28 mai 2012 à 23:01
Bonjour,

J'ai voulu installer mysql server sur une machine Debian 6.0 32 bits; je tape donc la commande:
apt-get install mysql-server

On me demande mon mot de passe, je le saisis, puis une autre fois.
tout ce passe bien quand soudain...

????????????????????? Configuration de mysql-server-5.1 ?????????????????????
? ?
? Unable to set password for the MySQL "root" user ?
? ?
? An error occurred while setting the password for the MySQL ?
? administrative user. This may have happened because the account already ?
? has a password, or because of a communication problem with the MySQL ?
? server. ?
? ?
? You should check the account's password after the package installation. ?
? ?
? Please read the /usr/share/doc/mysql-server-5.1/README.Debian file for ?
? more information. ?
? ?
? <Ok> ?
? ?
????????????????????????????????????????????????????????????????????????


voici ce qu'il y a d'écrit dans la console Linux
;InnoDB: End of page dump


120528 1:48:54 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
120528 1:48:54InnoDB: Error: trying to access a stray pointer 0x34593ff8
InnoDB: buf pool start is at 0xb4584000, end at 0xb4d84000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: https://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: how to force recovery.
120528 1:48:54 InnoDB: Assertion failure in thread 3077854928 in file ../../.. /storage/innobase/include/buf0buf.ic line 264
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://bugs.mysql.com/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: https://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
01:48:54 UTC - mysqld got signal 6 ;
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_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 345933 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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...
stack_bottom = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2d) [0xc0a20d]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4) [0x9ef104]
[0x12d500]
/lib/libc.so.6(abort+0x182) [0x327922]
/usr/sbin/mysqld(page_cur_search_with_match+0x9a3) [0xb27c03]
/usr/sbin/mysqld(btr_cur_search_to_nth_level+0x5ae) [0xabf4ce]
/usr/sbin/mysqld(btr_pcur_open_on_user_rec+0x73) [0xb88be3]
/usr/sbin/mysqld(+0x4868c5) [0xade8c5]
/usr/sbin/mysqld(dict_load_sys_table+0x75) [0xae51a5]
/usr/sbin/mysqld(dict_boot+0xd27) [0xb8a497]
/usr/sbin/mysqld(innobase_start_or_create_for_mysql+0x13f4) [0xb60804]
/usr/sbin/mysqld(+0x454c66) [0xaacc66]
/usr/sbin/mysqld(ha_initialize_handlerton(st_plugin_int*)+0x3f) [0x9dd59f]
/usr/sbin/mysqld(+0x42721f) [0xa7f21f]
/usr/sbin/mysqld(plugin_init(int*, char**, int)+0x89f) [0xa82c2f]
/usr/sbin/mysqld(+0x276f82) [0x8cef82]
/usr/sbin/mysqld(main+0x212) [0x8d3962]
/lib/libc.so.6(__libc_start_main+0xe6) [0x310c76]
/usr/sbin/mysqld(+0x18f651) [0x7e7651]
The manual page at https://dev.mysql.com/doc/refman/8.0/en/crashing.html contains
information that should help you find out what is causing the crash.
Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing mysql-server-5.1 (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of mysql-server:
mysql-server depends on mysql-server-5.1; however:
Package mysql-server-5.1 is not configured yet.
dpkg: error processing mysql-server (--configure):
dependency problems - leaving unconfigured
configured to not write apport reports
configured to not write apport reports
Errors were encountered while processing:
mysql-server-5.1
mysql-server


J'ai même fait un dpkg --configure mysql-server-5.1
Setting up mysql-server-5.1 (5.1.61-0+squeeze1) ...
Stopping MySQL database server: mysqld.
Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing mysql-server-5.1 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 mysql-server-5.1


Merci d'avance de m'aiguiller car ça fait plusieurs heures que je galère là dessus...

Cordialement
A voir également:

1 réponse

mamiemando Messages postés 33401 Date d'inscription jeudi 12 mai 2005 Statut Modérateur Dernière intervention 28 novembre 2024 7 804
28 mai 2012 à 23:01
Commence par tout mettre à jour. En root :

aptitude update
aptitude safe-upgrade


Ensuite purge ton installation actuelle mysql. Il te demandera peut être ce qu'il doit faire de /var/lib/mysql (les données stockées en base), à toi de voir, sachant que les mots de passe mysql sont stockés dedans (ou plus proprement, fais un backup de ces bases avec la commande mysqldump). Si tu n'as pas de données importantes, défais la base.
http://dev.mysql.com/doc/refman/5.0/fr/mysqldump.html?iframe=true&width=100%&height=100%
https://www.netadmintools.com/art408.html

Dans le doute je te conseille copier ce fichier, puis de purger :

service mysql stop
cp -r /var/lib/mysql /var/lib/mysql.bak
aptitude purge mysql-server


Vérifie qu'il ne reste rien du serveur, sinon purge les paquets restants :

dpkg -l | grep mysql


Ensuite tente de réinstaller mysql :

aptitude install mysql-server


Si tu as toujours la même erreur, purge à nouveau mysql-server et supprime /var/lib/mysql, puis réinstalle-le :

aptitude purge mysql-server
rm -rf /var/lib/mysql
aptitude install mysql-server


Bonne chance
0