Issue Cannot update from Plesk Obsidian 18.0.69

[Aspire]

Server operating system version

Ubuntu 22.04

Plesk version and microupdate number

Plesk Obsidian 18.0.69 #4

We installed a Plesk system from AWS marketplace about a year ago, but cannot update it.
The EMI was: Plesk Obsidian 'Bring Your Own License' (Ubuntu 22.04 aarch64) 20250430.0715-7917ca0b-ac94-416a-9357-1d45f6bf9b65

Update attempt returns:
There are no products for your operating system
( 'Ubuntu' 'Linux' '24.04' 'aarch64' ) available
from the selected source.

Because the reason for the update was to patch PHP 8.3.26 , I installed PHP 8.3.36 and switched Plesk over to it,

We have around 20 sites on that EC2 and all are running again, but it's a wee bit unstable. With the occassional MariaDB lockup and probably related timeouts.

It was rock-solid before, but before I go retuning it, I'd like to get Plesk updated.

What can I do form here?

 

[tessa67]

Hi,

Look at the error again: it says ‘Ubuntu’ ‘Linux’ ‘24.04’ ‘aarch64’, not 22.04. Plesk doesn’t have packages for that combo. Ubuntu 24.04 is only supported on x86-64, and Plesk has said in the forum that there are no plans for 24.04/26 on ARM. ARM support is supposed to end together with Ubuntu 22.04 in April 2027.

So first, check what your server really is:

cat /etc/os-release
uname -m
plesk version
grep -rhE “^(deb |URIs:|Suites:)” /etc/apt/sources.list /etc/apt/sources.list.d/

If it says 24.04: at some point the OS got upgraded (do-release-upgrade or apt), and Plesk is now on an unsupported platform. That could also explain the flakiness, since you’d have a mix of packages from both releases. Your options:

1. Roll back to an EBS snapshot/AMI from before the OS upgrade, if you have one. Downgrading Ubuntu isn’t really a thing.
2. Spin up a fresh Ubuntu 22.04 aarch64 instance and move everything over with the Plesk Migrator. That works, but only until April 2027.
3. Spin up an x86-64 instance with Ubuntu 24.04 and migrate with the Plesk Migrator. That’s the only long-term supported route.

If it says 22.04: then the installer is picking up 24.04 from somewhere else (leftover repo config maybe). Post the output of the commands above and we can dig further.

About the MariaDB lockups: I wouldn’t tune anything yet. Check the logs first:

journalctl -u mariadb --since “7 days ago” | tail -n 100
dmesg -T | grep -i -E “out of memory|oom”
free -h

If the OOM killer shows up there, that’s a good lead. It’s just a guess though, so look at the logs before changing anything.

One more question: where did you get PHP 8.3.36 from? Plesk’s own packages or a third-party repo? If it’s a third-party repo, it might be part of the problem.

Sources:

• https://support.plesk.com/hc/en-us/articles/20033524944663
• Question - Plesk Support for ARM (Ubuntu 24/26)

Regards
Tessa

 

[Aspire]

Hi Tessa,
Thanks for the comprehensive reply. You nailed it.

cat /etc/os-release
uname -m
plesk version
grep -rhE “^(deb |URIs:|Suites:)” /etc/apt/sources.list /etc/apt/sources.list.d/

PRETTY_NAME="Ubuntu 24.04.5 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.5 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

aarch64

Product version: Plesk Obsidian 18.0.69.4
OS version: Ubuntu 24.04 aarch64
Build date: 2025/06/03 20:00
Revision: 0ca7a512b8d26c968db3caf91f81ac03aba22842
URIs: Index of /ondrej/php/ubuntu
Suites: noble
deb [signed-by=/etc/apt/keyrings/plesk.gpg] Index of /pool/PSA_18.0.69_17010 jammy extras
deb [signed-by=/etc/apt/keyrings/plesk.gpg] Index of /PHP82_17 jammy all
deb [signed-by=/etc/apt/keyrings/plesk.gpg] Index of /PHP83_17 jammy all
URIs: Index of /ubuntu-ports
Suites: noble noble-updates noble-backports
URIs: Index of /ubuntu-ports
Suites: noble-security

About the MariaDB lockups: I wouldn’t tune anything yet. Check the logs first:

journalctl -u mariadb --since “7 days ago” | tail -n 100
dmesg -T | grep -i -E “out of memory|oom”
free -h

