Description of problem:

This one is a bit weird, but I have seen it twice and can reproduce it. It seems that postgresql 9.1 can only start once some extra thing is installed, and that extra component is part of the apache2 dependencies, not the postgresql ones.

How reproducible:

Always


Steps to Reproduce:

1. 
Remove apache, postgresql to start with a clean system:

urpme apache-mpm-prefork ; urpme postgresql9.1; urpme  postgresql9.1-server ; urpme postgresql9.1-plpgsql ; urpme postgresql9.1-contrib;  urpme --auto-orphans
rm -rf /var/lib/pgsql/


2. Install JUST postgres:

urpmi postgresql9.1 postgresql9.1-server postgresql9.1-plpgsql postgresql9.1-contrib

3. The installer complains:

Failed to issue method call: Unit postgresql.service failed to load: No such file or directory. See system logs and 'systemctl status postgresql.service' for details.
warning: %posttrans(postgresql9.1-server-9.1.3-1.mga2.x86_64) scriptlet failed, exit status 1


4. Manually starting it complains:

# service postgresql start
Starting postgresql (via systemctl):  Failed to issue method call: Unit postgresql.service failed to load: No such file or directory. See system logs and 'systemctl status postgresql.service' for details.  [FAILED]

                                              
# systemctl status postgresql.service
postgresql.service
          Loaded: error (Reason: No such file or directory)
          Active: inactive (dead) since Wed, 14 Mar 2012 00:22:12 +0000; 1min 45s ago
        Main PID: 6056 (code=exited, status=0/SUCCESS)


I also noticed that /var/lib/pgsql/data is rather empty.


5. Now install apache2:  urpmi apache-mpm-prefork-2.2.22-3  (and all 47 dependencies)


6. It is now possible to start postgresql.


Sorry this report only explains what happens and not why!