Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Akonadi errors
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Barade
n00b
n00b


Joined: 03 Feb 2009
Posts: 25

PostPosted: Tue Aug 05, 2014 10:27 pm    Post subject: Akonadi errors Reply with quote

Akonadi fails to start.

mysql.err
Code:

140806  2:22:13  InnoDB: Initializing buffer pool, size = 80.0M
140806  2:22:13  InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140806  2:22:13  InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.


mysql.conf
Code:

#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
# sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)
max_connections=256

# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)

# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0

# Do not cache results (default:1)
query_cache_type=0

# Do not use the privileges mechanisms
skip_grant_tables

# Do not listen for TCP/IP connections at all
skip_networking

# The number of open tables for all threads. (default:64)
table_open_cache=200

# How many threads the server should cache for reuse (default:0)
thread_cache_size=3

# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000

# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=16K

[client]
default-character-set=utf8


Akonadi server version 1.11.0

emerge --info
Code:

Portage 2.2.8-r1 (default/linux/amd64/13.0/desktop/kde/systemd, gcc-4.7.3, glibc-2.19-r1, 3.15.7-gentoo x86_64)
=================================================================
System uname: Linux-3.15.7-gentoo-x86_64-Intel-R-_Core-TM-_i7-4710HQ_CPU_@_2.50GHz-with-gentoo-2.2
KiB Mem:    16360744 total,  11646880 free
KiB Swap:    8388604 total,   8388604 free
Timestamp of tree: Tue, 05 Aug 2014 21:30:01 +0000
ld GNU ld (Gentoo 2.23.2 p1.0) 2.23.2
app-shells/bash:          4.2_p45
dev-lang/python:          2.7.7, 3.3.5-r1
dev-util/cmake:           2.8.12.2-r1
dev-util/pkgconfig:       0.28-r1
sys-apps/baselayout:      2.2
sys-apps/openrc:          0.12.4
sys-apps/sandbox:         2.6-r1
sys-devel/autoconf:       2.13, 2.69
sys-devel/automake:       1.12.6, 1.13.4
sys-devel/binutils:       2.23.2
sys-devel/gcc:            4.7.3-r1
sys-devel/gcc-config:     1.7.3
sys-devel/libtool:        2.4.2-r1
sys-devel/make:           3.82-r4
sys-kernel/linux-headers: 3.13 (virtual/os-headers)
sys-libs/glibc:           2.19-r1
Repositories: gentoo gamerlay godin
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="* -@EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt /usr/share/themes/oxygen-gtk/gtk-2.0"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://distfiles.gentoo.org"
LANG="en_US.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j8"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/var/lib/layman/gamerlay /var/lib/layman/godin"
USE="X a52 aac acl acpi alsa amd64 berkdb bluetooth branding bzip2 cairo cdda cdr clang cli cracklib crypt cryptsetup cups cxx dbus declarative dri dts dvd dvdr emboss encode exif fam ffmpeg firefox flac fortran gdbm gif gpm gtk iconv ipv6 jpeg kde kipi lcms ldap libnotify mad melt mmx mng modules mp3 mp4 mpeg multilib ncurses networkmanager nls nptl ogg opengl openmp pam pango pcre pdf phonon plasma png policykit ppds pulseaudio python qt3support qt4 readline sdl semantic-desktop session spell sqlite sse sse2 ssl startup-notification svg systemd tcpd threads tiff truetype udev udisks unicode upower usb vorbis webkit wxwidgets x264 xcb xcomposite xinerama xml xscreensaver xv xvid zlib" ABI_X86="64" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm
authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-5" PYTHON_
SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_3" RUBY_TARGETS="ruby19 ruby20" USERLAND="GNU" VIDEO_CARDS="nvidia intel fbdev" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, SYNC, USE_PYTHON

Back to top
View user's profile Send private message
MickKi
Veteran
Veteran


Joined: 08 Feb 2004
Posts: 1107
Location: 51:45:20N, 0:40:44W

PostPosted: Sun Aug 10, 2014 10:43 am    Post subject: Reply with quote

I have the same error, following upgrade of mysql to 5.5.39 but my error continues with more information:
Code:
[snip ...]
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140810  9:28:28  InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
140810  9:28:28  InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
140810  9:28:28 InnoDB: Could not open or create data files.
140810  9:28:28 InnoDB: If you tried to add new data files, and it failed here,
140810  9:28:28 InnoDB: you should now edit innodb_data_file_path in my.cnf back
140810  9:28:28 InnoDB: to what it was, and remove the new ibdata files InnoDB created
140810  9:28:28 InnoDB: in this failed attempt. InnoDB only wrote those files full of
140810  9:28:28 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
140810  9:28:28 InnoDB: remove old data files which contain your precious data!
140810  9:28:28 [ERROR] Plugin 'InnoDB' init function returned error.
140810  9:28:28 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
140810  9:28:28 [ERROR] Unknown/unsupported storage engine: innodb
140810  9:28:28 [ERROR] Aborting

