[SOLVED] After upgrade to mga2 postgresql cannot be started

This forum is dedicated to basic help and support :

Ask here your questions about basic installation and usage of Mageia. For example you may post here all your questions about getting Mageia isos and installing it, configuring your printer, using your word processor etc.

Try to ask your questions in the right sub-forum with as much details as you can gather. the more precise the question will be, the more likely you are to get a useful answer

[SOLVED] After upgrade to mga2 postgresql cannot be started

Postby magfan » Jun 4th, '12, 13:01

After the upgrade from Mageia 1 to Mageia 2 postgresql cannot be started any more:

Code: Select all
[root@cortex etc]# systemctl start postgresql.service
[root@cortex etc]# systemctl status postgresql.service
postgresql.service - LSB: PostgreSql server database
          Loaded: loaded (/etc/rc.d/init.d/postgresql)
          Active: failed (Result: exit-code) since Mon, 04 Jun 2012 12:51:45 +0200; 6s ago
         Process: 14327 ExecStop=/etc/rc.d/init.d/postgresql stop (code=exited, status=1/FAILURE)
         Process: 14282 ExecStart=/etc/rc.d/init.d/postgresql start (code=exited, status=0/SUCCESS)
        Main PID: 14318 (code=exited, status=1/FAILURE)
          CGroup: name=systemd:/system/postgresql.service

Jun 04 12:51:45 cortex su[14294]: pam_tcb(su-l:session): Session opened for...0)
Jun 04 12:51:45 cortex postgresql[14282]: Dienst postgresql wird gestartet: ...]
Jun 04 12:51:45 cortex su[14339]: pam_tcb(su-l:session): Session opened for...0)
Jun 04 12:51:45 cortex postgresql[14327]: Stoppen des postgresql-Dienstes: p...t
Jun 04 12:51:45 cortex postgresql[14327]: Is server running?
[root@cortex etc]#


It happened that my backup software (SEP sesam) told me that there is no postgres server running. Starting it manually failed. What can I do?
Last edited by magfan on Jun 6th, '12, 08:28, edited 1 time in total.
magfan
 
Posts: 334
Joined: Apr 3rd, '12, 12:33

Re: After upgrade mga1 -> mga2 postgresql cannot be started

Postby doktor5000 » Jun 5th, '12, 19:35

Please show the output of
Code: Select all
rpm -qa | grep postgresql
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18056
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: After upgrade mga1 -> mga2 postgresql cannot be started

Postby magfan » Jun 6th, '12, 08:27

Code: Select all
[root@cortex etc]# rpm -qa | grep postgresql
postgresql8.4-devel-8.4.11-1.mga2
postgresql8.4-server-8.4.11-1.mga2
postgresql8.4-8.4.11-1.mga2
postgresql-jdbc-9.0.801-1.mga2
[root@cortex etc]#


Thank you for that hint. I reinstalled all these packages (urpmi --replacepkgs *) and now it is working.
magfan
 
Posts: 334
Joined: Apr 3rd, '12, 12:33

Re: [SOLVED] After upgrade to mga2 postgresql cannot be star

Postby doktor5000 » Jun 6th, '12, 23:38

Be aware that there are three different postgresql versions in Mageia currently. Just FYI.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18056
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: [SOLVED] After upgrade to mga2 postgresql cannot be star

Postby magfan » Jun 8th, '12, 14:30

That is true but the automatic upgrade does not let me choose anyway. SEP sesam requires PostgreSQL 8.3 but once PostgreSQL was running I had to change only two system settings to run sesam with the newer version.
magfan
 
Posts: 334
Joined: Apr 3rd, '12, 12:33


Return to Basic support

Who is online

Users browsing this forum: No registered users and 1 guest

cron