No email yet, although there are about 500 msgs in in the spool file.
Akonadi is being a problem child, here is a start log that failed.
Test 5: ERROR
--------
MySQL server log contains errors.
Details: The MySQL server error log file '<a href='/home/gene/.local/share/akonadi/db_data/mysql.err'>/home/gene/.local/share/akonadi/db_data/mysql.err[/url]' contains errors.
File content of '/home/gene/.local/share/akonadi/db_data/mysql.err':
110418 12:33:17 InnoDB: Initializing buffer pool, size = 80.0M
110418 12:33:17 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.
110418 12:33:17 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.
Wash, rinse, repeat.
Actually that's just the first error and that's probably 30k just for this
Whats the best SWAG here? I have had synaptic re-install akonadi, no diff. And I get lost in 'database'ish stuff.
htop says there are about 10% of the usual mysql instances running. Only 2, so I killed them, but when as root, I did a service mysql restart, it wasn't found, so syntaptic is re-installing that whole kit. Didn't help. Humm, mysqld wasn't running, but is now. That shortened the akonadi startup log but it still fails to start
Test 5: ERROR
--------
MySQL server log contains errors.
Details: The MySQL server error log file '<a href='/home/gene/.local/share/akonadi/db_data/mysql.err'>/home/gene/.local/share/akonad
i/db_data/mysql.err[/url]' contains errors.
File content of '/home/gene/.local/share/akonadi/db_data/mysql.err':
110418 13:00:08 InnoDB: Initializing buffer pool, size = 80.0M
110418 13:00:08 InnoDB: Completed initialization of buffer pool
110418 13:00:08 InnoDB: Started; log sequence number 0 144037
110418 13:00:08 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.55' socket: '/home/gene/.local/share/akonadi/socket-coyote.coyote.den/mysql.socket' port: 0 PCLinuxOS - MySQL Standard E
dition (GPL)
InnoDB: Error: tablespace id is 4 in the data dictionary
InnoDB: but in file ./akonadi/collectiontable.ibd it is 49!
110418 13:00:09 InnoDB: Assertion failure in thread 3070528368 in file fil/fil0fil.c line 603
InnoDB: Failing assertion: 0
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.1/en/forcing-innodb-recovery.htmlInnoDB: about forcing recovery.
110418 13:00:09 - 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=8384512
read_buffer_size=131072
max_used_connections=2
max_threads=256
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 566893 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x9cdcd10
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 = 0xb704836c thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x29) [0x84a0f29]
/usr/sbin/mysqld(handle_segfault+0x50c) [0x81de0ac]
[0xffffe400]
[0xffffe424]
/lib/i686/libc.so.6(gsignal+0x51) [0x4970c291]
/lib/i686/libc.so.6(abort+0x17e) [0x4970ddbe]
/usr/sbin/mysqld() [0x839f1d0]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0xac904538): Can't read from address 0xac904538: Invalid argument.
Connection ID (thread ID): 2
Status: NOT_KILLED
I need a magic twanger to help me see the trees in all this forest.
Thanks & Cheers, Gene