[kde-freebsd] Akonadi/mysqld problems

[Dwayne MacKinnon]

Done some further digging:

It appears that something is going on with the db connections between 
mysqld and akonadi. The net_read_timeout value is being invoked, 
somehow. Basically, under the default value, 30, 30 seconds after you 
start up akonadi mysqld kills all the connections. Akonadi expects 
persistent connections... the conf file it uses resets wait_timeout to 1 
year.

I'm currently experimenting with changing net_read_timeout, although 
obviously this is a hack fix. I've set it to 1 hr. We'll see how that goes.

Couple of other things:
When akonadi sets up its database, it doesn't create the mysql system 
database. This creates a bunch of errors when mysqld starts up. It may 
not do any actual harm, though. On linux the mysql system database is 
installed.

The reset of wait_timeout to 1 year seems to be ignored. On my system 
it stays at the default 8 hrs.

Cheers,
DMK


On May 30, 2012 08:02:44 PM Alberto Villa wrote:
> On Wed, May 30, 2012 at 6:16 PM, Jaap Boender 
<jaapb at kerguelen.org> wrote:
> > Just to chime in here, I've been having the same problem (exact 
same
> > messages); also with the internal postgres server where akonadi 
doesn't
> > want to start because of 'pg_ctl: another server may be running' 
errors
> > (which isn't the case, and it still does this even after I remove the
> > .local/share/akonadi directory)
> > 
> > At least for a workaround: it does work with an external postgres 
server.
> 
> Just guessing: maybe Akonadi fails to detect running instance of local
> database because of Linux-dependent code?