Problems upgrading to 2.4.4.0

Technical Support
1

OS Name/Version: Ubuntu 22.04.3 LTS

Product Name/Version: AMP Instance Manager v2.4.1.2 built 21/12/2022 17:55

Problem Description:
I am trying to upgrade to version 2.4.4.0 via the command line. usually i just do the following

sudo su -l AMP

ampinstmgr -p

but when i do that this time i get the following error below.

[/home/AMP/.ampdata/instances/AMPCache-Mainline-2440.zip]
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.

ampinstmgr -p
[Info] AMP Instance Manager v2.4.1.2 built 21/12/2022 17:55
[Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV
[Info] Upgrading instance ADS01
[Info] Using cached archive: /home/AMP/.ampdata/instances/AMPCache-Mainline-2440.zip
[/home/AMP/.ampdata/instances/AMPCache-Mainline-2440.zip]
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
[/home/AMP/.ampdata/instances/AMPCache-Mainline-2440.zip.ZIP]
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
[Error] Download or unpack failed. Please check your network connection and try again.
[Error] Unzip return code was 2
[Info] Upgrade failed

Actions taken to resolve so far:
the box is up to date and rebooted and I even tried deleting all the AMP cache files and letting it redownload the 2.4.4.0 version which it did but still the same error.

2

2.4.4.0 is long out of date, are you absolutely certain that your system is up to date? An update to ampinstmgr (usually handled via apt) is required to pull versions 2.4.5 and beyond.

If so, do you see the cubecoders repo when you run an apt update?
Its possible that you may have either removed the repo (such as during an OS upgrade) or are still using the expired key. Posting the output of an apt update will let us confirm that.

3

you are correct the repository got disabled and doesn’t seem to work after an LTS upgrade it looks. I deleted the repo and tried to re-run the install script but it doesn’t seem to add the repo. how can this be manually added? or what is the best way to fix this.

4

If its just disabled but still present, you may need to reenable it rather than readding it, but try giving bash <(wget -qO- getamp.sh) addRepo a go

5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.