FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian KDE

 
 
LinkBack Thread Tools
 
Old 12-02-2011, 04:26 PM
Michael Strobel
 
Default Kontact broken after upgrading to KDE 4.7.2

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello!

I recently upgraded to KDE 4.7.2. and installed kdepim which doesn't
seem to work.
I appended the logs.

regards Michael


(resending sice the mailing list daemon did non respond)



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJO2QosAAoJEJykIvTGvo0BnJwP/16xC86tzd2Ga+mjZMr+RTJZ
4ra7le3eHxFU7U9R3BDXpAsKtP76h9NNpGWpKIcAjRTyDZmCOs Qq+G1ekRRC67Vw
MxmxCciCA7mJLmltOS9xS2t2y1BFyiLP7FVDUv78OcB6+U6VPQ jUt4eeYlOfHgiJ
zNFR8iBe/qPW6NnjcJXpwh9VcmQsM3tRU8dxkYtRfe+a97kf9FUcAeID2XX mlNI5
+zRSE+jqv9IXaHYz/nCs4nV+EOXMoLrdMWyYnm1m0yNKM41SMYNoMce20o2f7eG5
zmITFQRsy8cVzEam7WT+cykJhbF9pEorGd8fW+/uF8Ren2wiigcKA6DUmulmzRWV
PZcEIFefYMFzX06WbJZ/NwA6NhcFndx69zKWZ7f3Afmk9UAC9G0WXGwaHRX/1pOz
mGHmUdTvJ7sNdP1fKPpTmzsSBUrSdI5TWKHDL0+H1MkqmqhJpM NkRi3fTjUp++D3
0jKXeu3mSB5Wej0hfk+0MPNw58aXRc8nPU6EzYgbLroqq5Q/T5rN/gtLu7d4ZMc/
KewpAsfp0XK3onFylClfA+PfnPdoafs3KkmkQ1dEa+DPFsk4GT QudmhzzFQ5r8Iw
Gh3hn1whD1Or1Eqw+nB26hGh8wYI9HT2I/5h6vJcu/k/d8+jGiEkrsPfGQoJZRKp
qtV9UCuirikUbQsZW0aT
=zgvk
-----END PGP SIGNATURE-----
Akonadi Server Self-Test Report
===============================

Test 1: SUCCESS
--------

Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system.

File content of '/home/michael/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/home/michael/.local/share/akonadi/socket-MacBook/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null


Test 2: SUCCESS
--------

Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.

Test 3: SUCCESS
--------

MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server '/usr/sbin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution.

Test 4: SUCCESS
--------

MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld Ver 5.1.58-1 for debian-linux-gnu on x86_64 ((Debian))


Test 5: ERROR
--------

MySQL server log contains errors.
Details: The MySQL server error log file &apos;<a href='/home/michael/.local/share/akonadi/db_data/mysql.err'>/home/michael/.local/share/akonadi/db_data/mysql.err</a>&apos; contains errors.

