AMP is missing the Backup Menu

Technical Support
,
1

OS Name/Version: Ubuntu 24.04

Product Name/Version: AMP Release Callisto - v2.5.1

Problem Description:
On my AMP instances, there’s the Backup Menu missing. Yesterday I had the issue, when I’m restarting my Ubuntu 24.04 VM for AMP inside Proxmox, that some data was missing.

How can I restore the menu item? I assume there should be a Backup Plugin inside each AMP Instance folder.

Here’s for example, the content of my Minecraft Forge Server’s directory:

AMPConfig.conf      AMPVersion               datastore.dat              FileManagerPlugin.kvp.old  Licences                       MinecraftModule.kvp          Plugins               WebRequestPlugin.kvp.old
AMPConfig.conf.old  AnalyticsPlugin.kvp      EmailSenderPlugin.kvp      ForgeVersionManifest.xml   LocalFileBackupPlugin.kvp      MinecraftModule.kvp.old      scheduleEvents.json   WebRoot
AMP_Linux_x86_64    AnalyticsPlugin.kvp.old  EmailSenderPlugin.kvp.old  geoip-data.mmdb.gz         LocalFileBackupPlugin.kvp.old  ModpacksCache.json           scheduleTimes.json
AMP_Logs            Backups                  FileManagerPlugin.kvp      InstalledDeps.json         Minecraft                      NeoForgeVersionManifest.xml  WebRequestPlugin.kvp

Steps to reproduce:

  • Go into Proxmox
  • Reboot the VM using the restart button

Actions taken to resolve so far:

I tried to run ampinstmgr upgradeall but it won’t restore the Backup Menu.

Thank you for help

Edit: I just noticed that I even have a LocalFileBackupPlugin in my instance folder. However, the backup menu is missing.

2

@CubeCoders-Bot can you walk this user through checking the logs for the affected instance and see if there’s anything that might prevent the backup plugin from loading?

3

Alrighty, let’s dig into those logs and see what’s going on with the backup plugin. First, let’s check the logs for the affected instance. Here’s how you can do it:

  1. Log in to the AMP web interface.
  2. Right-click on the instance that’s missing the backup menu and select “View Logs”.

Once you’re in the logs, look for any errors or warnings that might give us a clue about why the backup plugin isn’t loading. Let me know what you find! :crossed_fingers:

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback
4

Sorry for the late reply.

Two weeks ago, I configured a custom backup location. I tried to fix the permissions, but nothing seemed to work. First, I had mounted a virtual hard drive to /media/backups and thought that maybe the mount options in my fstab had some issues for the hard drive.

I tried this (and some other) mount options:

/dev/disk/by-uuid/someuuid /media/backups ext4 defaults,auto,rw,user,exec 0 2

But I couldn’t locate the issue that prevents amp from accessing the path. Then I removed the hard drive, hoping that if I pointed amp to a folder that isn’t on a second hard drive, it could access the directory and its subdirectories. But even chowning did not change anything, and the same error still occurs.

As soon as I revert the custom backup location, the backup plugin loads normally.

Here’s the log:

