Bug 7751 - PostgreSQL 9.2 doesn't start in Cauldron
Summary: PostgreSQL 9.2 doesn't start in Cauldron
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: High major
Target Milestone: ---
Assignee: Funda Wang
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-10 01:25 CEST by Frédéric "LpSolit" Buclin
Modified: 2013-02-04 00:31 CET (History)
4 users (show)

See Also:
Source RPM: postgresql-9.2
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Frédéric "LpSolit" Buclin 2012-10-10 01:25:33 CEST 
I installed postgresql9.2-server-9.2.1-1.mga3 in Cauldron. It cannot start due to a missing /usr/bin/postgresql-check-db-dir script:

# systemctl status postgresql.service
postgresql.service - PostgreSQL database server
          Loaded: loaded (/usr/lib/systemd/system/postgresql.service; disabled)
          Active: failed (Result: exit-code) since Wed, 10 Oct 2012 01:20:15 +0200; 1min 9s ago
         Process: 4253 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA} (code=exited, status=203/EXEC)
          CGroup: name=systemd:/system/postgresql.service

Oct 10 01:20:15 localhost systemd[1]: Starting PostgreSQL database server...
Oct 10 01:20:15 localhost systemd[4253]: Failed at step EXEC spawning /usr/bin/postgresql-check-db-dir: No such file or directory
Oct 10 01:20:15 localhost systemd[1]: Failed to start PostgreSQL database server.
Comment 1 Frédéric "LpSolit" Buclin 2012-10-10 01:29:25 CEST 
I also cannot locate pg_hba.conf.
Comment 2 Remco Rijnders 2012-10-10 08:18:48 CEST 
Assigning to maintainer, Cc to maintainer other postgresql packages.

CC: (none) => nanardon, remco
Assignee: bugsquad => fundawang

Comment 3 Frédéric "LpSolit" Buclin 2012-10-11 19:06:16 CEST 
With postgresql9.2-server-9.2.1-2.mga3, the error is now:

# systemctl status postgresql.service
postgresql.service - PostgreSQL database server
          Loaded: loaded (/usr/lib/systemd/system/postgresql.service; disabled)
          Active: failed (Result: exit-code) since Thu, 11 Oct 2012 19:04:43 +0200; 2s ago
         Process: 6990 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p ${PGPORT} -w -t 300 (code=exited, status=1/FAILURE)
          CGroup: name=systemd:/system/postgresql.service

Oct 11 19:04:38 localhost pg_ctl[6990]: postgres ne peut pas accéder au fichier de configuration « /var/lib/pgsql/data/postgresql.conf » : Aucun fichier ou dossier de ce type
Oct 11 19:04:43 localhost pg_ctl[6990]: pg_ctl : n'a pas pu démarrer le serveur
Oct 11 19:04:43 localhost pg_ctl[6990]: Examinez le journal applicatif.
Oct 11 19:04:43 localhost systemd[1]: Failed to start PostgreSQL database server.
Samuel Verschelde 2012-10-15 16:29:29 CEST

CC: (none) => stormi

Comment 4 Frédéric "LpSolit" Buclin 2012-11-23 14:15:24 CET 
Could someone fix this bug please? I see that postgresql9.2-server-9.2.1-3.mga3 has been uploaded but due to this bug, this makes the new package totally useless.
Comment 5 Shlomi Fish 2013-01-08 11:15:34 CET 
Hi,

(In reply to comment #4)
> Could someone fix this bug please? I see that postgresql9.2-server-9.2.1-3.mga3
> has been uploaded but due to this bug, this makes the new package totally
> useless.

I ran into this problem too. I cannot install php-pdo_pgsql either. This bug should really be fixed. I'll try to investigate.

Regards,

-- Shlomi Fish

CC: (none) => shlomif

Comment 6 Funda Wang 2013-01-22 15:05:06 CET 
still valid?
Comment 7 Frédéric "LpSolit" Buclin 2013-01-22 23:08:49 CET 
(In reply to comment #6)
> still valid?

Looks like PostgreSQL is starting correctly now. I will try to test later this week if it also works correctly.
Comment 8 Funda Wang 2013-02-03 19:46:53 CET 
ping?
Comment 9 Frédéric "LpSolit" Buclin 2013-02-04 00:31:01 CET 
PostgreSQL is working correctly again. I installed Bugzilla using PostgreSQL as DB server, and everything is working fine now.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.