Bug 303740 - postgresql akonadi backend does not start if hostname changes
Summary: postgresql akonadi backend does not start if hostname changes
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 1.7.2
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 13:06 UTC by luisfe
Modified: 2016-10-31 19:12 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description luisfe 2012-07-18 13:06:55 UTC
if the hostname of the computer changes then akonadi does not start. The problem seems that the socket address

/home/[user]/.local/share/akonadi/socket-[hostname]

is harcoded in 
.local/share/akonadi/db_data/postgresql.conf

as

unix_socket_directory = '/home/[user]/.local/share/akonadi/socket-[hostname]'

Reproducible: Always

Steps to Reproduce:
1. Create a new empty user /akonadi configuration with postgresql backend and default options.
2. Change the hostname of the computer.
3. Reboot
Actual Results:  
postgresql refuses to start with error 

stdout: "esperando que el servidor se inicie....FATAL:  no se pudo crear el archivo de bloqueo «/home/user/.local/share/akonadi/socket-oldhostname/.s.PGSQL.5432.lock»: No existe el fichero o el directorio

Expected Results:  
hostname changes should not affect akonadi. It does not for .kde/ socket-cache-tmp symlinks
Comment 1 Denis Kurz 2016-09-24 20:36:07 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 luisfe 2016-10-31 19:12:26 UTC
I cannot further reproduce this bug with kmail 5.2.3