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

Bug#883435: marked as done (akonadi-backend-postgresql: akonadictl start fails with Postgresql 10 installed, likely needs a rebuild)

Your message dated Tue, 05 Dec 2017 22:44:23 +0100
with message-id <1852107.uSn5dy8YCK@bagend>
and subject line Re: Bug#883435: akonadi-backend-postgresql: akonadictl start fails with Postgresql 10 installed, likely needs a rebuild
has caused the Debian Bug report #883435,
regarding akonadi-backend-postgresql: akonadictl start fails with Postgresql 10 installed, likely needs a rebuild
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.)


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

Now that qt does support Postgresql 10 (#876421) I upgraded my
Postgresql packages to 10 and migrated the cluster (from 9.6).
After that I did 'akonadictl start' and noticed it was still using
Postgresql 9.6. So I purged that (and rebooted) and after that, akonadi
didn't want to start anymore. For some reason it's explicitly trying to
use pg_ctl from 9.6, but it should use the 10 version.

Konsole output:

$ akonadictl start
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Could not start database server!
org.kde.pim.akonadiserver: executable: "/usr/lib/postgresql/9.6/bin/pg_ctl"
org.kde.pim.akonadiserver: arguments: ("start", "-w", "--timeout=10", "--pgdata=/home/diederik/.local/share/akonadi/db_data", "-o \"-k/tmp/akonadi-diederik.IOXa0T\" -h ''")
org.kde.pim.akonadiserver: process error: "execvp: No such file or directory"
org.kde.pim.akonadiserver: Failed to remove runtime connection config file
org.kde.pim.akonadicontrol: Application 'akonadiserver' exited normally...

So my guess is that akonadi-backend-postgresql needs to be rebuild so
that it gets linked to the current Postgresql version, which is 10 (in
both testing and sid).

(Even better would be if it would use the most recent version, but that
may be stretching it)

Cheers,
  Diederik

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages akonadi-backend-postgresql depends on:
ii  libqt5sql5-psql  5.9.2+dfsg-5

Versions of packages akonadi-backend-postgresql recommends:
ii  akonadi-server  4:17.08.0-1+b1
ii  postgresql      10+188

akonadi-backend-postgresql suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
For some reason my config file contained the 9.6 path to pg_ctl and some other 
weird settings. Including a MYSQL block, which I have never used ...
And now it also looks like my akonadi database is gone, thus closing this bug.

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


--- End Message ---
Reply to: