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

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
  • well we figured out that whenever we restarted pmx we got 'fresh' results in the quarantine

    but queue runner still never startedqueuerunner.jpg

    we couldn't get it started via dashboard -> queue runner -> start/restart either

    but we managed to start it via local services -> queue runner -> restart

    queuerunner2b.jpg

    and now the quarantine seems to be populated normaly ..

    :44965
Reply
  • well we figured out that whenever we restarted pmx we got 'fresh' results in the quarantine

    but queue runner still never startedqueuerunner.jpg

    we couldn't get it started via dashboard -> queue runner -> start/restart either

    but we managed to start it via local services -> queue runner -> restart

    queuerunner2b.jpg

    and now the quarantine seems to be populated normaly ..

    :44965
Children
No Data