140810  9:28:28 [Note] /usr/sbin/mysqld: Shutdown complete


In addition I have rebuilt:

dev-qt/qtcore-4.8.5-r2
app-office/akonadi-server-1.11.0
sys-libs/glibc-2.19-r1

and have run successfully:

mysql_upgrade --socket=/tmp/akonadi-michael.2CRt9p/mysql.socket

This is happening on two different user accounts, so I am guessing some change with mysql has brought it about. If I could only go back to KDE3 days with not semantic c*ap and databases, I would be a really happy camper. :-(
_________________
Regards,
Mick
Back to top
View user's profile Send private message
Poldi_232
n00b
n00b


Joined: 10 Aug 2014
Posts: 1

PostPosted: Sun Aug 10, 2014 10:29 pm    Post subject: Reply with quote

I got the same errors after update (emerge --sync -q && emerge -uDvqaN --with-bdeps=y --autounmask-write @world && emerge -qav @preserved-rebuild && emerge -a --depclean && dispatch-conf) today:

Code:

InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process


I followed the hints for usage of mysql_update from http://stackoverflow.com/a/20990016 which seemed to work successfully. But the problem persisted.

Then I tried
Code:
sudo revdep-rebuild

which resulted in
Code:
emerge --oneshot --complete-graph dev-qt/qtsql:4

After this akonadi worked.
Back to top
View user's profile Send private message
MickKi
Veteran
Veteran


Joined: 08 Feb 2004
Posts: 1107
Location: 51:45:20N, 0:40:44W

PostPosted: Mon Aug 11, 2014 7:10 pm    Post subject: Reply with quote

Thanks for the hint!

I thought that I had run revdep-rebuild as part of my regular incantation, but clearly I hadn't on this machine. Once it installed dev-qt/qtsql:4 all worked as intended.
_________________
Regards,
Mick
Back to top
View user's profile Send private message
Barade
n00b
n00b


Joined: 03 Feb 2009
Posts: 25

PostPosted: Mon Aug 11, 2014 9:20 pm    Post subject: Reply with quote

Does not work for me, I still get:
Code:

140812  1:18:00 InnoDB: The InnoDB memory heap is disabled
140812  1:18:00 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140812  1:18:00 InnoDB: Compressed tables use zlib 1.2.8
140812  1:18:00 InnoDB: Using Linux native AIO
140812  1:18:00 InnoDB: Initializing buffer pool, size = 80.0M
140812  1:18:00 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140812  1:18:00  InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
Back to top
View user's profile Send private message
Barade
n00b
n00b


Joined: 03 Feb 2009
Posts: 25

PostPosted: Mon Aug 11, 2014 9:20 pm    Post subject: Reply with quote

bw. I just copied the data from another PC so do I have to remove any temporary files?!
Back to top
View user's profile Send private message
adsicks
n00b
n00b


Joined: 08 Sep 2012
Posts: 9
Location: Oklahoma, USA

PostPosted: Sun Aug 17, 2014 1:24 am    Post subject: I think this is the why Reply with quote

Code:
dd /usr/lib64/qt4/plugins/sqldrivers/libqsqlmysql.so
   linux-vdso.so.1 (0x00007ffff4787000)
   libmysqlclient_r.so.16 => not found
   libQtSql.so.4 => /usr/lib64/qt4/libQtSql.so.4 (0x00007f72f1016000)
   libQtCore.so.4 => /usr/lib64/qt4/libQtCore.so.4 (0x00007f72f0b40000)
   libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libstdc++.so.6 (0x00007f72f083b000)
   libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so.1 (0x00007f72f0624000)
   libc.so.6 => /lib64/libc.so.6 (0x00007f72f0280000)
   libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f72eff4f000)
   libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f72efd30000)
   libz.so.1 => /lib64/libz.so.1 (0x00007f72efb1a000)
   libdl.so.2 => /lib64/libdl.so.2 (0x00007f72ef916000)
   librt.so.1 => /lib64/librt.so.1 (0x00007f72ef70d000)
   libm.so.6 => /lib64/libm.so.6 (0x00007f72ef40c000)
   /lib64/ld-linux-x86-64.so.2 (0x0000003422c00000)

Hopefully
Code:
emerge --oneshot --complete-graph dev-qt/qtsql:4

will fix my bad symlink.

