My ubuntu server updated and then I lost access to the AMP dashboard. I have a heap of trouble getting AMP to update due to changes in the Ubuntu Server update but once it finally updated, my entire AMP system had reset and I have lost all of my instances including the long term Minecraft Survival World. Why did this happen?
Reproduction Steps
Ubuntu Server Updated
Lost access to AMP dashboard, returned an error connecting to the server.
Updated the AMP Service via terminal
Relogged into AMP Dashboard, all instances gone. Completely wiped.
I am not too sure to be honest. It came up on the new packages to install in Webmin. Something like ampmgr-inst or something like that. I have just had updates again and it has done the same thing. New AMP update available, installed and now I get the ‘refused to connect’ error when trying to load AMP via the usual IP address.
Now I get this error when trying to update AMP…
dpkg: error processing package ampinstmgr (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
Errors were encountered while processing:
ampinstmgr
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
linux-headers-6.8.0-139 linux-headers-6.8.0-139-generic
linux-image-6.8.0-139-generic linux-modules-6.8.0-139-generic
linux-modules-extra-6.8.0-139-generic linux-tools-6.8.0-139
linux-tools-6.8.0-139-generic
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
ampinstmgr
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/61.9 MB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 239767 files and directories currently installed.)
Preparing to unpack .../ampinstmgr_2.8.0.8_amd64.deb ...
Failed to stop amptasks.timer: Unit amptasks.timer not loaded.
Failed to stop ampfirewall.timer: Unit ampfirewall.timer not loaded.
dpkg: warning: old ampinstmgr package pre-removal script subprocess returned error exit status 5
dpkg: trying script from the new package instead ...
Failed to stop amptasks.timer: Unit amptasks.timer not loaded.
Failed to stop ampfirewall.timer: Unit ampfirewall.timer not loaded.
dpkg: error processing archive /var/cache/apt/archives/ampinstmgr_2.8.0.8_amd64.deb (--unpack):
new ampinstmgr package pre-removal script subprocess returned error exit status 5
chown: cannot access '/etc/systemd/system/ampinstmgr.*': No such file or directory
Failed to enable unit: Unit file ampinstmgr.service does not exist.
Failed to enable unit: Unit file amptasks.timer does not exist.
Failed to start amptasks.timer: Unit amptasks.timer not found.
Failed to enable unit: Unit file ampfirewall.timer does not exist.
Failed to start ampfirewall.timer: Unit ampfirewall.timer not found.
dpkg: error while cleaning up:
installed ampinstmgr package post-installation script subprocess returned error exit status 5
Errors were encountered while processing:
/var/cache/apt/archives/ampinstmgr_2.8.0.8_amd64.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
If I were you, I wouldn’t update AMP any other way than following the update guide. If you have terminal access, it’s as easy as running getamp update as root. I would give that a shot first, then consult the update guide if you have more issues.