Upgrade from 7 to 8 - Revision history

Stoiko Ivanov: /* Systemd-boot (for ZFS on root and UEFI systems only) */

2026-01-28T13:46:40Z

Systemd-boot (for ZFS on root and UEFI systems only)

← Older revision		Revision as of 13:46, 28 January 2026
Line 220:		Line 220:
	== Systemd-boot (for ZFS on root and UEFI systems only) ==		== Systemd-boot (for ZFS on root and UEFI systems only) ==

	Systems booting via UEFI from a ZFS on root setup should install the <code>systemd-boot</code> package after the upgrade. You will get a Warning from the <code>~~pve7to8~~</code> script after the upgrade if your system is affected - in all other cases you can safely ignore this point.		Systems booting via UEFI from a ZFS on root setup should install the <code>systemd-boot</code> package after the upgrade. You will get a Warning from the <code>pmg7to8</code> script after the upgrade if your system is affected - in all other cases you can safely ignore this point.

	The <code>systemd-boot</code> was split out from the <code>systemd</code> package for Debian Bookworm based releases. It won't get installed automatically upon upgrade from Proxmox Mail Gateway 7.3 as it can cause trouble on systems not booting from UEFI with ZFS on root setup by the Proxmox Mail Gateway installer.		The <code>systemd-boot</code> was split out from the <code>systemd</code> package for Debian Bookworm based releases. It won't get installed automatically upon upgrade from Proxmox Mail Gateway 7.3 as it can cause trouble on systems not booting from UEFI with ZFS on root setup by the Proxmox Mail Gateway installer.

Stoiko Ivanov: fix link to potential issues, provision for linking to all minor-releases known issues

2024-02-26T12:13:23Z

fix link to potential issues, provision for linking to all minor-releases known issues