Update:
It just did:
Code:
ldd /usr/lib64/qt4/plugins/sqldrivers/libqsqlmysql.so
   linux-vdso.so.1 (0x00007fff561ff000)
   libmysqlclient.so.18 => /usr/lib64/libmysqlclient.so.18 (0x00007ff276886000)
   libQtSql.so.4 => /usr/lib64/qt4/libQtSql.so.4 (0x00007ff276645000)
   libQtCore.so.4 => /usr/lib64/qt4/libQtCore.so.4 (0x00007ff27616f000)
   libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libstdc++.so.6 (0x00007ff275e6a000)
   libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so.1 (0x00007ff275c54000)
   libc.so.6 => /lib64/libc.so.6 (0x00007ff2758af000)
   libz.so.1 => /lib64/libz.so.1 (0x00007ff275699000)
   libssl.so.1.0.0 => /usr/lib64/libssl.so.1.0.0 (0x00007ff275433000)
   libcrypto.so.1.0.0 => /usr/lib64/libcrypto.so.1.0.0 (0x00007ff275087000)
   libdl.so.2 => /lib64/libdl.so.2 (0x00007ff274e83000)
   libpthread.so.0 => /lib64/libpthread.so.0 (0x00007ff274c65000)
   libm.so.6 => /lib64/libm.so.6 (0x00007ff274963000)
   libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007ff274632000)
   librt.so.1 => /lib64/librt.so.1 (0x00007ff27442a000)
   /lib64/ld-linux-x86-64.so.2 (0x0000003422c00000)


akonadi now starts!!!
Back to top
View user's profile Send private message
Barade
n00b
n00b


Joined: 03 Feb 2009
Posts: 25

PostPosted: Tue Aug 19, 2014 11:50 am    Post subject: Reply with quote

It still does not work for me.
I've made the upgrade and remerged qtsql.
Now I've killed all mysqld processes and tried to restart and then I got:
Code:

140819 15:47:22 InnoDB: The InnoDB memory heap is disabled
140819 15:47:22 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140819 15:47:22 InnoDB: Compressed tables use zlib 1.2.8
140819 15:47:22 InnoDB: Using Linux native AIO
140819 15:47:22 InnoDB: Initializing buffer pool, size = 80.0M
140819 15:47:22 InnoDB: Completed initialization of buffer pool
140819 15:47:22 InnoDB: highest supported file format is Barracuda.
140819 15:47:22  InnoDB: Warning: allocated tablespace 13, old maximum was 0
140819 15:47:22  InnoDB: Waiting for the background threads to start
140819 15:47:23 InnoDB: 5.5.39 started; log sequence number 181297397340
140819 15:47:23 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.39'  socket: '/tmp/akonadi-me.vgkqyB/mysql.socket'  port: 0  Source distribution
InnoDB: Error: tablespace id is 34 in the data dictionary
InnoDB: but in file ./akonadi/collectionmimetyperelation.ibd it is 16!
140819 15:47:23  InnoDB: Assertion failure in thread 139741226571520 in file fil0fil.c line 768
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://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: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
13:47:23 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=16384
read_buffer_size=131072
max_used_connections=2
max_threads=256
thread_count=2
connection_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 560022 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x164b650
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 = 7f180a2b8ee8 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x29)[0x76b039]
/usr/sbin/mysqld(handle_fatal_signal+0x35c)[0x66e71c]
/lib64/libpthread.so.0(+0x11250)[0x7f181a0a0250]
/lib64/libc.so.6(gsignal+0x35)[0x7f1818c9a795]
/lib64/libc.so.6(abort+0x148)[0x7f1818c9bc18]
/usr/sbin/mysqld[0x8143d8]
/usr/sbin/mysqld[0x8144b4]
/usr/sbin/mysqld[0x81bc33]
/usr/sbin/mysqld[0x7f8a59]
/usr/sbin/mysqld[0x7f9401]
/usr/sbin/mysqld[0x7ea102]
/usr/sbin/mysqld[0x7ccb46]
/usr/sbin/mysqld[0x7cd289]
/usr/sbin/mysqld[0x7cdd23]
/usr/sbin/mysqld[0x806cd8]
/usr/sbin/mysqld[0x807055]
/usr/sbin/mysqld[0x783740]
/usr/sbin/mysqld(_ZN7handler7ha_openEP5TABLEPKcii+0x3f)[0x671eaf]
/usr/sbin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0x567)[0x600457]
/usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootP18Open_table_context+0x98f)[0x55fdbf]
/usr/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x42b)[0x56071b]
/usr/sbin/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy+0x49)[0x560fd9]
/usr/sbin/mysqld[0x62960d]
/usr/sbin/mysqld(_ZN21Check_table_statement7executeEP3THD+0xb2)[0x62abc2]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0xcf7)[0x590cc7]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x180)[0x595630]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1484)[0x596ad4]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x176)[0x61fb56]
/usr/sbin/mysqld(handle_one_connection+0x4a)[0x61fbba]
/lib64/libpthread.so.0(+0x91da)[0x7f181a0981da]
/lib64/libc.so.6(clone+0x6d)[0x7f1818d4fd7d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f17f8004a50): CHECK TABLE `collectionmimetyperelation`  FOR UPGRADE
Connection ID (thread ID): 2
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