File content of '/home/michael/.local/share/akonadi/db_data/mysql.err':
111201 14:18:26 [Note] Plugin 'FEDERATED' is disabled.
111201 14:18:26 InnoDB: Initializing buffer pool, size = 80.0M
111201 14:18:26 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
111201 14:18:26 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 2654, file name ./mysql-bin.000003
111201 14:18:26 InnoDB: Started; log sequence number 0 8713003
111201 14:18:26 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
111201 14:18:26 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
111201 14:18:26 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.58-1' socket: '/home/michael/.local/share/akonadi/socket-MacBook/mysql.socket' port: 0 (Debian)
InnoDB: Error: Removing element from mem pool free list 64 though the
InnoDB: element is not marked free!
InnoDB: Apparent memory corruption: mem dump len 500; hex 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000b100000000000000e0 7c0cb8aa7f00001050dfb2aa7f0000a000000000000000f63d 775f0000000000000000000000000000000000000000030000 00000000000000000000000000000000000000000008000000 01000000000000000000000001000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000030c00db8aa7f00 00f0740cb8aa7f000000000000000000003143010000000000 10c00db8aa7f0000307c0cb8aa7f00002843010000000000f6 3d775f00000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 ; asc | P =w_ 0 t 1C 0| (C =w_ ;
InnoDB: Scanning backward trying to find previous allocated mem blocks
111201 14:18:26 - mysqld got signal 11 ;
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=8384512
read_buffer_size=131072
max_used_connections=1
max_threads=256
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 567892 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7faab88d72f0
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 = 0x7faab5923e80 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x29) [0x7faab600ec09]
/usr/sbin/mysqld(handle_segfault+0x440) [0x7faab5d03020]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf020) [0x7faab555f020]
/usr/sbin/mysqld(mem_analyze_corruption+0x8a) [0x7faab5f2d60a]
/usr/sbin/mysqld(mem_area_alloc+0x2bc) [0x7faab5f2edcc]
/usr/sbin/mysqld(+0x59f83e) [0x7faab5f2d83e]
/usr/sbin/mysqld(mem_heap_add_block+0x50) [0x7faab5f2e4c0]
/usr/sbin/mysqld(trx_undo_get_undo_rec_low+0x193) [0x7faab5f7cdd3]
/usr/sbin/mysqld(trx_undo_prev_version_build+0x445) [0x7faab5f7d2e5]
/usr/sbin/mysqld(row_vers_build_for_consistent_read+0x4f3) [0x7faab5f69d83]
/usr/sbin/mysqld(row_search_for_mysql+0x2cb1) [0x7faab5f62c61]
/usr/sbin/mysqld(ha_innobase::index_read(unsigned char*, unsigned char const*, unsigned int, ha_rkey_function)+0x18f) [0x7faab5eb98af]
/usr/sbin/mysqld(ha_innobase::index_first(unsigned char*)+0x37) [0x7faab5eb69a7]
/usr/sbin/mysqld(ha_innobase::rnd_next(unsigned char*)+0x37) [0x7faab5ebeda7]
/usr/sbin/mysqld(rr_sequential(READ_RECORD*)+0x19) [0x7faab5df83c9]
/usr/sbin/mysqld(sub_select(JOIN*, st_join_table*, bool)+0x63) [0x7faab5d6dd03]
/usr/sbin/mysqld(+0x3f17d3) [0x7faab5d7f7d3]
/usr/sbin/mysqld(JOIN::exec()+0xbcb) [0x7faab5d8c6fb]
/usr/sbin/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*)+0x12e) [0x7faab5d87fbe]
/usr/sbin/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned long)+0x174) [0x7faab5d8dd64]
/usr/sbin/mysqld(+0x3818a1) [0x7faab5d0f8a1]
/usr/sbin/mysqld(mysql_execute_command(THD*)+0x4de) [0x7faab5d164de]
/usr/sbin/mysqld(Prepared_statement::execute(String*, bool)+0x395) [0x7faab5d9c755]
/usr/sbin/mysqld(Prepared_statement::execute_loop(String*, bool, unsigned char*, unsigned char*)+0x8e) [0x7faab5d9c82e]
/usr/sbin/mysqld(mysqld_stmt_execute(THD*, char*, unsigned int)+0x1ea) [0x7faab5d9cf4a]
/usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x4c2) [0x7faab5d1e2e2]
/usr/sbin/mysqld(do_command(THD*)+0xea) [0x7faab5d1f87a]
/usr/sbin/mysqld(handle_one_connection+0x235) [0x7faab5d0f315]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b40) [0x7faab5556b40]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7faab409136d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7faab8923e00): SELECT * FROM PimItemTable LIMIT 1
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.


Test 6: SUCCESS
--------

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/etc/akonadi/mysql-global.conf'>/etc/akonadi/mysql-global.conf</a>.

File content of '/etc/akonadi/mysql-global.conf':
#
# 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]
skip_grant_tables
skip_networking

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#sql_mode=strict_trans_tables,strict_all_tables,st rict_error_for_division_by_zero,no_auto_create_use r,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

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=utf8
collation_server=utf8_general_ci
table_cache=200
thread_cache_size=3
#log_bin=mysql-bin
#expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# 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
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2

# Do not drop the connection to the DB after 8 hours of inactivity
wait_timeout=31536000

[client]
default-character-set=utf8


Test 7: SKIP
--------

MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.

Test 8: SUCCESS
--------

MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href='/home/michael/.local/share/akonadi/mysql.conf'>/home/michael/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/michael/.local/share/akonadi/mysql.conf':
#
# 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]
skip_grant_tables
skip_networking

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#sql_mode=strict_trans_tables,strict_all_tables,st rict_error_for_division_by_zero,no_auto_create_use r,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

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=utf8
collation_server=utf8_general_ci
table_cache=200
thread_cache_size=3
#log_bin=mysql-bin
#expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# 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
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2

# Do not drop the connection to the DB after 8 hours of inactivity
wait_timeout=1296000

[client]
default-character-set=utf8


Test 9: SUCCESS
--------

