- Package:
- akonadi-backend-postgresql
- Source:
- akonadi
- Submitter:
- Vincent-Xavier JUMEL
- Date:
- 2019-12-07 15:57:03 UTC
- Severity:
- important
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
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
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/msg00000.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.
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