• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Forwarded to devs Plesk updates when running Ubuntu 24.04.1 LTS - Possible Installer Plesk bug

learning_curve

learning_curve

Golden Pleskian
Username:

TITLE

Plesk updates when running Ubuntu 24.04.1 LTS - Possible Installer Plesk bug

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian 18.0.64 / Ubuntu 24.04.1 / Plesk Update Process

PROBLEM DESCRIPTION

The complete data set, problem and temp workaround, is shown in the first two posts, in this thread:
Issue - Plesk updates when running Ubuntu 24.04.1 LTS - Possible Installer Plesk bug?

STEPS TO REPRODUCE

The complete data set, problem and temp workaround, is shown in the first two posts, in this thread:
Issue - Plesk updates when running Ubuntu 24.04.1 LTS - Possible Installer Plesk bug?

ACTUAL RESULT

The complete data set, problem and temp workaround, is shown in the first two posts, in this thread:
Issue - Plesk updates when running Ubuntu 24.04.1 LTS - Possible Installer Plesk bug?

EXPECTED RESULT

The complete data set, problem and temp workaround, is shown in the first two posts, in this thread:
Issue - Plesk updates when running Ubuntu 24.04.1 LTS - Possible Installer Plesk bug?

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Sebahat.hadzhi said:
~~ Could you please provide us with the output for: apt-cache policy ~~
Click to expand...
See below. For simplicity, we've removed all of the Non-Plesk / Non-Ubuntu entries. FWIW apt-cache policy plesk* produces a 1000 line + detailed output, but it has no errors or warnings anywhere that we could see e.g. Different versions, shown under Table numbers (see example one item extract, also below) Finally and again, just FWIW apt update and/or apt list --upgradable and/or apt -u -V upgrade all provide zero returns at the time of making this post.

apt-cache policy:
Code: 
# apt-cache policy
Package files:

 500 http://security.ubuntu.com/ubuntu noble-security/multiverse amd64 Packages
     release v=24.04,o=Ubuntu,a=noble-security,n=noble,l=Ubuntu,c=multiverse,b=amd64
     origin security.ubuntu.com
 500 http://security.ubuntu.com/ubuntu noble-security/universe amd64 Packages
     release v=24.04,o=Ubuntu,a=noble-security,n=noble,l=Ubuntu,c=universe,b=amd64
     origin security.ubuntu.com
 500 http://security.ubuntu.com/ubuntu noble-security/restricted amd64 Packages
     release v=24.04,o=Ubuntu,a=noble-security,n=noble,l=Ubuntu,c=restricted,b=amd64
     origin security.ubuntu.com
 500 http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages
     release v=24.04,o=Ubuntu,a=noble-security,n=noble,l=Ubuntu,c=main,b=amd64
     origin security.ubuntu.com
 510 https://esm.ubuntu.com/infra/ubuntu noble-infra-updates/main amd64 Packages
     release v=24.04,o=UbuntuESM,a=noble-infra-updates,n=noble,l=UbuntuESM,c=main,b=amd64
     origin esm.ubuntu.com
 510 https://esm.ubuntu.com/infra/ubuntu noble-infra-security/main amd64 Packages
     release v=24.04,o=UbuntuESM,a=noble-infra-security,n=noble,l=UbuntuESM,c=main,b=amd64
     origin esm.ubuntu.com
 510 https://esm.ubuntu.com/apps/ubuntu noble-apps-updates/main amd64 Packages
     release v=24.04,o=UbuntuESMApps,a=noble-apps-updates,n=noble,l=UbuntuESMApps,c=main,b=amd64
     origin esm.ubuntu.com
 510 https://esm.ubuntu.com/apps/ubuntu noble-apps-security/main amd64 Packages
     release v=24.04,o=UbuntuESMApps,a=noble-apps-security,n=noble,l=UbuntuESMApps,c=main,b=amd64
     origin esm.ubuntu.com


 500 http://autoinstall.plesk.com/PHP83_17 noble/all amd64 Packages
     release o=Plesk,a=noble,n=noble,l=PHP v 8.3 packages,c=all,b=amd64
     origin autoinstall.plesk.com
 500 http://autoinstall.plesk.com/PHP82_17 noble/all amd64 Packages
     release o=Plesk,a=noble,n=noble,l=PHP v 8.2 packages,c=all,b=amd64
     origin autoinstall.plesk.com
 500 http://autoinstall.plesk.com/pool/PSA_18.0.64_15680 noble/extras amd64 Packages
     release o=Plesk,a=noble,n=noble,l=Plesk 18.0.64 packages,c=extras,b=amd64
     origin autoinstall.plesk.com
 500 https://autoinstall.plesk.com/grafana/deb stable/main amd64 Packages
     release o=Plesk,a=stable,n=stable,l=grafana,c=main,b=amd64
     origin autoinstall.plesk.com

Pinned packages:
#

apt-cache policy plesk* One item extract: plesk-php83-xml:
Code: 
plesk-php83-xml:
  Installed: 8.3.12-ubuntu.24.04.240926.1652
  Candidate: 8.3.12-ubuntu.24.04.240926.1652
  Version table:
 *** 8.3.12-ubuntu.24.04.240926.1652 500
        500 http://autoinstall.plesk.com/PHP83_17 noble/all amd64 Packages
        100 /var/lib/dpkg/status
 
Could you please make sure you have repositories defined (/etc/apt/sources.list or /etc/apt/sources.list.d/* ) for noble/main and noble/universelike:

Index of /ubuntu noble/main amd64
Click to expand...

Index of /ubuntu noble/universe amd64
Click to expand...

Also, to work around the issue run on server before installation:

touch /tmp/plesk-installer-skip-repository-check.flag
Click to expand...

You may also try:

apt-get clean

apt-get update
Click to expand...

If you have the option to open a support ticket it would really help identifying the issue with direct access to the server.

In case there is still an issue, could you please provide the full output for:

apt-cache policy | grep "b=amd64"
Click to expand...

Thank you in advance.
 
Update

We were caught in cross communication there @Sebahat.hadzhi so this message was all but done, in advance of your previous message.
We'll deal with that in the next post.

Your previous request set us off on a mission, so we re-checked, re-worked and re-tested all of the Ubuntu dependencies, packages and repros. In addition to all of the previous tests mentioned, the following also provide zero returns: apt-get check and apt-mark showhold and apt install -f plus the far more time consuming #aptitude (via the interactive terminal) and | Resolver | shows zero defer and zero conflict so, as far as Ubuntu is concerned, we've either resolved the issue there, or, it was never there in the first place. The main update, is all of the following additional lines (Ubuntu) that now appear in the apt-cache policy:

Code: 
100 http://uk.archive.ubuntu.com/ubuntu noble-proposed/multiverse amd64 Packages
     release v=24.04,o=Ubuntu,a=noble-proposed,n=noble,l=Ubuntu,c=multiverse,b=amd64
     origin uk.archive.ubuntu.com
 100 http://uk.archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages
     release v=24.04,o=Ubuntu,a=noble-proposed,n=noble,l=Ubuntu,c=universe,b=amd64
     origin uk.archive.ubuntu.com
 100 http://uk.archive.ubuntu.com/ubuntu noble-proposed/restricted amd64 Packages
     release v=24.04,o=Ubuntu,a=noble-proposed,n=noble,l=Ubuntu,c=restricted,b=amd64
     origin uk.archive.ubuntu.com
 100 http://uk.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
     release v=24.04,o=Ubuntu,a=noble-proposed,n=noble,l=Ubuntu,c=main,b=amd64
     origin uk.archive.ubuntu.com
 100 http://uk.archive.ubuntu.com/ubuntu noble-backports/universe amd64 Packages
     release v=24.04,o=Ubuntu,a=noble-backports,n=noble,l=Ubuntu,c=universe,b=amd64
     origin uk.archive.ubuntu.com
 500 http://uk.archive.ubuntu.com/ubuntu noble-updates/multiverse amd64 Packages
     release v=24.04,o=Ubuntu,a=noble-updates,n=noble,l=Ubuntu,c=multiverse,b=amd64
     origin uk.archive.ubuntu.com
 500 http://uk.archive.ubuntu.com/ubuntu noble-updates/universe amd64 Packages
     release v=24.04,o=Ubuntu,a=noble-updates,n=noble,l=Ubuntu,c=universe,b=amd64
     origin uk.archive.ubuntu.com
 500 http://uk.archive.ubuntu.com/ubuntu noble-updates/restricted amd64 Packages
     release v=24.04,o=Ubuntu,a=noble-updates,n=noble,l=Ubuntu,c=restricted,b=amd64
     origin uk.archive.ubuntu.com
 500 http://uk.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
     release v=24.04,o=Ubuntu,a=noble-updates,n=noble,l=Ubuntu,c=main,b=amd64
     origin uk.archive.ubuntu.com
 500 http://uk.archive.ubuntu.com/ubuntu noble/multiverse amd64 Packages
     release v=24.04,o=Ubuntu,a=noble,n=noble,l=Ubuntu,c=multiverse,b=amd64
     origin uk.archive.ubuntu.com
 500 http://uk.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
     release v=24.04,o=Ubuntu,a=noble,n=noble,l=Ubuntu,c=universe,b=amd64
     origin uk.archive.ubuntu.com
 500 http://uk.archive.ubuntu.com/ubuntu noble/restricted amd64 Packages
     release v=24.04,o=Ubuntu,a=noble,n=noble,l=Ubuntu,c=restricted,b=amd64
     origin uk.archive.ubuntu.com
 500 http://uk.archive.ubuntu.com/ubuntu noble/main amd64 Packages
     release v=24.04,o=Ubuntu,a=noble,n=noble,l=Ubuntu,c=main,b=amd64
     origin uk.archive.ubuntu.com
 
There was a one policy addition to the /etc/apt/sources.list.d/ubuntu.sources file previously posted in the Issue - Plesk updates when running Ubuntu 24.04.1 LTS - Possible Installer Plesk bug? (which again, is a change of format, from that used in Ubuntu 22.04) and that addition was: Architectures: amd64

So the updated /etc/apt/sources.list.d/ubuntu.sources file now reads like this:
Code: 
Architectures: amd64
Types: deb deb-src
URIs: http://uk.archive.ubuntu.com/ubuntu/
Suites: noble noble-updates noble-backports noble-proposed
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

Architectures: amd64
Types: deb deb-src
URIs: http://security.ubuntu.com/ubuntu/
Suites: noble-security
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

This ^ answers your first question (correctly) and obviously all of the other suggested checks & updates that you've mentioned too.

The final requested item is here:
Code: 
# apt-cache policy | grep "b=amd64"
     release v=24.04,o=Ubuntu,a=noble-security,n=noble,l=Ubuntu,c=multiverse,b=amd64
     release v=24.04,o=Ubuntu,a=noble-security,n=noble,l=Ubuntu,c=universe,b=amd64
     release v=24.04,o=Ubuntu,a=noble-security,n=noble,l=Ubuntu,c=restricted,b=amd64
     release v=24.04,o=Ubuntu,a=noble-security,n=noble,l=Ubuntu,c=main,b=amd64
     release v=24.04,o=Ubuntu,a=noble-proposed,n=noble,l=Ubuntu,c=multiverse,b=amd64
     release v=24.04,o=Ubuntu,a=noble-proposed,n=noble,l=Ubuntu,c=universe,b=amd64
     release v=24.04,o=Ubuntu,a=noble-proposed,n=noble,l=Ubuntu,c=restricted,b=amd64
     release v=24.04,o=Ubuntu,a=noble-proposed,n=noble,l=Ubuntu,c=main,b=amd64
     release v=24.04,o=Ubuntu,a=noble-backports,n=noble,l=Ubuntu,c=universe,b=amd64
     release v=24.04,o=Ubuntu,a=noble-updates,n=noble,l=Ubuntu,c=multiverse,b=amd64
     release v=24.04,o=Ubuntu,a=noble-updates,n=noble,l=Ubuntu,c=universe,b=amd64
     release v=24.04,o=Ubuntu,a=noble-updates,n=noble,l=Ubuntu,c=restricted,b=amd64
     release v=24.04,o=Ubuntu,a=noble-updates,n=noble,l=Ubuntu,c=main,b=amd64
     release v=24.04,o=Ubuntu,a=noble,n=noble,l=Ubuntu,c=multiverse,b=amd64
     release v=24.04,o=Ubuntu,a=noble,n=noble,l=Ubuntu,c=universe,b=amd64
     release v=24.04,o=Ubuntu,a=noble,n=noble,l=Ubuntu,c=restricted,b=amd64
     release v=24.04,o=Ubuntu,a=noble,n=noble,l=Ubuntu,c=main,b=amd64
     release v=24.04,o=UbuntuESM,a=noble-infra-updates,n=noble,l=UbuntuESM,c=main,b=amd64
     release v=24.04,o=UbuntuESM,a=noble-infra-security,n=noble,l=UbuntuESM,c=main,b=amd64
     release v=24.04,o=UbuntuESMApps,a=noble-apps-updates,n=noble,l=UbuntuESMApps,c=main,b=amd64
     release v=24.04,o=UbuntuESMApps,a=noble-apps-security,n=noble,l=UbuntuESMApps,c=main,b=amd64
     release o=Plesk,a=noble,n=noble,l=PHP v 8.3 packages,c=all,b=amd64
     release o=Plesk,a=noble,n=noble,l=PHP v 8.2 packages,c=all,b=amd64
     release o=Plesk,a=noble,n=noble,l=Plesk 18.0.64 packages,c=extras,b=amd64
     release o=Plesk,a=stable,n=stable,l=grafana,c=main,b=amd64
#

Our own supposition, is that the addition of Architectures: amd64 to /etc/apt/sources.list.d/ubuntu.sources file, is the required "fix" and that it was not a Plesk issue, but an option within the Dist-Upgrade that was not invoked. Your team will know pretty quickly we think. We'll know, at the next 18.0.64 Mini Upgrade.
 
You must log in or register to reply here.

Similar threads

learning_curve
Issue Plesk updates when running Ubuntu 24.04.1 LTS - Possible Installer Plesk bug?
Replies
2
Views
233
learning_curve
learning_curve
learning_curve
Issue Plesk Related Issues Arising After Upgrading Ubuntu Server OS (22.04 LTS to 24.04 LTS)
Replies
6
Views
761
learning_curve
learning_curve
Talistech
Resolved Bug: Plesk NAT - IP Reset via command line does not work because plesk things the ip does not exist.
Replies
1
Views
390
Talistech
Talistech
Liwindo
run-parts: /etc/cron.daily/pleskupdate exited with return code 1
Replies
9
Views
3K
Peter Debik
P
M
Resolved Ubuntu ARM64: The antivirus settings tab of a mail address shows a list of antivirus extensions, of which one isn't available on ARM64.
Replies
3
Views
1K
Peter Debik
P
Back
Top