akonadictl found and usable
Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 1.6.2


Test 10: ERROR
--------

Akonadi control process not registered at D-Bus.
Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 11: ERROR
--------

Akonadi server process not registered at D-Bus.
Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 12: SUCCESS
--------

Nepomuk search service registered at D-Bus.
Details: The Nepomuk search service is registered at D-Bus which typically indicates it is operational.

Test 13: SUCCESS
--------

Nepomuk search service uses an appropriate backend.
Details: The Nepomuk search service uses one of the recommended backends.

Test 14: SKIP
--------

Protocol version check not possible.
Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements.

Test 15: ERROR
--------

No resource agents found.
Details: No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: '/usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/usr/share:/usr/share:/usr/local/share'; make sure this includes all paths where Akonadi agents are installed.

Directory listing of '/usr/share/akonadi/agents':
birthdaysresource.desktop
contactsresource.desktop
icalresource.desktop
imapresource.desktop
kabcresource.desktop
kcalresource.desktop
knutresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mboxresource.desktop
microblog.desktop
mtdummyresource.desktop
nepomukcalendarfeeder.desktop
nepomukcontactfeeder.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
pop3resource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/share:/usr/local/share'

Test 16: ERROR
--------

Current Akonadi server error log found.
Details: The Akonadi server reported errors during its current startup. The log can be found in <a href='/home/michael/.local/share/akonadi/akonadiserver.error'>/home/michael/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/michael/.local/share/akonadi/akonadiserver.error':
"Unable to retrieve data from table 'PimItemTable'.
Query error: 'Lost connection to MySQL server during query QMYSQL3: Unable to execute statement'"
Unable to initialize database.
"[
0: akonadiserver() [0x417c34]
1: akonadiserver() [0x417fbe]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x32480) [0x7fb0b0106480]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7fb0b0106405]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x180) [0x7fb0b0109680]
5: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+ 0x111) [0x7fb0b1dd2371]
6: akonadiserver() [0x419632]
7: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xaf) [0x7fb0b1e5f9ff]
8: /usr/lib/libQtCore.so.4(+0x118123) [0x7fb0b1e68123]
9: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x39) [0x7fb0b1e70fc9]
10: akonadiserver() [0x41b7db]
11: akonadiserver() [0x41c8b7]
12: akonadiserver() [0x412e42]
13: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fb0b00f2ead]
14: akonadiserver() [0x4136d1]
]
"


Test 17: ERROR
--------

Previous Akonadi server error log found.
Details: The Akonadi server reported errors during its previous startup. The log can be found in <a href='/home/michael/.local/share/akonadi/akonadiserver.error.old'>/home/michael/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/home/michael/.local/share/akonadi/akonadiserver.error.old':
"Unable to retrieve data from table 'PimItemTable'.
Query error: 'Lost connection to MySQL server during query QMYSQL3: Unable to execute statement'"
Unable to initialize database.
"[
0: akonadiserver() [0x417c34]
1: akonadiserver() [0x417fbe]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x32480) [0x7f6c7d3f3480]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f6c7d3f3405]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x180) [0x7f6c7d3f6680]
5: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+ 0x111) [0x7f6c7f0bf371]
6: akonadiserver() [0x419632]
7: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xaf) [0x7f6c7f14c9ff]
8: /usr/lib/libQtCore.so.4(+0x118123) [0x7f6c7f155123]
9: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x39) [0x7f6c7f15dfc9]
10: akonadiserver() [0x41b7db]
11: akonadiserver() [0x41c8b7]
12: akonadiserver() [0x412e42]
13: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f6c7d3dfead]
14: akonadiserver() [0x4136d1]
]
"


Test 18: SUCCESS
--------

No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.

Test 19: SUCCESS
--------

No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.
 
Old 12-05-2011, 01:49 PM
Martin Steigerwald
 
Default Kontact broken after upgrading to KDE 4.7.2

Am Freitag, 2. Dezember 2011 schrieb Michael Strobel:
> InnoDB: Last MySQL binlog file position 0 2654, file name
> ./mysql-bin.000003 111201 14:18:26 InnoDB: Started; log sequence
> number 0 8713003 111201 14:18:26 [Warning] Can't open and lock time
> zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying
> to live without them 111201 14:18:26 [ERROR] Can't open and lock
> privilege tables: Table 'mysql.servers' doesn't exist 111201 14:18:26
> [Note] /usr/sbin/mysqld: ready for connections. Version:
> '5.1.58-1' socket:
> '/home/michael/.local/share/akonadi/socket-MacBook/mysql.socket' port
> : 0 (Debian) InnoDB: Error: Removing element from mem pool free list
> 64 though the InnoDB: element is not marked free!
> InnoDB: Apparent memory corruption: mem dump len 500; hex
> 00000000000000000000000000000000000000000000000000 00000000000000000000
[…]
> asc
> | P =w_
>
> 0 t 1C 0| (C =w_
>
>
>
> ; InnoDB: Scanning backward trying to find previous allocated
> mem blocks 111201 14:18:26 - mysqld got signal 11 ;
> 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.

This and the following doesn´t look like a KDE problem at all.

Did you have a sudden power outage or crash in the last time. I´ve heard
reports that MySQL with the default configuration that Akonadi uses for it
is prone to database corruptions after such occurences.

Here Kontact works with KDE 4.7.2. But I am using a system-wide PostgreSQL
database for it.

As long as only contacts are stored in Akonadi it should be possible to
do:

1) akonadictl stop
2) mv .local/share/akonadi ls -l .local/share/akonadi-broken
3) akonadictl start

Otherwise you would need to repair the database manually for now. Maybe
its sufficient to remove the binlog file(s) - in that case you will loose
some changes to the databases.

But AFAIR even with mail, there is nothing in there, that couldn´t be
rebuilt from source.

Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201112051549.29424.Martin@lichtvoll.de">http://lists.debian.org/201112051549.29424.Martin@lichtvoll.de
 
Old 12-05-2011, 02:06 PM
Martin Steigerwald
 
Default Kontact broken after upgrading to KDE 4.7.2

Am Freitag, 2. Dezember 2011 schrieb Michael Strobel:
> InnoDB: Apparent memory corruption: mem dump len 500; hex

Note: This could also be a hardware problem.

When only part of the memory chip is broke, it might not be triggered all
of the time.

So if in doubt I suggest having the machine run with memtest86++ run over
night or so.

--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201112051606.13621.Martin@lichtvoll.de">http://lists.debian.org/201112051606.13621.Martin@lichtvoll.de
 
Old 12-05-2011, 06:56 PM
Michael Strobel
 
Default Kontact broken after upgrading to KDE 4.7.2

On 12/05/2011 03:49 PM, Martin Steigerwald wrote:


> Am Freitag, 2. Dezember 2011 schrieb Michael Strobel:


>> InnoDB: Last MySQL binlog file position 0 2654, file name
>> ./mysql-bin.000003 111201 14:18:26 InnoDB: Started; log sequence
>> number 0 8713003 111201 14:18:26 [Warning] Can't open and lock time
>> zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying
>> to live without them 111201 14:18:26 [ERROR] Can't open and lock
>> privilege tables: Table 'mysql.servers' doesn't exist 111201 14:18:26
>> [Note] /usr/sbin/mysqld: ready for connections. Version:
>> '5.1.58-1' socket:
>> '/home/michael/.local/share/akonadi/socket-MacBook/mysql.socket' port
>> : 0 (Debian) InnoDB: Error: Removing element from mem pool free list
>> 64 though the InnoDB: element is not marked free!
>> InnoDB: Apparent memory corruption: mem dump len 500; hex
>> 00000000000000000000000000000000000000000000000000 00000000000000000000


> […]


>> asc
>> | P =w_
>>
>> 0 t 1C 0| (C =w_
>>
>>
>>
>> ; InnoDB: Scanning backward trying to find previous allocated
>> mem blocks 111201 14:18:26 - mysqld got signal 11 ;
>> 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.


> This and the following doesn´t look like a KDE problem at all.
>
> Did you have a sudden power outage or crash in the last time. I´ve heard
> reports that MySQL with the default configuration that Akonadi uses for it
> is prone to database corruptions after such occurences.
>
> Here Kontact works with KDE 4.7.2. But I am using a system-wide PostgreSQL
> database for it.
>
> As long as only contacts are stored in Akonadi it should be possible to
> do:
>
> 1) akonadictl stop
> 2) mv .local/share/akonadi ls -l .local/share/akonadi-broken
> 3) akonadictl start
>
> Otherwise you would need to repair the database manually for now. Maybe
> its sufficient to remove the binlog file(s) - in that case you will loose
> some changes to the databases.
>
> But AFAIR even with mail, there is nothing in there, that couldn´t be
> rebuilt from source.
>
> Ciao,


Hello,

indeed i had to do a hard reset some days ago your workaround helped.
Thank you very much.

regards
Michael
 

Thread Tools




All times are GMT. The time now is 12:17 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org