There are a lot of errors here is a sample
Oct 29 15:57:43 positive.aspireconsulting.com.au mariadbd[1481379]: 2026-10-29 15:57:43 0 [Note] Server socket created on IP: '127.0.0.1', port: '3306'.
Oct 29 15:57:43 positive.aspireconsulting.com.au mariadbd[1481379]: 2026-10-29 15:57:43 0 [Note] /usr/sbin/mariadbd: ready for connections.
Oct 29 15:57:43 positive.aspireconsulting.com.au mariadbd[1481379]: Version: '10.11.14-MariaDB-0ubuntu0.24.04.1' socket: '/run/mysqld/mysqld.sock' port: 3306 Ubuntu 24.04
Oct 29 15:57:43 positive.aspireconsulting.com.au systemd[1]: Started mariadb.service - MariaDB 10.11.14 database server.
Oct 29 15:57:43 positive.aspireconsulting.com.au /etc/mysql/debian-start[1481404]: Upgrading MariaDB tables if necessary.
Oct 29 15:57:43 positive.aspireconsulting.com.au mariadbd[1481379]: 2026-10-29 15:57:43 10 [ERROR] mariadbd: Table './wp_pipk2/Q9uxhc_options' is marked as crashed and should be repaired
Oct 29 15:57:43 positive.aspireconsulting.com.au mariadbd[1481379]: 2026-10-29 15:57:43 10 [Warning] Checking table: './wp_pipk2/Q9uxhc_options'
Oct 29 15:57:43 positive.aspireconsulting.com.au mariadbd[1481379]: 2026-10-29 15:57:43 20 [ERROR] mariadbd: Table './wp_pipk2/Q9uxhc_wfStatus' is marked as crashed and should be repaired
Oct 29 15:57:43 positive.aspireconsulting.com.au mariadbd[1481379]: 2026-10-29 15:57:43 20 [Warning] Checking table: './wp_pipk2/Q9uxhc_wfStatus'
Oct 29 15:57:43 positive.aspireconsulting.com.au mariadbd[1481379]: 2026-10-29 15:57:43 30 [ERROR] mariadbd: Table './wp_uhauf/uXVdn_postmeta' is marked as crashed and should be repaired
Oct 29 15:57:43 positive.aspireconsulting.com.au mariadbd[1481379]: 2026-10-29 15:57:43 30 [Warning] Checking table: './wp_uhauf/uXVdn_postmeta'
Oct 29 15:57:43 positive.aspireconsulting.com.au mariadbd[1481379]: 2026-10-29 15:57:43 35 [ERROR] mariadbd: Table './wp_f8di9/jW8uw_actionscheduler_claims' is marked as crashed and should be repaired
Oct 29 15:57:43 positive.aspireconsulting.com.au mariadbd[1481379]: 2026-10-29 15:57:43 35 [Warning] Checking table: './wp_f8di9/jW8uw_actionscheduler_claims'
Oct 29 15:57:44 positive.aspireconsulting.com.au /etc/mysql/debian-start[1481443]: Checking for insecure root accounts.
Oct 29 15:57:44 positive.aspireconsulting.com.au mariadbd[1481379]: 2026-10-29 15:57:44 20 [ERROR] mariadbd: Table './wp_pipk2/Q9uxhc_actionscheduler_actions' is marked as crashed and should be repaired

dmesg -T | grep -i -E “out of memory|oom”

[Thu Oct 29 15:57:38 2026] systemd invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0
[Thu Oct 29 15:57:38 2026] oom_kill_process+0x108/0x380
[Thu Oct 29 15:57:38 2026] __alloc_pages_may_oom+0x144/0x218
[Thu Oct 29 15:57:38 2026] [ pid ] uid tgid total_vm rss rss_anon rss_file rss_shmem pgtables_bytes swapents oom_score_adj name
[Thu Oct 29 15:57:38 2026] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=init.scope,mems_allowed=0,global_oom,task_memcg=/system.slice/mariadb.service,task=mariadbd,pid=1478102,uid=115
[Thu Oct 29 15:57:38 2026] Out of memory: Killed process 1478102 (mariadbd) total-vm:4505160kB, anon-rss:2028864kB, file-rss:2488kB, shmem-rss:0kB, UID:115 pgtables:4548kB oom_score_adj:0

free -h

total used free shared buff/cache available
Mem: 15Gi 10Gi 2.5Gi 227Mi 3.0Gi 5.1Gi
Swap: 0B 0B 0B

One more question: where did you get PHP 8.3.36 from? Plesk’s own packages or a third-party repo? If it’s a third-party repo, it might be part of the problem.

It was installed from l Ondřej Surý PPA repository

I agree, the best long term solution is to change platform top x86/x64. As disappointing as that solution is.
As AWS seem to be promoting away from it for new EC2 instances.