Mailinglist Archive: opensuse (1786 mails)
| < Previous | Next > |
Re: [opensuse] Trouble with kmail
- From: Will Stephenson <wstephenson@xxxxxxx>
- Date: Wed, 23 Nov 2011 12:57:46 +0100
- Message-id: <11140280.QUkupXsUUN@whistler.site>
On Saturday 19 November 2011 08:48:17 lynn wrote:
It's a private 'embedded' instance, not the system wide server you're running,
so users don't need to do anything to set it up. Look at the Test 6 output
you pasted. As a mysql user you'll recognise that the config Akonadi's mysql
uses is optimised for this private local usage.
AFAICS it's a mysql upgrade problem, not a KMail problem. As a mysql user,
are you using some nonstandard mysql packages? Zypper locks to some specific
version you need?
<snip/>
The following looks like MySQL is unable to run at all. Check that all your
mysql packages are upgraded from 11.4 and are mysql-community-server, not
mariadb. Check that the usual system mysqld can run without error.
HTH
Will
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx
On 19/11/11 08:28, Roger Luedecke wrote:
On Saturday, November 19, 2011 08:10:13 AM lynn wrote:
On 18/11/11 17:07, Will Stephenson wrote:
On Friday 18 Nov 2011 16:16:23 lynn wrote:
On 18/11/11 12:41, Will Stephenson wrote:
On Friday 18 November 2011 11:36:30 Kaare Rasmussen wrote:
Uh, not really - the backup list won't solve Eddie's
problems.
I
need
to get the migration guide finished. Until I do that here's
Ubuntu's
guide:
https://wiki.kubuntu.org/OneiricOcelot/Final/Kubuntu/Kmail2
All these pages about kmail2 talks about moving stuff into the
Akonadi
server. I haven't found a description of exactly what that is.
The
closest I've found is http://community.kde.org/KDE_PIM/Akonadi
I've always liked the fact that kmail stores mails as
maildirs.
Easy
to
backup, process and handle outside kmail. Will this change? Is
this
configurable?
OK. I give up. 11.4 to 12.1 upgrade.
Migration failed. I've deleted all kmail stuff from .kde4
How do I start from scratch and get kmail to start? it will not
start
because akonadi has errors.
Thanks. L x
"Could not fetch the resource collection"? Or which error?
The ubuntu guide above explains how to resolve that one by
correcting
the path of the local folders resource to a valid path.
To get a blank slate, remove all of
~/.local/share/akonadi (Akonadi's databases)
~/.config/akonadi (configuration for Akonadi itself)
~/.kde4/share/config/akonadi* (configuration for KDE-based Akonadi
resources, eg imap or pop accounts)
and move aside ~/.kde4/share/config/kmail*
HTH, I'm on child rearing duties until Saturday morning so I will
check
back in then.
Will
Nope. Still doesn't work. Removing what you say gives these errors:
MySQL server not found
Executing the MySQL server failed
;ySQL server configuration not found or not readable
Akonadi control process not registered at dbus
+ some others.
Akonadi needs MySQL? I happen to use MySQL but most desktop users
don't
do they?
It's a private 'embedded' instance, not the system wide server you're running,
so users don't need to do anything to set it up. Look at the Test 6 output
you pasted. As a mysql user you'll recognise that the config Akonadi's mysql
uses is optimised for this private local usage.
Really confused with this. 12.2 should never have shipped with kmail2
if
it wasn't ready.
AFAICS it's a mysql upgrade problem, not a KMail problem. As a mysql user,
are you using some nonstandard mysql packages? Zypper locks to some specific
version you need?
Whats the problem? I have KMail with Google IMAP and AKonadi running
flawlessly. I missed the other messages since I been swamped lately.
OK. Followed the removal instructions above and get these errors:
<snip/>
The following looks like MySQL is unable to run at all. Check that all your
mysql packages are upgraded from 11.4 and are mysql-community-server, not
mariadb. Check that the usual system mysqld can run without error.
HTH
Will
Test 5: ERROR--
--------
MySQL server log contains errors.
Details: The MySQL server error log file '<a
href='/home/steve/.local/share/akonadi/db_data/mysql.err'>/home/steve/.local
/share/akonadi/db_data/mysql.err</a>' contains errors.
File content of '/home/steve/.local/share/akonadi/db_data/mysql.err':
111118 15:50:11 InnoDB: The InnoDB memory heap is disabled
111118 15:50:11 InnoDB: Mutexes and rw_locks use GCC atomic builtins
111118 15:50:11 InnoDB: Compressed tables use zlib 1.2.5
111118 15:50:11 InnoDB: Initializing buffer pool, size = 80.0M
111118 15:50:11 InnoDB: Completed initialization of buffer pool
111118 15:50:11 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
111118 15:50:11 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...
111118 15:50:11 InnoDB: Waiting for the background threads to start
111118 15:50:12 InnoDB: 1.1.8 started; log sequence number 607756
111118 15:50:12 InnoDB: Assertion failure in thread 139884215142144 in
file trx0purge.c line 828
InnoDB: Failing assertion: purge_sys->purge_trx_no <=
purge_sys->rseg->last_trx_no
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.
111118 15:50:12 - 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.
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx
| < Previous | Next > |