Bug#946199: akonadi-backend-postgresql: akonadictl fails to start with postgresql backend
control: severity -1 important Hey, I'm lowering the severity, as this package is not unfit for testing. It was used for serveral moths in experimental, where people used also Postgresql backend without any issues. hefee -- On Freitag, 6. Dezember 2019 12:57:03 CET Diederik de Haas wrote: > On donderdag 5 december 2019 15:34:37 CET Sandro Knauß wrote: > > do you have apparmor enabled? Maybe the Apparmor profile does not match > > anymore. Can you give it a try with aa-disable postgresql_akonadi? > > I have akonadi-backend-postgresql and apparmor enabled and it is working for > me. I only have PostgreSQL 12 though. > https://lists.debian.org/debian-kde/2019/11/msg0.html shows the way I > upgraded to PSQL 12 (and purged PSQL 11) > > If you have both, but didn't upgrade your cluster (ie transfer your akonadi > database to PSQL 12) and rebooted, then I think PSQL 12 uses the default > PSQL port. If you didn't change your config, then akonadi is asking PSQL 12 > for its data, but it can't find it. > That could be an explanation why it isn't working for Vincent-Xavier. signature.asc Description: This is a digitally signed message part.
Bug#946199: akonadi-backend-postgresql: akonadictl fails to start with postgresql backend
On donderdag 5 december 2019 15:34:37 CET Sandro Knauß wrote: > do you have apparmor enabled? Maybe the Apparmor profile does not match > anymore. Can you give it a try with aa-disable postgresql_akonadi? I have akonadi-backend-postgresql and apparmor enabled and it is working for me. I only have PostgreSQL 12 though. https://lists.debian.org/debian-kde/2019/11/msg0.html shows the way I upgraded to PSQL 12 (and purged PSQL 11) If you have both, but didn't upgrade your cluster (ie transfer your akonadi database to PSQL 12) and rebooted, then I think PSQL 12 uses the default PSQL port. If you didn't change your config, then akonadi is asking PSQL 12 for its data, but it can't find it. That could be an explanation why it isn't working for Vincent-Xavier. signature.asc Description: This is a digitally signed message part.
Bug#946199: akonadi-backend-postgresql: akonadictl fails to start with postgresql backend
Hey, do you have apparmor enabled? Maybe the Apparmor profile does not match anymore. Can you give it a try with aa-disable postgresql_akonadi? hefee -- >* What led up to the situation? >akonadi-backend-postgresql upgrade > >* What exactly did you do (or not do) that was effective (or > ineffective)? > >restart akonadictl, withou any effect, restart postgresql, on different >system with version 11 and 12. Postgresql connection is still available > >* What was the outcome of this action? >None >* What outcome did you expect instead? >Akonadi working > > > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, > 'stable-updates'), (500, 'stable-debug'), (500, 'buster-fasttrack'), (500, > 'unstable'), (500, 'testing'), (500, 'stable'), (100, 'buster-backports') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr > (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages akonadi-backend-postgresql depends on: > ii libqt5sql5-psql 5.12.5+dfsg-2 > > Versions of packages akonadi-backend-postgresql recommends: > ii akonadi-server 4:19.08.3-1 > ii postgresql 12+210 > > akonadi-backend-postgresql suggests no packages. > > -- no debconf information signature.asc Description: This is a digitally signed message part.
Bug#946199: akonadi-backend-postgresql: akonadictl fails to start with postgresql backend
Package: akonadi-backend-postgresql Version: 4:19.08.3-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? akonadi-backend-postgresql upgrade * What exactly did you do (or not do) that was effective (or ineffective)? restart akonadictl, withou any effect, restart postgresql, on different system with version 11 and 12. Postgresql connection is still available * What was the outcome of this action? None * What outcome did you expect instead? Akonadi working -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'stable-debug'), (500, 'buster-fasttrack'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (100, 'buster-backports') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages akonadi-backend-postgresql depends on: ii libqt5sql5-psql 5.12.5+dfsg-2 Versions of packages akonadi-backend-postgresql recommends: ii akonadi-server 4:19.08.3-1 ii postgresql 12+210 akonadi-backend-postgresql suggests no packages. -- no debconf information
