I just uninstalled the MySQL server but the daemon was still running in RAM. While it was still running, I got Inconsistency detected by ld.so: dl-open.c: 623: _dl_open: Assertion `_dl_debug_initialize (0, args.nsid)->r_state == RT_CONSISTENT' failed! when trying to install mysql-community (the command that failed, was tar). >>> Unpacking mysql-5.1.29-rc.tar.gz to /var/tmp/portage/dev-db/mysql-community-5.1.29_rc/work Inconsistency detected by ld.so: dl-open.c: 623: _dl_open: Assertion `_dl_debug_initialize (0, args.nsid)->r_state == RT_CONSISTENT' failed! * * ERROR: dev-db/mysql-community-5.1.29_rc failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 3663: Called mysql_src_unpack * environment, line 3299: Called unpack 'mysql-extras-20070916.tar.bz2' 'mysql-5.1.29-rc.tar.gz' * ebuild.sh, line 368: Called die * The specific snippet of code: * tar zoxf "${srcdir}${x}" ${tar_opts} || die "$myfail" * The die message: * failure unpacking mysql-5.1.29-rc.tar.gz * * If you need support, post the topmost build error, and the call stack if relevant. Even when I tried to use tar on the command line, I got the same error about inconsistency. After stopping MySQL, my system worked again as expected. IMHO, a warning should be placed after uninstalling MySQL to stop the daemon! Reproducible: Always Steps to Reproduce: 1. Install MySQL 2. Start MySQL daemon 3. Uninstall MySQL but don't stop the daemon 4. Some tar.gz and tar.bz2 archives won't unpack - e. g. mysql-5.1.29-rc.tar.gz
Hmmm, correction: my system doesn't work correctly after stopping the daemon. It works again after reinstalling MySQL - otherwise e. g. I cannot log into SSH :(
Still investigating... it might be a problem with libnss-mysql always needing some libs...
(In reply to comment #2) > Still investigating... it might be a problem with libnss-mysql always needing > some libs... Even so, you probably should have a configuration fallback to allow normal work for a few critical users when the database isn't available. I don't think this is a bug that Gentoo can fix for you.
Yeah, you're right. It was my mistake not remembering that I use SQL auth. Marked as FIXED.
