[Bug 241980] New: Akonadi does not always start mysql correctly

[Andre Heinecke]

https://bugs.kde.org/show_bug.cgi?id=241980

           Summary: Akonadi does not always start mysql correctly
           Product: Akonadi
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: MS Windows
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: server
        AssignedTo: vkrause at kde.org
        ReportedBy: aheinecke at intevation.de
                CC: kdepim-bugs at kde.org


Version:           unspecified (using Devel) 
OS:                MS Windows

Akonadi very often shows an Error Message, and sometimes does not start the
mysql server correctly after that.

Reproducible: Sometimes

Steps to Reproduce:
Either use the E-5 installer (which packages Akonadi from trunk at the moment)
as described here:
http://wiki.kolab.org/index.php/Kontact_for_Windows_(Enterprise-5) or from the
KDE-Windows Installer. Install it and start Akonadiconsole.

It is most likely the same cause as for Bug 241977
https://bugs.kde.org/show_bug.cgi?id=241977 


Actual Results:  
Starting akonadiserver (by either starting Kontact or akonadiconsole, or
akonadictl start) on Windows produces an error message nearly instantly that
QMysql 
This does not happen every time though and mainly appeared during the first
startup and/or on low performance systems.

The exact Error that shows up in a Error Dialog Box(annoying) is:
Failed to connect to database: Can't connect to MySQL server on 'localhost'
(10061) QMYSQL: Unable to connect.

In most cases Startup then continues normally. In some cases tough, again
mostly on slow performance Systems mysqld then gets started four times and the
Error log of mysql gets filled with messages that several processes are trying
to get data and the akonadiserver startup fails. 

Expected Results:  
Akonadi would quietly start one instance of mysqlserver.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.