Summary: | After system crash, postgresql akonadi server doesn't start due to lock file | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Benjamin M <alvanx> |
Component: | server | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | christophe |
Priority: | NOR | ||
Version: | 4.7 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/akonadi/f217d9e96dc8de88916e8ca0b93dd9a7500bbbc3 | Version Fixed In: | 1.12.2 |
Sentry Crash Report: |
Description
Benjamin M
2011-11-17 08:02:11 UTC
Correction to 2nd sentence: "Whenever I restart after a proper shutdown, ..." should be "Whenever I restart after an improper shutdown, ...". Git commit f217d9e96dc8de88916e8ca0b93dd9a7500bbbc3 by Dan Vrátil. Committed on 06/05/2014 at 14:38. Pushed by dvratil into branch '1.12'. Fix PostgreSQL start when postmaster.pid is not removed after non-clean shutdown When PostgreSQL is not terminated nicely, a pidfile is left behind in db_data, which will prevent pg_ctl from starting a new PostgreSQL server. We check for postmaster.pid file and verify that postgres server with PID specified in the pidfile is not running anymore, then delete the pidfile to allow pg_ctl to start a new server. If the postgres server is still running (possibly after Akonadi server crash), we try to connect to it right away. FIXED-IN: 1.12.2 M +37 -0 server/src/storage/dbconfigpostgresql.cpp http://commits.kde.org/akonadi/f217d9e96dc8de88916e8ca0b93dd9a7500bbbc3 |