Relocated datastore doesnt allow instances to start

  • 110 Views
  • Last Post 05 December 2019
kenryo posted this 04 December 2019

OS Name/Version: Ubuntu Server 18.0.4.3

Product Name/Version:AMP professional v1.9.0.6 built 25/11/2019 12:07

Problem Description: Relocated .ampdata directory with softlink can't start instances

Steps to reproduce:

1.as root I moved /home/amp/.ampdata so its now at /data/2/.ampdata 2. then created a soft link with ln -s /data/2/.ampdata /home/amp/.ampdata 3. then i used chown to change the link and directory owner back to amp user

Actions taken to resolve so far:

  • ampinstmgr was able to create a minecraft instance and it showed up in /data/2/.ampdata/instances so they're being seen and written too but they wont start.

    amp@theta ~> ampinstmgr -t [Info] AMP Instance Manager v1.9.0.6 built 25/11/2019 12:07 [Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV Instance Name │ Friendly Name │ Module │ IP │ Port │ Up ───────────────────┼──────────────────┼────────────┼─────────────────┼───────┼─── ADS01 │ ADS01 │ ADS │ 0.0.0.0 │ 8080 │
    test │ test │ Minecraft │ 0.0.0.0 │ 8081 │

    amp@theta ~> ampinstmgr -a [Info] AMP Instance Manager v1.9.0.6 built 25/11/2019 12:07 [Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV [Info] Starting Instance: 'ADS01' duplicate session: AMPADS01 [Info] Waiting for AMP instance to start... [Error] Failed to start AMP. Exit code was 1 [Info] Starting Instance: 'test' [Info] Waiting for AMP instance to start... duplicate session: AMPtest [Error] Failed to start AMP. Exit code was 1

Order By: Standard | Newest | Votes
Mike posted this 04 December 2019

Did I see on Discord that you managed to resolve this?

kenryo posted this 04 December 2019

Nope. i've redone this multiple times. Latest attempt was giving amp user rwx permissions for my /data/2/ folder directly then mkdir /data/2/.ampdata and making a soft link to it in /home/amp/. Currently ampinstmgr can see the instances and make new ones but running them ends in exit code 1

Mike posted this 05 December 2019

Changing the permissions is gonna kill it anyway. Have you tried checking the logs to see if that instance is running and checking htop to see if any are starting? Looks like they may be running if its complaining about duplicate sessions.

Close