Bug 244949 - deskutils/akonadiconsole: Cannot connect to MySQL server
Summary: deskutils/akonadiconsole: Cannot connect to MySQL server
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-kde (group)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-21 12:41 UTC by Gerard Seibert
Modified: 2021-06-27 12:30 UTC (History)
2 users (show)

See Also:
tcberner: maintainer-feedback+


Attachments
Debug Output (6.62 KB, text/plain)
2020-03-21 12:41 UTC, Gerard Seibert
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gerard Seibert 2020-03-21 12:41:44 UTC
Created attachment 212578 [details]
Debug Output

Server version: 8.0.19
FreeBSD 11.3-RELEASE-p7

Due to the fact that akonadiconsole will not start, other programs are failing as well, such as korganizer.

I have attached the output of gdb. It is not much.
Comment 1 Tobias C. Berner freebsd_committer freebsd_triage 2020-04-14 15:09:02 UTC
Comment on attachment 212578 [details]
Debug Output

Moin moin 

Sorry for the late reply:

Looking at:
mysqladmin: connect to server at 'localhost' failed 

Can you manually connect to the database?


mfg tobias
Comment 2 Gerard Seibert 2020-04-14 21:18:54 UTC
(In reply to Tobias C. Berner from comment #1)
I am not sure exactly what you are referring to. I don't think that a database was created. I see no sign that one was. I do have other MySQL databases that I connect to without any problems.
Comment 3 Adriaan de Groot freebsd_committer freebsd_triage 2021-06-27 12:30:31 UTC
I'm going to close this one as "overcome by events" since it's a year old. I'm sorry we didn't have time and energy to chase it down -- I've had some **similar** issues in the past where the mysql wouldn't start for Akonadi. I forget what I did in such cases, though.

As a general debugging guide for this, let's take a belated look:

The log contains this:

```
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial connection!
org.kde.pim.akonadiserver: executable: "/usr/local/libexec/mysqld"
org.kde.pim.akonadiserver: arguments: ("--defaults-file=/home/gerard/.local/share/akonadi/mysql.conf", "--datadir=/home/gerard/.local/share/akonadi/db_data/", "--socket=/var/run/user/1001/akonadi/mysql.socket", "--pid-file=/var/run/user/1001/akonadi/mysql.pid")
```

This says that **mysqld** itself didn't start; the place to look for problems is therefore in the log of **that** program, not in akonadi. Looking at my machine today (where Akonadi doesn't work either, but for totally different reasons) I **do** see mysqld running:

```
10854  -  I     0:40.32 /usr/local/libexec/mysqld --defaults-file=/home/adridg/.local/share/akonadi/mysql.conf --datadir=/home/adridg/.local/share/akonadi/db_data/ --socket=/var/run/user/1001/akonadi/mysql.socket --pid-file=/var/run/user/1001/akonadi/mysql.pid
```

In the *datadir* you can find the error log from mysqld, so that would-have-been the place to look. With mysqld running, there's a socket you can connect to to debug the database; without it running, there's a log file.