Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 0 subscribers
  • Views 18401 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Upgrade Puremessage to version 6 - migration error

tgermiat

Upgrading Puremessage for UNIX 5.61 to 6.  Install goes flawlessly.  Running pmx-v6-migrate ends in error, although the policy and white-listd senders do migrate before the error.  Not a clue how to get past this.  Full run of utility below.

---------------------------------------------------------------------------------------------------------------------------------------------------------------

1. [Recommended] Migrate Configuration (error)

2. ([Recommended] Migrate Log Search Files & Data)

3. ([Optional] Database & Quarantine)

4. Exit

Enter selection: 1

Migrating your PureMessage 5 configuration will overwrite your current settings.

Would you like to proceed (yes/no)? [yes]

Copying configuration files

Finalizing changes

Checking mail_sender value format

Updating cache info

Creating cdb files for maps, list and multilists

Migrating group data

ERROR: Command failed (1): 'su - pmx -c '/opt/pmx/bin/pmx-env pmx-database start'': pg_ctl: invalid data in PID file "/opt/pmx/postgres/var/data/postmaster.pid"

Migration script has terminated with error.

Review the log file for more information.

Press enter to continue...

:36407


This thread was automatically locked due to age.
Parents
  • 0

    Hello,

    Can you take a look at the .pid file, it should contain information, including the PID for postgres:

    cat /opt/pmx/postgres/var/data/postmaster.pid

    Is postgres actually running?  Can you find this PID?  Perhaps the .pid file is corrupt, or postgres didn't shutdown cleanly.   If postgres isn't running we don't actually need this file.  So, assuming you aren't running any other postgresql databases on this server, it should be safe to follow this process:

    su - pmx -c "pmx-database stop"

    ps auxwww | grep postgres

    killall postgres

    ps auxwww | grep postgres

    mv /opt/pmx/postgres/var/data/postmaster.pid /opt/pmx/postgres/var/data/postmaster.pid.bak

    Once you're sure that postgres is stopped and the .pid file is gone, just re-run pmx-v6-migrate (as the pmx6 user).

    Hope this helps!

    Tom.

    :36471
Reply
  • 0

    Hello,

    Can you take a look at the .pid file, it should contain information, including the PID for postgres:

    cat /opt/pmx/postgres/var/data/postmaster.pid

    Is postgres actually running?  Can you find this PID?  Perhaps the .pid file is corrupt, or postgres didn't shutdown cleanly.   If postgres isn't running we don't actually need this file.  So, assuming you aren't running any other postgresql databases on this server, it should be safe to follow this process:

    su - pmx -c "pmx-database stop"

    ps auxwww | grep postgres

    killall postgres

    ps auxwww | grep postgres

    mv /opt/pmx/postgres/var/data/postmaster.pid /opt/pmx/postgres/var/data/postmaster.pid.bak

    Once you're sure that postgres is stopped and the .pid file is gone, just re-run pmx-v6-migrate (as the pmx6 user).

    Hope this helps!

    Tom.

    :36471
Children
No Data
Unfiltered HTML