[Kde-pim] Akonadi postgresql backend not working

[Daniel Vrátil]

Hi,

it appears that you can solve your problem by removing the entire [QPSQL] 
section from ~/.config/akonadi/akonadiserverrc - it will get recreated with 
correct values.

I pushed some PostgreSQL startup fixes to 1.12 branch (and master) that should 
fix start when akonadiserverrc contains empty values (as produced by Akonadi 
KCM).

Dan

On Tuesday 06 of May 2014 14:23:41 Daniel Vrátil wrote:
> On Thursday 01 of May 2014 19:21:45 GEO wrote:
> > On Tuesday 22 April 2014 14:50:02 Daniel Vrátil wrote:
> > > I have attached a patch for DbConfigPostgresql that does so, if you can
> > > test it, please do.
> > 
> > Hi,
> > 
> > Sorry it took so long, I have been busy.
> > I have recompiled Akonadi with your patch, so in the following we talk
> > about the patched version.
> > 
> > Remember when we had a conversation on IRC, regarding the TCP issues, when
> > already one instance of postgres was running?
> > Because those issues complement it each other disjunctly:
> > 
> > Suppose all akonadi/kmail settings are purged: (cd && find | grep akonadi
> > |
> > xargs rm -rf  && find | grep mail | xargs rm -rf) and postgres is not
> > running (sudo killall -9 postgres), because on Ubuntu postgres if
> > installed
> > autostarts automatically on boot.
> > 
> > Then we set the postgres internal backend for akonadi and run "akonadictl
> > start". We will get the output as attached in 1.txt.
> > 
> > Now akonadi is not running, but postgres is running!
> > If we run akonadictl start now, we will get the issue we discussed in IRC,
> > output attached as 2.txt.
> > 
> > Setting listen_addresses = ''  in
> > .local/share/akonadi/db_data/postgresql.conf, removing everything apart
> > the
> > [%General] section in .config/akonadi/akonadiserverrc and starting akonadi
> > again works, output attached as 3.txt.
> 
> Hi,
> 
> could you please attach ~/.config/akonadi/akonadiserverrc with which the
> startup is failing for you?
> 
> Thanks
> Dan
> 
> > To conclude a normal user will never get the postgres backend working on
> > Ubuntu 14.04, because if no postgres is running, postgres refuses
> > connection and if postgres is running you will get the TCP conflict.
> > Remember we are talking here about stock 14.04 without any strange
> > modifications to either Akonadi or Postgres.
> > 
> > I know you offered me a patch once to fix the TCP conflict, but if I
> > remember correctly it did not work, but please link it again, as I have
> > lost it :-(.
> > 
> > Anway the patch you provided in the last mail should be merged!
> > 
> > I hope you can help me sort this issue out!
> > I am willing to recompile and test stuff as well as providing
> > configuration
> > stuff you need.
> > 
> > Thanks

-- 
Daniel Vrátil | dvratil at redhat.com | dvratil on #kde-devel, #kontact, #akonadi
KDE Desktop Team
Associate Software Engineer, Red Hat, Inc.

GPG Key: 0xC59D614F6F4AE348
Fingerprint: 4EC1 86E3 C54E 0B39 5FDD B5FB C59D 614F 6F4A E348
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20140506/43d291c6/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/