Upgrade from 5.x to 6.0 - Revision history

T.lamprecht at 08:25, 29 June 2023

2023-06-29T08:25:28Z

← Older revision		Revision as of 08:25, 29 June 2023
Line 129:		Line 129:

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

			[[Category: Upgrade]]

Stoiko Ivanov: /* For Clusters */

2021-05-19T13:10:17Z

For Clusters

← Older revision		Revision as of 13:10, 19 May 2021
Line 67:		Line 67:
	* Then proceed by upgrading all nodes sequentially.		* Then proceed by upgrading all nodes sequentially.
	* The mail gateway service is provided by the other nodes, currently not being upgraded.		* The mail gateway service is provided by the other nodes, currently not being upgraded.
			* Certain operations (for example config changes) will only work once all nodes have been upgraded.

	=== Upgrade The System ===		=== Upgrade The System ===

Stoiko Ivanov: /* Service Failure Caused By Apparmor Featureset Missmatch */

2020-08-26T15:29:34Z

Service Failure Caused By Apparmor Featureset Missmatch

← Older revision		Revision as of 15:29, 26 August 2020
Line 118:		Line 118:
	== Service Failure Caused By Apparmor Featureset Missmatch ==		== Service Failure Caused By Apparmor Featureset Missmatch ==
	Debian Buster installs apparmor, if you still have the Debian stock kernel installed (<code>linux-image-4.19.0-5-amd64</code> recommends apparmor), due to a mismatch between the apparmor featureset in the stock kernel and the pve-kernel (which Proxmox Mailgateway uses) certain important services (e.g. <code>clamav</code>) do not start. Currently you can mitigate the issue in two ways:		Debian Buster installs apparmor, if you still have the Debian stock kernel installed (<code>linux-image-4.19.0-5-amd64</code> recommends apparmor), due to a mismatch between the apparmor featureset in the stock kernel and the pve-kernel (which Proxmox Mailgateway uses) certain important services (e.g. <code>clamav</code>) do not start. Currently you can mitigate the issue in two ways:
	* uninstall <code>apparmor</code>: <code>apt remove apparmor</code>		* preferred: uninstall <code>apparmor</code>: <code>apt remove apparmor</code>
	* disable feature-pinning in apparmor by commenting out or deleting the line <code>features-file=/usr/share/apparmor-features/features</code> in <code>/etc/apparmor/parser.conf</code>		* disable feature-pinning in apparmor by commenting out or deleting the line <code>features-file=/usr/share/apparmor-features/features</code> in <code>/etc/apparmor/parser.conf</code>

Stoiko Ivanov: s/VE/Mail Gateway/

2020-06-22T13:01:26Z

s/VE/Mail Gateway/

← Older revision		Revision as of 13:01, 22 June 2020
Line 106:		Line 106:
	== General ==		== General ==

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

T.lamprecht: /* In-place Upgrade */

2019-10-10T11:30:38Z

In-place Upgrade

