mysql funktionierte bis anhin einwandfrei. Nun leitet ich via "dm_crypt" den Abschluss - verschlüsselung des /tmp Verzeichnis - ein, und dann meckerte Mysql.
Hier ein Auszug aus syslog:
Jan 11 19:33:22 sun mysqld_safe[4234]: started
Jan 11 19:33:22 sun mysqld[4237]: ^G/usr/sbin/mysqld: Can't read dir of '/tmp/' (Errcode: 13)
Jan 11 19:33:23 sun mysqld[4237]: ^G/usr/sbin/mysqld: Can't create/write to file '/tmp/ibNYhovc' (Errcode: 13)
Jan 11 19:33:23 sun mysqld[4237]: 060111 19:33:23 InnoDB: Error: unable to create temporary file; errno: 13
Jan 11 19:33:23 sun mysqld[4237]: 060111 19:33:23 [ERROR] Can't init databases
Jan 11 19:33:23 sun mysqld[4237]: 060111 19:33:23 [ERROR] Aborting
Jan 11 19:33:23 sun mysqld[4237]:
Jan 11 19:33:23 sun mysqld[4237]: 060111 19:33:23 [Note] /usr/sbin/mysqld: Shutdown complete
Jan 11 19:33:23 sun mysqld[4237]:
Jan 11 19:33:23 sun mysqld_safe[4239]: ended
Jan 11 19:33:24 sun kernel: eth0: no IPv6 routers present
Jan 11 19:33:28 sun /etc/init.d/mysql[4302]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Jan 11 19:33:28 sun /etc/init.d/mysql[4302]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed
Jan 11 19:33:28 sun /etc/init.d/mysql[4302]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)'
Jan 11 19:33:28 sun /etc/init.d/mysql[4302]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Die Schreibrechte wurden kontrolliert, nur der Socket??
.tmp verschlüsselung = Mysql error
sorry Savar, dies war die vorgeschichte " http://www.debianforum.de/wiki/?page=Cr ... t+dm_crypt " wo es um die "/tmp verschlüsselung" geht.
