OS Name/Version: Rocky Linux 9.4
Product Name/Version: 2.6.0.0
Problem Description:
Amp starts and runs normally as far as the web UI is concerned, reporting the correct version information, but the ampinstmgr cli on the amp system user fails on every command, reporting the following:
Failure processing application bundle.
Failed to create directory [/root/.cache/] for extracting bundled files.
The ampinstmgr CLI runs correctly from the root user, but this user (as configured by the amp installer by default) is not used to run amp instances.
Steps to reproduce:
Update from AMP 2.5.1 to 2.6
OR install fresh AMP 2.6.0
Actions taken to resolve so far:
Back up amp data, delete, and reinstall
Workaround found:
Run ampinstmgr command using sudo -u amp ampinstmgr from the root user
Mike
24 October 2024 09:18
2
This command won’t work. What happens if you do sudo su -l amp then ampinstmgr status?
That seems to work. Is the -l flag being required now an intentional change, or possibly a byproduct of another change?
The sudo -u amp ampinstmgr status does work, producing the same output as using su -l amp followed by ampinstmgr status
The following is the full list of packages changed by the update process:
Install kernel-modules-core-5.14.0-427.40.1.el9_4.x86_64 @baseos
Install kernel-modules-5.14.0-427.40.1.el9_4.x86_64 @baseos
Install kernel-core-5.14.0-427.40.1.el9_4.x86_64 @baseos
Install kernel-5.14.0-427.40.1.el9_4.x86_64 @baseos
Upgrade ampinstmgr-2.6-2.x86_64 @CubeCoders
Upgraded ampinstmgr-2.5.1.8-2.x86_64 @@System
Upgrade linux-firmware-whence-20240905-143.3.el9_4.noarch @baseos
Upgraded linux-firmware-whence-20240716-143.2.el9_4.noarch @@System
Upgrade linux-firmware-20240905-143.3.el9_4.noarch @baseos
Upgraded linux-firmware-20240716-143.2.el9_4.noarch @@System
Upgrade iwl7260-firmware-1:25.30.13.0-143.3.el9_4.noarch @baseos
Upgraded iwl7260-firmware-1:25.30.13.0-143.2.el9_4.noarch @@System
Upgrade iwl6050-firmware-41.28.5.1-143.3.el9_4.noarch @baseos
Upgraded iwl6050-firmware-41.28.5.1-143.2.el9_4.noarch @@System
Upgrade iwl6000g2a-firmware-18.168.6.1-143.3.el9_4.noarch @baseos
Upgraded iwl6000g2a-firmware-18.168.6.1-143.2.el9_4.noarch @@System
Upgrade iwl5150-firmware-8.24.2.2-143.3.el9_4.noarch @baseos
Upgraded iwl5150-firmware-8.24.2.2-143.2.el9_4.noarch @@System
Upgrade iwl5000-firmware-8.83.5.1_1-143.3.el9_4.noarch @baseos
Upgraded iwl5000-firmware-8.83.5.1_1-143.2.el9_4.noarch @@System
Upgrade iwl3160-firmware-1:25.30.13.0-143.3.el9_4.noarch @baseos
Upgraded iwl3160-firmware-1:25.30.13.0-143.2.el9_4.noarch @@System
Upgrade iwl2030-firmware-18.168.6.1-143.3.el9_4.noarch @baseos
Upgraded iwl2030-firmware-18.168.6.1-143.2.el9_4.noarch @@System
Upgrade iwl2000-firmware-18.168.6.1-143.3.el9_4.noarch @baseos
Upgraded iwl2000-firmware-18.168.6.1-143.2.el9_4.noarch @@System
Upgrade iwl135-firmware-18.168.6.1-143.3.el9_4.noarch @baseos
Upgraded iwl135-firmware-18.168.6.1-143.2.el9_4.noarch @@System
Upgrade iwl105-firmware-18.168.6.1-143.3.el9_4.noarch @baseos
Upgraded iwl105-firmware-18.168.6.1-143.2.el9_4.noarch @@System
Upgrade iwl1000-firmware-1:39.31.5.1-143.3.el9_4.noarch @baseos
Upgraded iwl1000-firmware-1:39.31.5.1-143.2.el9_4.noarch @@System
Upgrade iwl100-firmware-39.31.5.1-143.3.el9_4.noarch @baseos
Upgraded iwl100-firmware-39.31.5.1-143.2.el9_4.noarch @@System
Upgrade microcode_ctl-4:20230808-2.20240531.1.el9_4.noarch @baseos
Upgraded microcode_ctl-4:20230808-2.20231009.1.el9_3.noarch @@System
Upgrade glibc-minimal-langpack-2.34-100.el9_4.4.x86_64 @baseos
Upgraded glibc-minimal-langpack-2.34-100.el9_4.3.x86_64 @@System
Upgrade glibc-gconv-extra-2.34-100.el9_4.4.x86_64 @baseos
Upgraded glibc-gconv-extra-2.34-100.el9_4.3.x86_64 @@System
Upgrade glibc-common-2.34-100.el9_4.4.x86_64 @baseos
Upgraded glibc-common-2.34-100.el9_4.3.x86_64 @@System
Upgrade glibc-2.34-100.el9_4.4.x86_64 @baseos
Upgraded glibc-2.34-100.el9_4.3.x86_64 @@System
Upgrade kernel-tools-libs-5.14.0-427.40.1.el9_4.x86_64 @baseos
Upgraded kernel-tools-libs-5.14.0-427.35.1.el9_4.x86_64 @@System
Upgrade kernel-tools-5.14.0-427.40.1.el9_4.x86_64 @baseos
Upgraded kernel-tools-5.14.0-427.35.1.el9_4.x86_64 @@System
Upgrade bpftool-7.3.0-427.40.1.el9_4.x86_64 @baseos
Upgraded bpftool-7.3.0-427.35.1.el9_4.x86_64 @@System
Upgrade webkit2gtk3-jsc-2.46.1-2.el9_4.x86_64 @appstream
Upgraded webkit2gtk3-jsc-2.42.5-1.el9.x86_64 @@System
Upgrade netstandard-targeting-pack-2.1-8.0.110-1.el9_4.x86_64 @appstream
Upgraded netstandard-targeting-pack-2.1-8.0.108-1.el9_4.x86_64 @@System
Upgrade dotnet-host-8.0.10-1.el9_4.x86_64 @appstream
Upgraded dotnet-host-8.0.8-1.el9_4.x86_64 @@System
Reason Change NetworkManager-1:1.46.0-19.el9_4.x86_64 @baseos
Removed kernel-5.14.0-427.24.1.el9_4.x86_64 @@System
Removed kernel-core-5.14.0-427.24.1.el9_4.x86_64 @@System
Removed kernel-modules-5.14.0-427.24.1.el9_4.x86_64 @@System
Removed kernel-modules-core-5.14.0-427.24.1.el9_4.x86_64 @@System
Mike
24 October 2024 16:17
4
It is a side effect of the new packaging system used internally for the updated framework. But it’s more of a coincidence that it worked before because your arguments were wrong in the first place.
system
23 November 2024 16:17
5
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.