[Linux-bruxelles] /usr/sbin/mysqld: Can't create/write to file '/tmpfs/...
Didier Misson
didier.linux at gmail.com
Jeu 30 Sep 18:44:24 CEST 2010
Hello,
J'ai un problème :
Serveur Debian Lenny, en théorie à jour.
Il a rebooté tout seul cet après-midi.
Je ne vois rien dans les logs ...
càd je vois le reboot, mais aucun message bizarre avant.
Depuis, j'ai des crasses sur tous les sites Drupal :
exemple :
http://culbutte.be/
http://babel-res.be/
Comme ça touche plusieurs sites, ce sont des DB différentes, des
dossiers différents, des installations Drupal séparées.
Le problème est que MySQL n'arrive pas à écrire dans /tmpfs !
euh ...
crash ? Segmentation fault ?
Sep 30 18:30:04 ks308166 mysqld[6686]: The manual page at
http://www.mysql.com/doc/en/Crashing.html contains
Sep 30 18:30:04 ks308166 mysqld[6686]: information that should help you
find out what is causing the crash.
Sep 30 18:30:04 ks308166 kernel: grsec: Segmentation fault occurred at
00000000000000f0 in /usr/sbin/mysqld[mysqld:6727] uid/euid:107/107
gid/egid:110/110, parent /usr/bin/mysqld_safe[mysqld_safe:3175]
uid/euid:0/0 gid/egid:0/0
Sep 30 18:30:04 ks308166 mysqld_safe[7307]: Number of processes running
now: 0
Sep 30 18:30:04 ks308166 mysqld_safe[7309]: restarted
Sep 30 18:30:04 ks308166 mysqld[7312]: #007/usr/sbin/mysqld: Can't
create/write to file '/tmpfs/ibjbxg6F' (Errcode: 13)
Sep 30 18:30:04 ks308166 mysqld[7312]: 100930 18:30:04 InnoDB: Error:
unable to create temporary file; errno: 13
Sep 30 18:30:04 ks308166 mysqld[7312]: 100930 18:30:04 [Note]
/usr/sbin/mysqld: ready for connections.
Sep 30 18:30:04 ks308166 mysqld[7312]: Version: '5.0.51a-24+lenny4-log'
socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
Sep 30 18:30:06 ks308166 mysqld[7312]: 100930 18:30:06 - mysqld got
signal 11;
Sep 30 18:30:06 ks308166 mysqld[7312]: This could be because you hit a
bug. It is also possible that this binary
Sep 30 18:30:06 ks308166 mysqld[7312]: or one of the libraries it was
linked against is corrupt, improperly built,
Sep 30 18:30:06 ks308166 mysqld[7312]: or misconfigured. This error can
also be caused by malfunctioning hardware.
Sep 30 18:30:06 ks308166 mysqld[7312]: We will try our best to scrape up
some info that will hopefully help diagnose
Sep 30 18:30:06 ks308166 mysqld[7312]: the problem, but since we have
already crashed, something is definitely wrong
Sep 30 18:30:06 ks308166 mysqld[7312]: and this may fail.
Sep 30 18:30:06 ks308166 mysqld[7312]:
Sep 30 18:30:06 ks308166 mysqld[7312]: key_buffer_size=1073741824
Sep 30 18:30:06 ks308166 mysqld[7312]: read_buffer_size=4190208
Sep 30 18:30:06 ks308166 mysqld[7312]: max_used_connections=1
Sep 30 18:30:06 ks308166 mysqld[7312]: max_connections=1000
Sep 30 18:30:06 ks308166 mysqld[7312]: threads_connected=1
Sep 30 18:30:06 ks308166 mysqld[7312]: It is possible that mysqld could
use up to
Sep 30 18:30:06 ks308166 mysqld[7312]: key_buffer_size +
(read_buffer_size + sort_buffer_size)*max_connections = 9236568 K
Sep 30 18:30:06 ks308166 mysqld[7312]: bytes of memory
Sep 30 18:30:06 ks308166 mysqld[7312]: Hope that's ok; if not, decrease
some variables in the equation.
Sep 30 18:30:06 ks308166 mysqld[7312]:
Sep 30 18:30:06 ks308166 mysqld[7312]: thd=0x25065a0
Sep 30 18:30:06 ks308166 mysqld[7312]: Attempting backtrace. You can use
the following information to find out
Sep 30 18:30:06 ks308166 mysqld[7312]: where mysqld died. If you see no
messages after this, something went
Sep 30 18:30:06 ks308166 mysqld[7312]: terribly wrong...
Sep 30 18:30:06 ks308166 mysqld[7312]: Cannot determine thread,
fp=0x25065a0, backtrace may not be correct.
Sep 30 18:30:06 ks308166 mysqld[7312]: Bogus stack limit or frame
pointer, fp=0x25065a0, stack_bottom=0x42010000, thread_stack=524288,
aborting backtrace.
Sep 30 18:30:06 ks308166 mysqld[7312]: Trying to get some variables.
Sep 30 18:30:06 ks308166 mysqld[7312]: Some pointers may be invalid and
cause the dump to abort..
===============================================================
dans kern.log :
Sep 30 18:16:14 ks308166 kernel: kjournald starting. Commit interval 5
seconds
Sep 30 18:16:14 ks308166 kernel: EXT3 FS on sda6, internal journal
Sep 30 18:16:14 ks308166 kernel: EXT3-fs: mounted filesystem with
writeback data mode.
Sep 30 18:16:14 ks308166 kernel: r8169: eth0: link up
Sep 30 18:16:14 ks308166 kernel: r8169: eth0: link up
Sep 30 18:16:15 ks308166 kernel: grsec: time set by
/usr/sbin/ntpdate[ntpdate:2870] uid/euid:0/0 gid/egid:0/0, parent
/etc/network/if-up.d/ntpdate[ntpdate:2866] uid/euid:0/0 gid/egid:0/0
Sep 30 18:16:19 ks308166 kernel: warning: `ntpd' uses 32-bit
capabilities (legacy support in use)
Sep 30 18:20:05 ks308166 kernel: grsec: Segmentation fault occurred at
00000000000000f0 in /usr/sbin/mysqld[mysqld:3218] uid/euid:107/107
gid/egid:110/110, parent /usr/bin/mysqld_safe[mysqld_safe:3175]
uid/euid:0/0 gid/egid:0/0
Sep 30 18:20:07 ks308166 kernel: grsec: Segmentation fault occurred at
00000000000000f0 in /usr/sbin/mysqld[mysqld:5999] uid/euid:107/107
gid/egid:110/110, parent /usr/bin/mysqld_safe[mysqld_safe:3175]
uid/euid:0/0 gid/egid:0/0
Sep 30 18:25:03 ks308166 kernel: grsec: Segmentation fault occurred at
00000000000000f0 in /usr/sbin/mysqld[mysqld:6409] uid/euid:107/107
gid/egid:110/110, parent /usr/bin/mysqld_safe[mysqld_safe:3175]
uid/euid:0/0 gid/egid:0/0
Sep 30 18:25:05 ks308166 kernel: grsec: Segmentation fault occurred at
00000000000000f0 in /usr/sbin/mysqld[mysqld:6673] uid/euid:107/107
gid/egid:110/110, parent /usr/bin/mysqld_safe[mysqld_safe:3175]
uid/euid:0/0 gid/egid:0/0
Sep 30 18:30:04 ks308166 kernel: grsec: Segmentation fault occurred at
00000000000000f0 in /usr/sbin/mysqld[mysqld:6727] uid/euid:107/107
gid/egid:110/110, parent /usr/bin/mysqld_safe[mysqld_safe:3175]
uid/euid:0/0 gid/egid:0/0
Sep 30 18:30:06 ks308166 kernel: grsec: Segmentation fault occurred at
00000000000000f0 in /usr/sbin/mysqld[mysqld:7357] uid/euid:107/107
gid/egid:110/110, parent /usr/bin/mysqld_safe[mysqld_safe:3175]
uid/euid:0/0 gid/egid:0/0
ça me semble euh... foireux !
Je pensais essayer de faire un fsck sur la partition /
...
Comment on monte en RO une partition / sur un serveur distant ? (OVH)
mais en voyant le Segmentation fault ... ça ne serait pas un problème
disque alors...
Des idées ?
Merci,
--
Didier
http://misson.tel Annuaire Misson
http://drupal.tel Annuaire Drupal
Plus d'informations sur la liste de diffusion Linux-bruxelles