[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#921987: marked as done (mysqld-akonadi: Could not open required defaults file)

Your message dated Thu, 14 Feb 2019 18:26:34 +0100
with message-id <2683176.ex05xb4Vyj@tuxin>
and subject line Re: Bug#921987: mysqld-akonadi: Could not open required defaults file
has caused the Debian Bug report #921987,
regarding mysqld-akonadi: Could not open required defaults file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
921987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921987
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: akonadi-backend-mysql
Version: 4:18.08.3-3
Severity: important

Dear Maintainer,

Since yesturday, akonadi is not able to start in Debian Sid (up-do-date).

When I run "akonadictl start", here is the result:

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
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/sbin/mysqld-akonadi"
org.kde.pim.akonadiserver: arguments: ("--defaults-file=/home/[my login]/.local/share/akonadi/mysql.conf", "--datadir=/home/[my login]/.local/share/akonadi/db_data/", "--socket=/tmp/user/1000/akonadi-[my login].449afV/mysql.socket", "--pid-file=/tmp/user/1000/akonadi-[my login].449afV/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "mysqld-akonadi: [ERROR] Could not open required defaults file: /home/[my login]/.local/share/akonadi/mysql.conf\nmysqld-akonadi: [ERROR] Fatal error in defaults handling. Program aborted!\n"
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/tmp/user/1000/akonadi-[my login].449afV/mysql.socket' (2)'
Check that mysqld is running and that the socket: '/tmp/user/1000/akonadi-[my login].449afV/mysql.socket' exists!
org.kde.pim.akonadiserver: Failed to remove runtime connection config file
org.kde.pim.akonadicontrol: Application 'akonadiserver' exited normally...

mysql.conf is set as following: -rw-r--r-- 

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages akonadi-backend-mysql depends on:
ii  libqt5sql5-mysql                                   5.11.3+dfsg-4
ii  mysql-client-core-5.7 [virtual-mysql-client-core]  5.7.25-1
ii  mysql-server-5.7 [virtual-mysql-server]            5.7.25-1

Versions of packages akonadi-backend-mysql recommends:
ii  akonadi-server  4:18.08.3-3

akonadi-backend-mysql suggests no packages.

-- Configuration Files:
/etc/apparmor.d/usr.sbin.mysqld-akonadi changed [not included]

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 4:18.08.3-3

Close it as it was connection to not supported software.

hefee

--
On Donnerstag, 14. Februar 2019 12:38:04 CET Reinhard Karcher wrote:
> I removed mysql from my computer and installed akonadi-backend-mysql; that
> installed mariadb and mariadb started without problems and I am now using
> the mysql-backend.
> 
> Reinhard

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: