george wrote:

I suspect that doing so would be quite safe, as long as the version of PostgreSQL stays the same.

The one you need to take care of is Dovecot, not PostgreSQL.

- Setup a new VM with Alma 9 first, so that you have a working Dovecot config files for reference.
- Then upgrade Alma 8 in place.
- If there's something wrong, check log files to figure it out by comparing config files on both machines.

If there's something you need to change after in-place OS upgrade, please do let us know, so that we can publish a tutorial to benefit other iRedMail users.

Zhang, I have much of the upgrade-in-place documented and I'll happily put it on this thread.  Dovecot seems to have moved easily.  The upgrade of Postgresql required a bit more effort, but I documented that as well.  For some reason python3-sqlalchemy either wasn't installed on my test system or it got uninstalled in the upgrade.

The last item I need to get worked out has to do with the ebpf.plugin that seems to be part of netdata.  I see groups of entries in /var/log/messages like this:

Nov  6 14:04:20 mail-2.local.com netdata[8983]: time=2024-11-06T14:04:20.739-05:00 comm=ebpf.plugin source=collector level=warning tid=8983  msg="Failed to initialize journal. Using stderr."
Nov  6 14:04:20 mail-2.local.com netdata[8983]: time=2024-11-06T14:04:20.740-05:00 comm=ebpf.plugin source=collector level=info errno="2, No such file or directory" tid=8983  msg="Does not have a configuration file inside `/opt/netdata/etc/netdata/ebpf.d.conf. It will try to load stock file."
Nov  6 14:04:20 mail-2.local.com netdata[8983]: time=2024-11-06T14:04:20.751-05:00 comm=ebpf.plugin source=collector level=info tid=8983  msg="Name resolution is disabled, collector will not parse \"hostnames\" list."
Nov  6 14:04:20 mail-2.local.com netdata[8983]: time=2024-11-06T14:04:20.752-05:00 comm=ebpf.plugin source=collector level=info errno="2, No such file or directory" tid=8983  msg="Cannot read process groups configuration file '/opt/netdata/etc/netdata/apps_groups.conf'. Will try '/opt/netdata/usr/lib/netdata/conf.d/apps_groups.conf'"
Nov  6 14:04:20 mail-2.local.com netdata[8983]: time=2024-11-06T14:04:20.754-05:00 comm=ebpf.plugin source=collector level=info errno="2, No such file or directory" tid=8983  msg="PROCFILE: Cannot open file '/proc/8879/status'"
Nov  6 14:04:20 mail-2.local.com netdata[8983]: time=2024-11-06T14:04:20.755-05:00 comm=ebpf.plugin source=collector level=error tid=8983  msg="Cannot open /proc/8879/status"
Nov  6 14:04:20 mail-2.local.com netdata[8983]: libbpf: elf: failed to open /opt/netdata/usr/libexec/netdata/plugins.d/ebpf.d/rnetdata_ebpf_softirq.5.14.rhf.o: No such file or directory
Nov  6 14:04:41 mail-2.local.com kernel: ebpf.plugin[8983]: segfault at 10 ip 000000000095caad sp 00007ffd2cb63f58 error 4 in ebpf.plugin[401000+571000] likely on CPU 0 (core 0, socket 0)

I don't think these are normal.  Do you have any suggestion for what would be causing these?

Thank you.

I suspect that doing so would be quite safe, as long as the version of PostgreSQL stays the same.

The one you need to take care of is Dovecot, not PostgreSQL.

- Setup a new VM with Alma 9 first, so that you have a working Dovecot config files for reference.
- Then upgrade Alma 8 in place.
- If there's something wrong, check log files to figure it out by comparing config files on both machines.

If there's something you need to change after in-place OS upgrade, please do let us know, so that we can publish a tutorial to benefit other iRedMail users.

I am wondering if anyone has attempted to do an in-place upgrade of the underlying Linux system from Alma/Rocky/CentOS/RHEL 8 to v9.  I suspect that doing so would be quite safe, as long as the version of PostgreSQL stays the same.

Has anyone tested this yet?

Zhang, do you think this is advisable to do?  Or do you recommend that a new server be set up with iRedMail of the same version and then we do a migration of all the data?

Thank you.