[11:16:57] [Core Info/1]          : Starting AMP version 2.5.1.0 (Callisto), built 06/07/2024 22:13
[11:16:57] [Core Info/1]          : Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[11:16:57] [Core Info/1]          : Running in a Docker environment.
[11:16:57] [Core Info/1]          : OS: Linux / x86_64
[11:16:57] [Core Info/1]          : CPU: QEMU Virtual CPU version 2.5+ (6C/6T)
[11:16:57] [Core Info/1]          : RAM: 32059MB
[11:16:57] [Core Info/1]          : AMP Instance ID: b6faa855-02b6-400e-bf8c-fc7027a05504
[11:16:57] [Loader Info/1]        : Loaded MinecraftModule version 1.0.0.3 by CubeCoders Limited
[11:16:57] [Core Info/1]          : Metrics publishing is enabled at udp://localhost:12820.
[11:16:57] [Loader Info/1]        : Loaded FileManagerPlugin by CubeCoders Limited
[11:16:57] [Loader Info/1]        : Loaded EmailSenderPlugin by CubeCoders Limited
[11:16:57] [Loader Info/1]        : Loaded WebRequestPlugin by CubeCoders Limited
[11:16:57] [Loader Error/1]       : Container failed to resolve plugin LocalFileBackupPlugin
[11:16:57] [Loader Error/1]       : Resolution of the dependency failed, type = 'LocalFileBackupPlugin.PluginMain', name = '(none)'.
Exception occurred while: Calling constructor LocalFileBackupPlugin.PluginMain(ModuleShared.ILogger log, ModuleShared.IConfigSerializer config, ModuleShared.IPlatformInfo currentPlatform, ModuleShared.IRunningTasksManager tasks, ModuleShared.IFeatureManager features, ModuleShared.IApplicationWrapper app, ModuleShared.IPluginMessagePusher messages, ModuleShared.IAMPInstanceInfo instanceInfo).
Exception is: UnauthorizedAccessException - Access to the path '/media/backups/PreyUltra01/' is denied.
-----------------------------------------------
At the time of the exception, the container was: 
  Resolving LocalFileBackupPlugin.PluginMain,(none)
  Calling constructor LocalFileBackupPlugin.PluginMain(ModuleShared.ILogger log, ModuleShared.IConfigSerializer config, ModuleShared.IPlatformInfo currentPlatform, ModuleShared.IRunningTasksManager tasks, ModuleShared.IFeatureManager features, ModuleShared.IApplicationWrapper app, ModuleShared.IPluginMessagePusher messages, ModuleShared.IAMPInstanceInfo instanceInfo)

[11:16:57] [Logger Fatal/1]       : 'LocalFileBackupPlugin' does not implement abstract class 'ModuleShared.AMPPlugin'

Thank you for help

5

Ah, that log entry is definitely telling us something important! Specifically, this bit:

Exception is: UnauthorizedAccessException - Access to the path '/media/backups/PreyUltra01/' is denied.

This indicates that AMP can’t access the /media/backups/PreyUltra01/ directory due to permission issues. Even though you already tried fixing the permissions, let’s double-check things and try a few additional steps to ensure AMP has the access it needs.

  1. Check Permissions:
    Make sure the directory is accessible by the AMP user. You can try the following:

    sudo chown -R amp:amp /media/backups
sudo chmod -R 755 /media/backups

  2. Verify Mount Options:
    Ensure that the mount options you use in fstab are correct and don’t restrict access. The options you provided look fine, but double-checking won’t hurt:

    /dev/disk/by-uuid/someuuid /media/backups ext4 defaults,auto,rw,user,exec 0 2

  3. Access from AMP:
    Try accessing the directory as the AMP user to ensure there’s no implicit restriction:

    sudo su -l amp
cd /media/backups
touch testfile

    If this fails, we’ll know more specifically what the issue might be.

  4. Recheck Backup Location Setting:
    Go back into the AMP web interface:

    • Use the search box in the top-right corner to find the backup settings.
    • Ensure that the backup location is set correctly and points to /media/backups/.

Try these steps and let me know if the backup plugin still doesn’t load.

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback
6

I checked the permissions and mount options twice, but the backup plugin still doesn’t load.

I also upgraded my amp instance to the latest version.

7

Alright, thanks for double-checking those permissions and getting AMP updated. Since permissions don’t seem to be the issue, we might be looking at something a bit trickier. To narrow it down, let’s perform a test with a simpler backup location to isolate the problem.

Here’s what we’ll do next:

  1. Create a temporary local backup directory:

    mkdir /home/amp/backups
sudo chown -R amp:amp /home/amp/backups
sudo chmod -R 755 /home/amp/backups

  2. Update AMP to use this new backup location:

    • Go into the AMP web interface.
    • Use the search box to find the backup settings.
    • Change the backup location to /home/amp/backups.

  3. Restart the AMP instance and see if the backup plugin loads:

    • Restart the instance via the AMP interface by right-clicking the instance and selecting “Restart”.

Let’s see if AMP happily loads the Backup Plugin using this simpler, local directory. If it works, we can then try figuring out what makes /media/backups/ different. If it fails, it might point to something more intricate with AMP itself or how it’s configured. Let me know how it goes!

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback
8

@s3tupw1zard I can see in the header information that the instance is running inside a docker container - did you map that path to the instance so that it’s available inside the container? At the moment this has to be done manually in the Instances.json file.

10

@CubeCoders-Bot Stop responding for now because you hallucinated that last response.

11

undefined

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback
1 Like
12

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