maybe killing the processes was the wrong way but at least the errors are different.
Anyone knows what to do?
Back to top
View user's profile Send private message
adsicks
n00b
n00b


Joined: 08 Sep 2012
Posts: 9
Location: Oklahoma, USA

PostPosted: Tue Aug 19, 2014 2:55 pm    Post subject: There is the first clue Reply with quote

Code:
InnoDB: Error: tablespace id is 34 in the data dictionary
InnoDB: but in file ./akonadi/collectionmimetyperelation.ibd it is 16!


Looks like table corruption.....

Try

Code:
mysql_upgrade
/etc/init.d/mysql stop
/etc/init.d/mysql start


And see if that fixes it....
Back to top
View user's profile Send private message
Barade
n00b
n00b


Joined: 03 Feb 2009
Posts: 25

PostPosted: Fri Aug 22, 2014 9:36 pm    Post subject: Reply with quote

I use systemd so I enabled the mysqld but it says:
Code:

systemctl status mysqld.service
● mysqld.service - MySQL database server
   Loaded: loaded (/usr/lib64/systemd/system/mysqld.service; enabled)
   Active: failed (Result: start-limit) since Fri 2014-08-22 23:27:28 CEST; 10s ago
  Process: 30879 ExecStartPost=/usr/libexec/mysqld-wait-ready $MAINPID (code=exited, status=1/FAILURE)
  Process: 30878 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS)
 Main PID: 30878 (code=exited, status=0/SUCCESS)

Aug 22 23:27:28 user systemd[1]: Failed to start MySQL database server.
Aug 22 23:27:28 user systemd[1]: Unit mysqld.service entered failed state.
Aug 22 23:27:28 user systemd[1]: mysqld.service holdoff time over, scheduling restart.
Aug 22 23:27:28 user systemd[1]: Stopping MySQL database server...
Aug 22 23:27:28 user systemd[1]: Starting MySQL database server...
Aug 22 23:27:28 user systemd[1]: mysqld.service start request repeated too quickly, refusing to start.
Aug 22 23:27:28 user systemd[1]: Failed to start MySQL database server.
Aug 22 23:27:28 user systemd[1]: Unit mysqld.service entered failed state.


and the log dir
Code:


vim /var/log/mysql/mysqld.err
140822 23:29:17 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140822 23:29:19 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140822 23:29:19 [Warning] Can't create test file /var/lib/mysql/user.lower-test
140822 23:29:19 [Warning] Can't create test file /var/lib/mysql/user.lower-test
140822 23:29:19 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=mysqld-bin' to avoid this problem.
^G/usr/sbin/mysqld: File './mysqld-bin.index' not found (Errcode: 13)
140822 23:29:19 [ERROR] Aborting


I thought when using an internal MySQL server with akonadi I hadn't have to start the daemon ...

edit:
and mysql_upgrade says:
Code:

mysql_upgrade
Looking for 'mysql' as: mysql
Looking for 'mysqlcheck' as: mysqlcheck
FATAL ERROR: Upgrade failed
Back to top
View user's profile Send private message
MickKi
Veteran
Veteran


Joined: 08 Feb 2004
Posts: 1107
Location: 51:45:20N, 0:40:44W

PostPosted: Wed Aug 27, 2014 9:09 am    Post subject: Reply with quote

Barade, have a look in your /tmp directory to find out what is the socket that akonadi is connected to, then run mysql_upgrade using the socket like so:
Code:
mysql_upgrade --socket=/tmp/akonadi-michael.2CRt9p/mysql.socket

Of course in your case the socket path would be different. BTW, as I discovered, you have to run any akonadi commands logged into the desktop and not remotely through ssh.
_________________
Regards,
Mick
Back to top
View user's profile Send private message
Barade
n00b
n00b


Joined: 03 Feb 2009
Posts: 25

PostPosted: Sun Aug 31, 2014 12:41 pm    Post subject: Reply with quote

Of course I did that. I also got the mysqld working with systemd but it still doesn't work. I also tried http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html.
I still have the old data on the old computer. Maybe I will try to make the upgrade there first and then move the data to the new computer.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum