[Maria-developers] mariadb-server not installable on Debian Testing AMD64
SEND-PR: -*- send-pr -*-
SEND-PR: Lines starting with `SEND-PR' will be removed automatically, as
SEND-PR: will all comments (text enclosed in `<' and `>').
SEND-PR:
From: thackert@nexgo.de
To: maria-developers@lists.launchpad.net
Subject: mariadb-server not installable on Debian Testing AMD64
>Description:
Hello @ll,
this is my first try to report a bug with mysqlbug. If I missed
something and/or have something wrong, feel free to ask, but do not
condemn me ... ;)
I have tried to install mariadb-server on Debian Testing AMD64. I got
the error message
<quote>
<snip>
[ ok ] Stopping MariaDB database server: mysqld.
130130 17:28:50 [Note] Plugin 'InnoDB' is disabled.
130130 17:28:50 [Note] Plugin 'FEEDBACK' is disabled.
[....] Starting MariaDB database server: mysqld . . . . . . . . . . . .
. . . . . . . . FAIL . . . . . . . failed!
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: Fehler beim Bearbeiten von mariadb-server-10.0 (--configure):
Unterprozess installiertes post-installation-Skript gab den Fehlerwert
1 zurück
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von mariadb-server:
mariadb-server hängt ab von mariadb-server-10.0; aber:
Paket mariadb-server-10.0 ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten von mariadb-server (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
Trigger für menu werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
mariadb-server-10.0
mariadb-server
</quote>
... :( I get the same message, if I try to install mysql-server from
Debian's repository ... :(
>How-To-Repeat:
1. Add " # MariaDB 10.0 repository list - created 2013-01-30 16:20 UTC
# http://mariadb.org/mariadb/repositories/deb
# http://mirror.netcologne.de/mariadb//repo/10.0/debian wheezy main
deb-src http://mirror.netcologne.de/mariadb//repo/10.0/debian wheezy
main" to your /etc/apt/sources.list.
2. Run "apt-get update"
3. Run "apt-get install mariadb-server"
The error message appears nearly at the end of the installation ... :(
>Fix:
I do not know, sorry ... :( But maybe it is possible to check first, if
mysql- or mariadb-server was installed before, and if it was, stop it.
If it was not installed before, than it should not try to stop the
server ... ;)
>Submitter-Id: <submitter ID>
>Originator: Thomas Hackert
>Organization: <none>
>MySQL support: [none | licence | email support | extended email support
>]
>Synopsis: mariadb-server not installable on Debian Testing AMD64
>Severity: serious
>Priority: medium
>Category: mysql
>Class: <[ sw-bug | doc-bug | change-request | support ] (one
>line)>
>Release: mysql-10.0.0-mariadb1~wheezy (mariadb.org binary
>distribution)
>C compiler: gcc-4.7.real (Debian 4.7.1-2) 4.7.1
>C++ compiler: g++-4.7.real (Debian 4.7.1-2) 4.7.1
>Environment:
<machine, os, target, libraries (multiple lines)>
System: Linux neo 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux
Some paths: /usr/bin/perl /usr/bin/make /usr/bin/gcc /usr/bin/cc
GCC: Using built-in specs.
COLLECT_GCC=/usr/bin/gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.7/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.7.2-5'
--with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs
--enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.7 --enable-shared --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--enable-gnu-unique-object --enable-plugin --enable-objc-gc
--with-arch-32=i586 --with-tune=generic --enanable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--enable-gnu-unique-object --enable-plugin --enable-objc-gc
--with-arch-32=i586 --with-tune=generic --enable-checking=release
--build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 4.7.2 (Debian 4.7.2-5)
Compilation info (call): CC='/usr/bin/gcc' CFLAGS='-O2
-fno-omit-frame-pointer -g -pipe -Wall -Wno-uninitialized -O3 -g
-static-libgcc -fno-omit-frame-pointer -fno-strict-aliasing -DDBUG_OFF
-DMY_PTHREAD_FASTMUTEX=1' CXX='/usr/bin/g++' CXXFLAGS='-O2
-fno-omit-frame-pointer -g -pipe -Wall -Wno-uninitialized
-fno-exceptions -fno-rtti -O3 -g -static-libgcc -fno-omit-frame-pointer
-fno-strict-aliasing -DDBUG_OFF -DMY_PTHREAD_FASTMUTEX=1' LDFLAGS=''
ASFLAGS=''
Compilation info (used): CC='/usr/bin/gcc' CFLAGS='-O2
-fno-omit-frame-pointer -g -pipe -Wall -Wno-uninitialized -O3 -g
-static-libgcc -fno-omit-frame-pointer -fno-strict-aliasing -DDBUG_OFF
-DMY_PTHREAD_FASTMUTEX=1' CXX='/usr/bin/g++' CXXFLAGS='-O2
-fno-omit-frame-pointer -g -pipe -Wall -Wno-uninitialized
-fno-exceptions -fno-rtti -O3 -g -static-libgcc -fno-omit-frame-pointer
-fno-strict-aliasing -DDBUG_OFF -DMY_PTHREAD_FASTMUTEX=1' LDFLAGS=''
ASFLAGS=''
Perl: This is perl 5, version 14, subversion 2 (v5.14.2) built for
x86_64-linux-gnu-thread-multi
--
The way to make a small fortune in the commodities market is to start
with a large fortune.
Thomas Hackert <thackert@nexgo.de> writes:
[....] Starting MariaDB database server: mysqld . . . . . . . . . . . . . . . . . . . . FAIL . . . . . . . failed! invoke-rc.d: initscript mysql, action "start" failed.
The problem is a failure while starting the server. You need to find the error messages in the server error log. On my system (Debian testing) it is in /var/log/daemon.log. Find the messages logged by mysqld, and if they do not provide you the answer immediately, send them to the list. Often such problems are existing /etc/mysql/my.cnf and/or old data directory that are incompatible. If you are *sure* you do not need any existing data, you can also try to purge (remove is not enough) all mysql/mariadb related packages and try install again. This will *remove* any existing database and let you try a fresh start. Else check the error messages and probably the problem can be corrected. - Kristian.
Hello Kristian, *, sorry for the delay, but had not the time to test the last days ... :( On Thu, Jan 31, 2013 at 10:22:25AM +0100, Kristian Nielsen wrote:
Thomas Hackert <thackert@nexgo.de> writes:
[....] Starting MariaDB database server: mysqld . . . . . . . . . . . . . . . . . . . . FAIL . . . . . . . failed! invoke-rc.d: initscript mysql, action "start" failed.
The problem is a failure while starting the server.
? I had not installed mysql-server (and its dependencies) before ... :( It seems, that it is a problem to try to stop a non-installed server before starting it, or am I wrong ;?
You need to find the error messages in the server error log. On my system (Debian testing) it is in /var/log/daemon.log.
Are you sure? My last entry there is from May 1st ... ;) Neither dmesg nor any other log files seems to report anything wrt mysqld ... :( But I discovered, that mysql itself creates a /var/log/mysql directory as well as *.err and *.log files (which are empty files). In /v/l/mysql are some mariadb-bin.00000$X binary files with one index file. Could they be of any help? And how do I use them? I am using Debian Testing AMD64 as well ... ;)
Find the messages logged by mysqld, and if they do not provide you the answer immediately, send them to the list.
If I had any messages there, which differs from my formerly pasted ones ... ;)
Often such problems are existing /etc/mysql/my.cnf and/or old data directory that are incompatible. If you are *sure* you do not need any existing data, you can also try to purge (remove is not enough) all mysql/mariadb related
Well, to purge is my preferred way to remove packages ... ;)
packages and try install again. This will *remove* any existing database and let you try a fresh start.
But this does not remove /etc/mysql, /var/lib/mysql, the aforementioned logs ... :(
Else check the error messages and probably the problem can be corrected.
/If/ there would be any ... :( Would it be of any help, if I install a logging daemon (not sure, why I have no syslogd and/or alternatives of it installed ... :( I was pretty sure, that some progs need to log every now and then ... ;) )? But only one with no dependencies to mail servers or the like, please ... ;) I had tested it a little bit further. My findings so far: 1. I started the purging of mariadb and its dependencies again. 2. Started to install mariadb-server again. Still the same error message ... :( 3. Purged it again, removed all founded mysql files and directories, and tried to install mariadb-server again, but to no avail ... :( Sorry for the inconvenience and have a nice evening Thomas. -- Cancel me not -- for what then shall remain? Abscissas, some mantissas, modules, modes, A root or two, a torus and a node: The inverse of my verse, a null domain. -- Stanislaw Lem, "Cyberiad"
Thomas Hackert <thackert@nexgo.de> writes:
It seems, that it is a problem to try to stop a non-installed server before starting it, or am I wrong ;?
It does not look like the problem is stopping the server. The error is about a failure to *start* the server.
I had tested it a little bit further. My findings so far: 1. I started the purging of mariadb and its dependencies again. 2. Started to install mariadb-server again. Still the same error message ... :( 3. Purged it again, removed all founded mysql files and directories, and tried to install mariadb-server again, but to no avail ... :(
Ok, I was going to suggest moving away (or deleting if you don't need it) anything in /etc/mysql/ and /var/lib/mysql/ and /var/log/mysql/. But seems you already tried this, and it did not work...
/If/ there would be any ... :( Would it be of any help, if I install a logging daemon (not sure, why I have no syslogd and/or alternatives of it installed ... :( I was pretty sure, that some progs need to log every
Hm, I wonder if this is related. The server logs messages to syslog for .deb packages. I am not sure of the exact mechanism though. I wonder if the server tries to log to syslog, this gives an error because of no syslog present, and this is what causes the server start to fail? There is not much I can say without a better idea of why the server fails to start. One thing you could try is to try and start the server manually after the install fails: sudo /etc/init.d/mysql start You can try with strace -f to spot why it fails, or you can edit /etc/init.d/mysql to make it more verbose in an attempt to spot what causes the problem. Stuff like that. Or is there a way for me to reproduce the problem myself? - Kristian.
Hello Kristian, *, On Mon, Feb 04, 2013 at 10:27:59AM +0100, Kristian Nielsen wrote:
Thomas Hackert <thackert@nexgo.de> writes:
It seems, that it is a problem to try to stop a non-installed server before starting it, or am I wrong ;?
It does not look like the problem is stopping the server. The error is about a failure to *start* the server.
O.K.
I had tested it a little bit further. My findings so far: 1. I started the purging of mariadb and its dependencies again. 2. Started to install mariadb-server again. Still the same error message ... :( 3. Purged it again, removed all founded mysql files and directories, and tried to install mariadb-server again, but to no avail ... :(
Ok, I was going to suggest moving away (or deleting if you don't need it) anything in /etc/mysql/ and /var/lib/mysql/ and /var/log/mysql/. But seems you already tried this, and it did not work...
Unfortunately not ... :(
/If/ there would be any ... :( Would it be of any help, if I install a logging daemon (not sure, why I have no syslogd and/or alternatives of it installed ... :( I was pretty sure, that some progs need to log every
Hm, I wonder if this is related. The server logs messages to syslog for .deb packages. I am not sure of the exact mechanism though. I wonder if the server tries to log to syslog, this gives an error because of no syslog present, and this is what causes the server start to fail?
Should syslog not a dependency to install mariadb-server then?
There is not much I can say without a better idea of why the server fails to start. One thing you could try is to try and start the server manually after the install fails:
sudo /etc/init.d/mysql start
Done this before (but had apparently forgotten to mention it, sorry ... :( ). Leads to <quote> /etc/init.d/mysql start [....] Starting MariaDB database server: mysqld . . . . . . . . . . . . . . . . . . . . [FAIL . . . . . . . failed! </quote> ... :(
You can try with strace -f to spot why it fails, or you can edit /etc/init.d/mysql to make it more verbose in an attempt to spot what causes the problem. Stuff like that.
Well, I have "strace"d it to a file, but am not sure, what it is telling me ... :( The file is 7.2 MB ("bzip"ped only 340 KB) ... :( Is it possible to send it to someone, who is able to "read" strace? I am not, sorry ... :(
Or is there a way for me to reproduce the problem myself?
I am not sure. I have only added mariadb's repository to my /etc/apt/sources.list, run "apt-get update" and tried to install mariadb-server, when I stumbled upon this problem ... ;) Thanks for your answers and have a nice evening Thomas. -- We Klingons believe as you do -- the sick should die. Only the strong should live. -- Kras, "Friday's Child", stardate 3497.2
Hi Thomas, The topmost reason for this kind of failure is usually an existing my.cnf file which contains option(s) not supported by the current version of the server, e.g. deprecated and removed. You mentioned that you purged everything mysql-ish, did it include all instances of my.cnf you could find? They could be hiding in /etc/my.cnf or /usr/etc/my.cnf, etc. Further, if you don't have syslog, your error output currently just goes nowhere; at least I tried to stop rsyslog, and that's what happens. Please try to modify /etc/mysql/conf.d/mysqld_safe_syslog.cnf -- it most likely has 'syslog' option, just change it to skip-syslog. It should enable default error logging to /var/lib/mysql/<machine name>.err. Then, try to run /etc/init.d/mysql start again and see if the error log is updated. If it still isn't, I'd recommend to check permissions on /var/lib/mysql. Regards, Elena On 2/4/2013 10:38 PM, Thomas Hackert wrote:
Hello Kristian, *, On Mon, Feb 04, 2013 at 10:27:59AM +0100, Kristian Nielsen wrote:
Thomas Hackert <thackert@nexgo.de> writes:
It seems, that it is a problem to try to stop a non-installed server before starting it, or am I wrong ;?
It does not look like the problem is stopping the server. The error is about a failure to *start* the server.
O.K.
I had tested it a little bit further. My findings so far: 1. I started the purging of mariadb and its dependencies again. 2. Started to install mariadb-server again. Still the same error message ... :( 3. Purged it again, removed all founded mysql files and directories, and tried to install mariadb-server again, but to no avail ... :(
Ok, I was going to suggest moving away (or deleting if you don't need it) anything in /etc/mysql/ and /var/lib/mysql/ and /var/log/mysql/. But seems you already tried this, and it did not work...
Unfortunately not ... :(
/If/ there would be any ... :( Would it be of any help, if I install a logging daemon (not sure, why I have no syslogd and/or alternatives of it installed ... :( I was pretty sure, that some progs need to log every
Hm, I wonder if this is related. The server logs messages to syslog for .deb packages. I am not sure of the exact mechanism though. I wonder if the server tries to log to syslog, this gives an error because of no syslog present, and this is what causes the server start to fail?
Should syslog not a dependency to install mariadb-server then?
There is not much I can say without a better idea of why the server fails to start. One thing you could try is to try and start the server manually after the install fails:
sudo /etc/init.d/mysql start
Done this before (but had apparently forgotten to mention it, sorry ... :( ). Leads to <quote> /etc/init.d/mysql start [....] Starting MariaDB database server: mysqld . . . . . . . . . . . . . . . . . . . . [FAIL . . . . . . . failed! </quote> ... :(
You can try with strace -f to spot why it fails, or you can edit /etc/init.d/mysql to make it more verbose in an attempt to spot what causes the problem. Stuff like that.
Well, I have "strace"d it to a file, but am not sure, what it is telling me ... :( The file is 7.2 MB ("bzip"ped only 340 KB) ... :( Is it possible to send it to someone, who is able to "read" strace? I am not, sorry ... :(
Or is there a way for me to reproduce the problem myself?
I am not sure. I have only added mariadb's repository to my /etc/apt/sources.list, run "apt-get update" and tried to install mariadb-server, when I stumbled upon this problem ... ;) Thanks for your answers and have a nice evening Thomas.
Hello Elena, *, On Mon, Feb 04, 2013 at 11:13:17PM +0400, Elena Stepanova wrote:
The topmost reason for this kind of failure is usually an existing my.cnf file which contains option(s) not supported by the current version of the server, e.g. deprecated and removed. You mentioned that you purged everything mysql-ish, did it include all instances of my.cnf you could find? They could be hiding in /etc/my.cnf or /usr/etc/my.cnf, etc.
well, I had mentioned it to Kristian (see https://lists.launchpad.net/maria-developers/msg05104.html, where all steps are listed, which I have done) ... ;)
Further, if you don't have syslog, your error output currently just goes nowhere; at least I tried to stop rsyslog, and that's what happens. Please try to modify /etc/mysql/conf.d/mysqld_safe_syslog.cnf -- it most likely has 'syslog' option, just change it to skip-syslog. It should enable default error logging to /var/lib/mysql/<machine name>.err. Then, try to run /etc/init.d/mysql start again and see if the error log is updated.
Cool, did not know this trick, thanks :) Now I have a $name.err ... ;)
If it still isn't, I'd recommend to check permissions on /var/lib/mysql.
It is :) There I found <quote> <snip> 130205 19:12:39 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 99: Cannot assign requested address 130205 19:12:39 [ERROR] Do you already have another mysqld server running on port: 3306 ? 130205 19:12:39 [ERROR] Aborting </snip> ... :( But no mysqld was/is running ... :( Or does it mean, I have to install bind? Sorry for the inconvenience and have a nice evening Thomas. <TOFU removed> -- With all the fancy scientists in the world, why can't they just once build a nuclear balm?
Thomas Hackert <thackert@nexgo.de> writes:
Should syslog not a dependency to install mariadb-server then?
Yes, this is a possibility, but just a guess on my part. Let's be sure of the actual root cause before deciding how to fix.
Well, I have "strace"d it to a file, but am not sure, what it is telling me ... :( The file is 7.2 MB ("bzip"ped only 340 KB) ... :( Is it possible to send it to someone, who is able to "read" strace? I am not, sorry ... :(
If you mail the gzip'ed one to me (or upload it to ftp.askmonty.org in private/ if you prefer), then I will take a look. Thanks! - Kristian.
participants (3)
-
Elena Stepanova -
Kristian Nielsen -
Thomas Hackert