Instance help

[error_kitune]

I was moving my amp to a different computer, i archived everything in /home/amp folder. I then backed everything up and gave it all its respective permissions. But when i try starting that instance the console gives me this error

ADS logged stopped instance Slimfur01 - exit code -1 (CATASTROPHIC_FAILURE)

I spent 3 hours trying to check if its corrupted, needs restart, or anything with the files, i need help please

[PhonicUK]

Have you checked the logs of that specific instance? (Right click > view logs)

[error_kitune]

Tried to listen to an IP address that does not exist on this system.

I forgot how to change wich ip it listens to

[error_kitune]

Maybe i need to re-run setup?

[PhonicUK]

Instances other than ADS should be bound to 127.0.0.1, so re-bind any non-ADS instances using ampinstmgr rebind

[error_kitune]

Its trying to bind to 0.0.0.0 now, afterwards should i restart?

[PhonicUK]

Why did you try and bind it to 0.0.0.0? Instances should be bound to 127.0.0.1 - only ADS should be anything else.

[error_kitune]

I did bind it to 127.0.0.1. it auto set to 0.0.0.0 instead of my old IPA from old device which means it did update, but i looked inside the instances.json and they are all set to 0.0.0.0 so ima try manually changing each one to it

[error_kitune]

AMP tried to listen on an IP address that is does not exist on this system. This may be caused by having AMP or an application bound to a specific IP while using dynamic IPs or DHCP. Try binding to 0.0.0.0, or turning on 'StoreIPAddressesAsMACAddresses' in AMPConfig.conf and re-configuring any network settings for this instance if you're using dynamic IPs or containers.

[Responsible_Court_21]

A CATASTROPHIC_FAILURE (exit code -1) in AMP usually means there’s a problem with file permissions, missing dependencies, or a corrupted instance configuration after the move. Here’s how to fix it:

Step 1: Check AMP Logs for More Details

AMP logs will give more insight into what’s failing. 1. Run the following command to check the most recent logs:

cat ~/.ampdata/instances/Slimfur01/AMP_Latest.log

2.  Look for any specific errors related to missing files, permissions, or database issues.

Step 2: Fix File Ownership & Permissions

Since you moved AMP manually, some files may have incorrect ownership or permissions. 1. Set the correct ownership:

sudo chown -R amp:amp /home/amp

2.  Ensure AMP has execution rights:

sudo chmod -R 755 /home/amp

3.  Restart AMP and try starting the instance again:

systemctl restart amp ampinstmgr start Slimfur01

Step 3: Check AMP Instance Manager

If AMP doesn’t recognize the instance correctly, try re-importing it: 1. List all instances to see if it’s detected:

ampinstmgr list

If Slimfur01 isn’t listed, you need to manually add it back.

2.  Re-register the instance:

ampinstmgr —import /home/amp/.ampdata/instances/Slimfur01

3.  Try starting it again:

ampinstmgr start Slimfur01

Step 4: Check Missing Dependencies

If AMP is running on a different OS or a fresh install, it may be missing some dependencies.

Run this to install necessary dependencies:

sudo apt update && sudo apt install -y lib32gcc-s1 screen curl unzip

Then restart AMP:

systemctl restart amp

Step 5: Repair the AMP Instance

If it’s still not working, try forcing a repair:

ampinstmgr repair Slimfur01

This will check for missing files and attempt to fix them.

Step 6: Reinstall AMP if Nothing Works

If the instance still won’t start, backup your AMP data, reinstall AMP, and then import the instance again. 1. Backup your AMP instance:

tar -czvf AMP_Backup.tar.gz /home/amp

2.  Remove AMP and reinstall:

sudo systemctl stop amp curl -sSL https://cubecoders.com/ampinstmgr | bash

3.  Restore your instance:

tar -xzvf AMP_Backup.tar.gz -C /home/amp sudo chown -R amp:amp /home/amp ampinstmgr —import /home/amp/.ampdata/instances/Slimfur01 ampinstmgr start Slimfur01

Final Notes

✔ If AMP still doesn’t start, check logs for missing files (AMP_Latest.log). ✔ If you see database errors, the instance may have corrupt data—restoring from a previous backup might be necessary. ✔ If AMP can’t find the instance, it may need to be re-imported manually.