Upgrade ERROR

[TFrenz]

Hallo,
ich will das Mailgateway von V7.3 auf V8 heben.
Beim Befehl pmg7to8 kommt aber ein Fehler das postgres version 11 und nicht version 13 ist.
Wie kann das behoben werden?
Das Gateway ist auf dem aktuellen stand 7.3-2

root@mta:~# pmgversion
pmg-api/7.3-6/5a2550b8 (running kernel: 5.15.107-2-pve)
root@mta:~# pmg7to8
= CHECKING VERSION INFORMATION FOR PMG PACKAGES =

Checking for package updates..
PASS: all packages up-to-date

Checking proxmox-mailgateway package version..
PASS: proxmox-mailgateway package has version >= 7.3-2

Checking running kernel version..
PASS: running kernel '5.15.107-2-pve' is considered suitable for upgrade.
INFO: Checking if the cluster nodes are in sync
SKIP: no cluster, no sync status to check
FAIL: Running postgres version '11' is not '13', was a previous upgrade left unfinished?
WARN: Not upgraded but core services still active. Consider stopping and masking them for the upgrade:
    postfix
    pmg-smtp-filter
    pmgpolicy
    pmgdaemon
    pmgproxy

= MISCELLANEOUS CHECKS =

SKIP: No SSH config file found.
INFO: Checking for supported & active NTP service..
WARN: systemd-timesyncd is not the best choice for time-keeping on servers, due to only applying updates on boot.
  It's recommended to use one of:
    * chrony
    * ntpsec
    * openntpd

INFO: Checking if the local node's hostname 'mta' is resolvable..
INFO: Checking if resolved IP is configured on local node..
PASS: Resolved node IP '192.168.188.45' configured and active on single interface.
INFO: Check node certificate's RSA key size
PASS: Certificate 'pmg-api.pem' passed Debian Busters (and newer) security level for TLS connections (4096 >= 2048)
PASS: Certificate 'pmg-tls.pem' passed Debian Busters (and newer) security level for TLS connections (4096 >= 2048)
INFO: Checking for package repository suite mismatches..
PASS: found no suite mismatch
INFO: Checking bootloader configuration...
SKIP: not yet upgraded, no need to check the presence of systemd-boot

= SUMMARY =

TOTAL:    13
PASSED:   7
SKIPPED:  3
WARNINGS: 2
FAILURES: 1

ATTENTION: Please check the output for detailed information!
Try to solve the problems one at a time and then run this checklist tool again.
root@mta:~#

 

[hawkeye]

Anleitung befolgt? Siehe Preconditions ...

(Auszug)

• Upgraded to the latest version of Proxmox Mail Gateway 7., see the roadmap for potential important changes in the stable release.Use apt update and apt dist-upgrade (still with Debian Bullseye repos setup) to upgrade to latest 7.3
• Verify version:You can check the web-interface (reload) at the top, or use pmgversion. Both must show a version with 7.3-6 (or newer), for example something like pmg-api/7.3-6/... for the CLI command.If you still see an older version, you should ensure that you have valid package repositories configured.

 

[dcsapak]

wahrscheinilch ist das upgrade von 6 zu 7 nicht fertiggemacht worden? siehe https://pmg.proxmox.com/wiki/index.php/Upgrade_from_6.x_to_7.0
edit: speziell https://pmg.proxmox.com/wiki/index.php/Upgrade_from_6.x_to_7.0#Upgrade_the_PostgreSQL_database

 

[TFrenz]

Hallo, richtig, es wurde das Upgrade 6 zu 7 nicht richtig beendet.
Wurde nun nachgezogen.

Aber nun kommen 2 Warnungen, können die Ignoriert werden?

root@mta:~# pmg7to8
= CHECKING VERSION INFORMATION FOR PMG PACKAGES =

Checking for package updates..
PASS: all packages up-to-date

Checking proxmox-mailgateway package version..
PASS: proxmox-mailgateway package has version >= 7.3-2

Checking running kernel version..
PASS: running kernel '5.15.107-2-pve' is considered suitable for upgrade.
INFO: Checking if the cluster nodes are in sync
SKIP: no cluster, no sync status to check
PASS: Before upgrade and running postgres version is 13.
WARN: Not upgraded but core services still active. Consider stopping and masking them for the upgrade:
    postfix
    pmg-smtp-filter
    pmgpolicy
    pmgdaemon
    pmgproxy

= MISCELLANEOUS CHECKS =

SKIP: No SSH config file found.
INFO: Checking for supported & active NTP service..
WARN: systemd-timesyncd is not the best choice for time-keeping on servers, due to only applying updates on boot.
  It's recommended to use one of:
    * chrony
    * ntpsec
    * openntpd

INFO: Checking if the local node's hostname 'mta' is resolvable..
INFO: Checking if resolved IP is configured on local node..
PASS: Resolved node IP '192.168.xxx.yyy' configured and active on single interface.
INFO: Check node certificate's RSA key size
PASS: Certificate 'pmg-api.pem' passed Debian Busters (and newer) security level for TLS connections (4096 >= 2048)
PASS: Certificate 'pmg-tls.pem' passed Debian Busters (and newer) security level for TLS connections (4096 >= 2048)
INFO: Checking for package repository suite mismatches..
PASS: found no suite mismatch
INFO: Checking bootloader configuration...
SKIP: not yet upgraded, no need to check the presence of systemd-boot

= SUMMARY =

TOTAL:    13
PASSED:   8
SKIPPED:  3
WARNINGS: 2
FAILURES: 0

ATTENTION: Please check the output for detailed information!

 

[Stoiko Ivanov]

steht recht gut in der upgrade Anleitung beschrieben:
https://pmg.proxmox.com/wiki/index.php/Upgrade_from_7_to_8

 

[TFrenz]

Danke, nun habe ich es verstanden in welcher Reihenfolge ich vorgehen muss
Das pmg7to8 macht nur einen Prüflauf, dann kommen die Befehle
Das Upgrade läuft gerade.