← Older revision		Revision as of 11:30, 10 October 2019
Line 31:		Line 31:
	apt dist-upgrade		apt dist-upgrade

	* Make a valid and tested backup of Proxmox Mail Gateway		* Make a valid and tested backup of Proxmox Mail Gateway, either create and download it from the Webinterface, or do so on the CLI:
	pmgbackup backup		pmgbackup backup

	* At least 1GB free disk space at root mount point.		* At least 1GB free disk space at root mount point.
			* Check [[Upgrade_from_5.x_to_6.0#Potential_issues\|known upgrade issues]]

	In-place upgrades are done with apt. '''Familiarity with apt is required to proceed with this upgrade mechanism. '''		In-place upgrades are done with apt. '''Familiarity with apt is required to proceed with this upgrade mechanism. '''

T.lamprecht: /* General */

2019-10-10T11:26:59Z

General

← Older revision		Revision as of 11:26, 10 October 2019
Line 109:		Line 109:

	Especially the [https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#openssl-defaults OpenSSL default version and security level raised] and [https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#su-environment-variables Semantics for using environment variables for su changed]		Especially the [https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#openssl-defaults OpenSSL default version and security level raised] and [https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#su-environment-variables Semantics for using environment variables for su changed]


	== Postgres And Other Template Modifications ==		== Postgres And Other Template Modifications ==

T.lamprecht: /* Potential issues */ copy over general notes from PVE (Upgrade specific issues for buster)

2019-10-10T11:26:50Z

Potential issues: copy over general notes from PVE (Upgrade specific issues for buster)

← Older revision		Revision as of 11:26, 10 October 2019
Line 102:		Line 102:

	= Potential issues =		= Potential issues =

			== General ==

			As a Debian based Distribution, Proxmox VE is affected by most issues and changes affecting Debian.
			So ensure to read the [https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html Upgrade specific issues for buster]

			Especially the [https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#openssl-defaults OpenSSL default version and security level raised] and [https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#su-environment-variables Semantics for using environment variables for su changed]


	== Postgres And Other Template Modifications ==		== Postgres And Other Template Modifications ==

T.lamprecht: /* Potential issues */ Add/Transform to headings for each potential issue to highlight them more

2019-09-19T07:33:54Z

Potential issues: Add/Transform to headings for each potential issue to highlight them more

← Older revision		Revision as of 07:33, 19 September 2019
Line 103:		Line 103:
	= Potential issues =		= Potential issues =

			== Postgres And Other Template Modifications ==
	* If you've modified the configuration template for postgresql (<code>/var/lib/pmg/templates/postgresql.conf</code>), make sure to compare and update your copy in <code>/etc/pmg/templates/</code>		If you've modified the configuration template for postgresql (<code>/var/lib/pmg/templates/postgresql.conf</code>), make sure to compare and update your copy in <code>/etc/pmg/templates/</code>

	* Also compare all other templates you've overriden for new changes through the packages		Also compare all other templates you've overriden for new changes through the packages.

			== Service Failure Caused By Apparmor Featureset Missmatch ==
	* Debian Buster installs apparmor, if you still have the Debian stock kernel installed (<code>linux-image-4.19.0-5-amd64</code> recommends apparmor), due to a mismatch between the apparmor featureset in the stock kernel and the pve-kernel (which Proxmox Mailgateway uses) certain important services (e.g. <code>clamav</code>) do not start. Currently you can mitigate the issue in two ways:		Debian Buster installs apparmor, if you still have the Debian stock kernel installed (<code>linux-image-4.19.0-5-amd64</code> recommends apparmor), due to a mismatch between the apparmor featureset in the stock kernel and the pve-kernel (which Proxmox Mailgateway uses) certain important services (e.g. <code>clamav</code>) do not start. Currently you can mitigate the issue in two ways:
	** uninstall <code>apparmor</code>: <code>apt remove apparmor</code>
	** ~~disable feature-pinning in apparmor by commenting out or deleting the line~~ <code>~~features-file=/usr/share/~~apparmor~~-features/features~~</code> in <code>~~/etc/~~apparmor~~/parser.conf~~</code>		* uninstall <code>apparmor</code>: <code>apt remove apparmor</code>
			* disable feature-pinning in apparmor by commenting out or deleting the line <code>features-file=/usr/share/apparmor-features/features</code> in <code>/etc/apparmor/parser.conf</code>

			== Logrotation (rsyslog) ==
	* If you've modified <code>/etc/logrotate.d/rsyslog</code> make sure to compare the file upon upgrade - the <code>postrotate</code> script changed. Without the new script logrotation does not work which also breaks the tracking center. The <code>postrotate</code> script needs to be:		If you've modified <code>/etc/logrotate.d/rsyslog</code> make sure to compare the file upon upgrade - the <code>postrotate</code> script changed. Without the new script logrotation does not work which also breaks the tracking center. The <code>postrotate</code> script needs to be:
	/usr/lib/rsyslog/rsyslog-rotate		/usr/lib/rsyslog/rsyslog-rotate

Stoiko Ivanov: /* Potential issues */

2019-09-13T18:02:24Z

Potential issues

← Older revision		Revision as of 18:02, 13 September 2019
Line 107:		Line 107:
	* Also compare all other templates you've overriden for new changes through the packages		* Also compare all other templates you've overriden for new changes through the packages

	* Debian Buster installs apparmor, if you still have the Debian stock kernel installed (<code>linux-image-4.19.0-5-amd64</code> recommends apparmor), due to a mismatch between the apparmor featureset in the stock kernel and the pve-kernel (which Proxmox Mailgateway uses) certain important services (e.g. <code>clamav</code>) do not start. Currently ~~uninstall~~ ~~<code>apparmor</code>~~ in ~~that~~ ~~situation~~:		* Debian Buster installs apparmor, if you still have the Debian stock kernel installed (<code>linux-image-4.19.0-5-amd64</code> recommends apparmor), due to a mismatch between the apparmor featureset in the stock kernel and the pve-kernel (which Proxmox Mailgateway uses) certain important services (e.g. <code>clamav</code>) do not start. Currently you can mitigate the issue in two ways:
	apt remove apparmor		** uninstall <code>apparmor</code>: <code>apt remove apparmor</code>
			** disable feature-pinning in apparmor by commenting out or deleting the line <code>features-file=/usr/share/apparmor-features/features</code> in <code>/etc/apparmor/parser.conf</code>

			* If you've modified <code>/etc/logrotate.d/rsyslog</code> make sure to compare the file upon upgrade - the <code>postrotate</code> script changed. Without the new script logrotation does not work which also breaks the tracking center. The <code>postrotate</code> script needs to be:
			/usr/lib/rsyslog/rsyslog-rotate

	= External links =		= External links =

T.lamprecht: /* Potential issues */

2019-08-27T10:47:41Z

Potential issues

← Older revision		Revision as of 10:47, 27 August 2019
Line 107:		Line 107:
	* Also compare all other templates you've overriden for new changes through the packages		* Also compare all other templates you've overriden for new changes through the packages

	* Debian Buster installs apparmor, if you still have the Debian stock kernel installed (<code>linux-image-4.19.0-5-amd64</code> recommends apparmor), due to a mismatch between the apparmor featureset in		* Debian Buster installs apparmor, if you still have the Debian stock kernel installed (<code>linux-image-4.19.0-5-amd64</code> recommends apparmor), due to a mismatch between the apparmor featureset in the stock kernel and the pve-kernel (which Proxmox Mailgateway uses) certain important services (e.g. <code>clamav</code>) do not start. Currently uninstall <code>apparmor</code> in that situation:
	the stock kernel and the pve-kernel (which Proxmox Mailgateway uses) certain important services (e.g. <code>clamav</code>) do not start. Currently uninstall <code>apparmor</code> in that situation:
	apt remove apparmor		apt remove apparmor