upgrade from 6.4-4 to 7.3-3 according to wiki fails

J

jppialasse

Member
Jan 5, 2021
1
1
8
124
following https://pmg.proxmox.com/wiki/index.php/Upgrade_from_6.x_to_7.0 to upgrade the process fails.

at the end of the upgrade process you get

dpkg: error processing package pmg-api (--configure): installed pmg-api package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of proxmox-mailgateway: proxmox-mailgateway depends on pmg-api (>= 7.3~); however: Package pmg-api is not configured yet. dpkg: error processing package proxmox-mailgateway (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.31-13+deb11u5) ... Processing triggers for oddjob (0.34.6-1) ... Processing triggers for ca-certificates (20210119) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Processing triggers for initramfs-tools (0.140) ... update-initramfs: Generating /boot/initrd.img-5.15.102-1-pve Running hook script 'zz-proxmox-boot'.. Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace.. No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync. Errors were encountered while processing: pmg-api proxmox-mailgateway E: Sub-process /usr/bin/dpkg returned an error code (1)

it happends that trying to then do apt install proxmox-mailgateway you get a more verbose message telling that pmg-api fails because of a masked service

workaround is

Code: 
systemctl unmask  pmg-smtp-filter
apt install proxmox-mailgateway

ulitmately I feel like this is either a documentation bug either a bug in the post script that test for service not being masked...
 
  • Like
Reactions: Stoiko Ivanov
could you please share the complete /var/log/apt/term.log (and /var/log/apt/history.log)?

do you have any modifications on the system - config wise?

thanks!
 
Ok - I think we found out what happend:
* with the changes between 7.2 and 7.3 we modified the postfix templates - this results in `pmgconfig sync -restart 1` (which is called by the postinst script of pmg-api) to try to reload postfix - which in turn fails due to the masking from the guide

There is a patch on the pmg-devel list which addresses the issue:
https://lists.proxmox.com/pipermail/pmg-devel/2023-March/002385.html

once it has been applied the issue should not occur anymore

Thanks for the report!
 
seems it did not get applied until now - the workaround described above should still work though

Thanks for the reminder!
 
  • Like
Reactions: Tyrant82
Can you please give a follow up when this is fixed so i can safely do the upgrade process?

Br,
 
You must log in or register to reply here.
Top Bottom