← Older revision		Revision as of 12:13, 26 February 2024
Line 47:		Line 47:

	* At least 5 GB free disk space on root mount point.		* At least 5 GB free disk space on root mount point.
	* Check [[~~Upgrade_from_7.x_to_8.0~~#Potential_issues\|known upgrade issues]]		* Check [[#Potential_issues\|known upgrade issues]]

	In-place upgrades are carried out using APT. '''Familiarity with APT is required to proceed with this upgrade mechanism. '''		In-place upgrades are carried out using APT. '''Familiarity with APT is required to proceed with this upgrade mechanism. '''
Line 175:		Line 175:
	Thus, ensure to read the [https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html upgrade specific issues for Bookworm].		Thus, ensure to read the [https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html upgrade specific issues for Bookworm].

	Please also check the known issue list ~~from~~ the Proxmox Mail Gateway 8.0 ~~changelog~~: ~~https://pmg.proxmox.com/wiki/Roadmap#8.0-known-issues~~		Please also check the known issue list for the Proxmox Mail Gateway 8.X minor releases:
			* https://pmg.proxmox.com/wiki/Roadmap#8.0-known-issues

	== Breaking Changes ==		== Breaking Changes ==

Stoiko Ivanov: /* Update the configured APT repositories */

2023-08-16T08:08:26Z

Update the configured APT repositories

← Older revision		Revision as of 08:08, 16 August 2023
Line 86:		Line 86:

	echo "deb https://enterprise.proxmox.com/debian/pmg bookworm pmg-enterprise" > /etc/apt/sources.list.d/pmg-enterprise.list		echo "deb https://enterprise.proxmox.com/debian/pmg bookworm pmg-enterprise" > /etc/apt/sources.list.d/pmg-enterprise.list

			For the no-subscription repository, see [https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmg_package_repositories Package Repositories].
			Rather than commenting out/removing the PMG 7.x repositories, as was previously mentioned, you could also run the following command to update to the Proxmox Mail Gateway 8 repositories:
			sed -i -e 's/bullseye/bookworm/g' /etc/apt/sources.list.d/pmg-install-repo.list

	Make sure to also update any extra files that you added to <code>/etc/apt/sources.list.d/</code> to Bookworm accordingly.		Make sure to also update any extra files that you added to <code>/etc/apt/sources.list.d/</code> to Bookworm accordingly.

Stoiko Ivanov: /* Network Interface Name Change */

2023-07-05T08:25:47Z

Network Interface Name Change

← Older revision		Revision as of 08:25, 5 July 2023
Line 198:		Line 198:
	=== Network Interface Name Change ===		=== Network Interface Name Change ===

	Due to the new kernel recognizing more features of some hardware, like for example virtual functions, and interface naming often derives from the PCI(e) address, some NICs may change their name, in which case the network configuration needs to be adapted.		Due to the new kernel recognizing more features of some hardware, like for example virtual functions, and since interface naming often derives from the PCI(e) address, some NICs may change their name, in which case the network configuration needs to be adapted.

			This can also happen in virtualized environments (and has been reported with Xen for this upgrade)

	In general, it's recommended to either have an independent remote connection to the Proxmox Mail Gateways's host console, for example, through the hypervisor in case of a VM or container setup, IPMI or iKVM, or physical access for managing the server even		In general, it's recommended to either have an independent remote connection to the Proxmox Mail Gateways's host console, for example, through the hypervisor in case of a VM or container setup, IPMI or iKVM, or physical access for managing the server even

T.lamprecht: /* Continuously use the pmg7to8 checklist script */

2023-07-01T13:36:42Z

Continuously use the pmg7to8 checklist script

← Older revision		Revision as of 13:36, 1 July 2023
Line 66:		Line 66:

	It is recommended to re-run the script after each attempt to fix an issue. This ensures that the actions taken actually fixed the respective warning.		It is recommended to re-run the script after each attempt to fix an issue. This ensures that the actions taken actually fixed the respective warning.


	=== For clusters ===		=== For clusters ===

T.lamprecht: /* Adapt modified configuration templates to new shipped versions */

2023-06-29T11:42:02Z

Adapt modified configuration templates to new shipped versions

← Older revision		Revision as of 11:42, 29 June 2023
Line 127:		Line 127:

	If configuration templates are used in <code>/etc/pmg/templates</code>, you will see a prompt about the changes in the new version that are not yet incorporated. Review the changes carefully and ensure that only the changes you want are shown in the diff.		If configuration templates are used in <code>/etc/pmg/templates</code>, you will see a prompt about the changes in the new version that are not yet incorporated. Review the changes carefully and ensure that only the changes you want are shown in the diff.

			=== Disable ClamAV On-Access Scanner Service ===

			The new ClamAV on-access scanning service is not useful for Proxmox Mail Gateway setups and is disabled for new installations as it not only slows down the entire system, but also affects the spam and virus detection mechanisms managed by Proxmox Mail Gateway.

			During upgrades, the service may get enabled and will then be marked as failed.
			It is recommended to disable this service:
			systemctl disable clamav-clamonacc.service

	=== Upgrade the PostgreSQL database ===		=== Upgrade the PostgreSQL database ===

T.lamprecht at 08:58, 29 June 2023

2023-06-29T08:58:21Z

← Older revision		Revision as of 08:58, 29 June 2023
Line 157:		Line 157:
	systemctl start pmgmirror pmgtunnel		systemctl start pmgmirror pmgtunnel

		⚫	= Potential Issues =
	= Known issues and deprecations =

		⚫	== General ==

		⚫	As a Debian based Distribution, Proxmox Mail Gateway is affected by most issues and changes affecting Debian.
		⚫	Thus, ensure to read the [https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html upgrade specific issues for Bookworm].

		⚫	Please also check the known issue list from the Proxmox Mail Gateway 8.0 changelog: https://pmg.proxmox.com/wiki/Roadmap#8.0-known-issues

			== Breaking Changes ==

	* Changed defaults for Bayes and AWL		* Changed defaults for Bayes and AWL
Line 172:		Line 181:
	*: if you have modified the template (or copied it without modification) in /etc/pmg/templates/ - make sure to remove the line and/or remove the complete template override (if you don't have any modifications)		*: if you have modified the template (or copied it without modification) in /etc/pmg/templates/ - make sure to remove the line and/or remove the complete template override (if you don't have any modifications)

		⚫	=== Upgrade wants to remove package 'proxmox-mail-gateway' ===
⚫	= Potential ~~issues~~ =

⚫	== General ==

⚫	As a Debian based Distribution, Proxmox Mail Gateway is affected by most issues and changes affecting Debian.
⚫	Thus, ensure to read the [https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html upgrade specific issues for Bookworm].

⚫	Please also check the known issue list from the Proxmox Mail Gateway 8.0 changelog: https://pmg.proxmox.com/wiki/Roadmap#8.0-known-issues


⚫	==== Upgrade wants to remove package 'proxmox-mail-gateway' ====

	If you have installed Proxmox Mail Gateway on top of a plain Debian Bookworm (without using the Proxmox Mail Gateway ISO), you may have installed the package 'linux-image-amd64', which conflicts with current 8.x setups. To solve this, you have to remove this package with		If you have installed Proxmox Mail Gateway on top of a plain Debian Bookworm (without using the Proxmox Mail Gateway ISO), you may have installed the package 'linux-image-amd64', which conflicts with current 8.x setups. To solve this, you have to remove this package with
Line 188:		Line 187:
	before the dist-upgrade.		before the dist-upgrade.

			== Network ==
	<hr>

	=== Network ===		=== Network Interface Name Change ===

	==== Network Interface Name Change ====

	Due to the new kernel recognizing more features of some hardware, like for example virtual functions, and interface naming often derives from the PCI(e) address, some NICs may change their name, in which case the network configuration needs to be adapted.		Due to the new kernel recognizing more features of some hardware, like for example virtual functions, and interface naming often derives from the PCI(e) address, some NICs may change their name, in which case the network configuration needs to be adapted.
Line 199:		Line 196:
	when its own network doesn't come up after a major upgrade or network change.		when its own network doesn't come up after a major upgrade or network change.

	==== Network Fails on Boot Due to NTPsec Hook ====		=== Network Fails on Boot Due to NTPsec Hook ===

	Some users reported that after the upgrade their network failed to come up cleanly on boot, but worked if triggered manually (e.g., using <code>ifreload -a</code>), when ntpsec was installed.		Some users reported that after the upgrade their network failed to come up cleanly on boot, but worked if triggered manually (e.g., using <code>ifreload -a</code>), when ntpsec was installed.
Line 207:		Line 204:
	The simplest solution might be switching to that via <code>apt install chrony</code>.		The simplest solution might be switching to that via <code>apt install chrony</code>.

		⚫	== Systemd-boot (for ZFS on root and UEFI systems only) ==
	<hr>

⚫	=== Systemd-boot (for ZFS on root and UEFI systems only) ===

	Systems booting via UEFI from a ZFS on root setup should install the <code>systemd-boot</code> package after the upgrade. You will get a Warning from the <code>pve7to8</code> script after the upgrade if your system is affected - in all other cases you can safely ignore this point.		Systems booting via UEFI from a ZFS on root setup should install the <code>systemd-boot</code> package after the upgrade. You will get a Warning from the <code>pve7to8</code> script after the upgrade if your system is affected - in all other cases you can safely ignore this point.
Line 221:		Line 216:
	It is not recommended installing <code>systemd-boot</code> on systems which don't need it, as it would replace <code>grub</code> as bootloader in its <code>postinst</code> script.		It is not recommended installing <code>systemd-boot</code> on systems which don't need it, as it would replace <code>grub</code> as bootloader in its <code>postinst</code> script.

	== External links ==		= External links =

	[https://www.debian.org/releases/bookworm/amd64/release-notes/ Release Notes for Debian 12.0 (bookworm), 64-bit PC]		[https://www.debian.org/releases/bookworm/amd64/release-notes/ Release Notes for Debian 12.0 (bookworm), 64-bit PC]

T.lamprecht: /* Upgrade the system */

2023-06-29T08:54:46Z

Upgrade the system

← Older revision		Revision as of 08:54, 29 June 2023
Line 104:		Line 104:
	apt dist-upgrade		apt dist-upgrade

			During the above step, you will be asked to approve changes to configuration files, where the default config has been updated by their respective package.
	It is not necessary to reboot yet.

			It's suggested to check the difference for each file in question and choose the answer accordingly to what's most appropriate for your setup.

			Common configuration files with changes, and the recommended choices are:
			* <code>/etc/issue</code> -> Proxmox Mail Gateway will auto-generate this file on boot, and it has only cosmetic effects on the login console.
			*: Using the default "No" (keep your currently-installed version) is safe here.

			* <code>/etc/clamav/clamd.conf </code> and <code>/etc/clamav/freshclam.conf</code> -> Those two configuration files are managed by Proxmox Mail Gateway directly, at will be re-generate on any relevant change and on boot.
			*: Using the default "No" (keep your currently-installed version) is safe here.

			* <code>/etc/ssh/sshd_config</code> -> If you have not changed this file manually, the only differences should be a replacement of <code>ChallengeResponseAuthentication no</code> with <code>KbdInteractiveAuthentication no</code> and some irrelevant changes in comments (lines starting with <code>#</code>).
			*: If this is the case, both options are safe, though we would recommend installing the package maintainer's version in order to move away from the deprecated <code>ChallengeResponseAuthentication</code> option. If there are other changes, we suggest to inspect them closely and decide accordingly.

			* <code>/etc/default/grub</code> -> Here you may want to take special care, as this is normally only asked for if you changed it manually, e.g., for adding some kernel command line option.
			*: It's recommended to check the difference for any relevant change, note that changes in comments (lines starting with <code>#</code>) are not relevant.
			*: If unsure, we suggested to selected "No" (keep your currently-installed version)

			It is not necessary to reboot the Proxmox Mail Gateway host yet after the dist-upgrade finished.

	=== Adapt modified configuration templates to new shipped versions ===		=== Adapt modified configuration templates to new shipped versions ===

T.lamprecht at 08:25, 29 June 2023

2023-06-29T08:25:14Z

Show changes

T.lamprecht: reserve

2023-06-26T19:08:30Z

reserve

New page