Forums Archived

This forum has been archived. No new posts can be made and no new users can sign up. It remains here for reference only.

Find the new forums here

Licence folder creation fails on newly created instance

  • 118 Views
  • Last Post 06 March 2020
Skeltoras posted this 06 March 2020

OS Name/Version

Linux / Debian GNU/Linux 10 (buster)

Product Name/Version

AMP Release "Lapetus" / v1.9.6.4 - installed by the getamp script

Problem Description

I have a problem on creating new instances with docker enabled. ADS will create the instance but the licences folder isn't created and the instance won't start. If i deactivate docker for instances and create a new instance, the licences folder works and the instance starts.

The command ampinstmgr reactivate INSTANCE doesn't change anything.

Steps to reproduce

  • Upgrade to AMP 1.9.6.4
  • Create a new instance with docker activated in the ADS web-UI
  • Check the licences folder exists
  • Deactivate docker for new instances
  • Create new instance
  • Check the licences folder exists

Actions taken to resolve so far

  • ADS01 restart
  • Creating new instance on CLI without docker flag -> licences folder will be created
  • Creating new instance on CLI with docker flag -> licences folder will not be created
  • Host reboot
  • command ampinstmgr reactivate INSTANCE
  • command ampinstmgr reactivateall
  • changed instance ip binding to 127.0.0.1
  • changed instance ip binding to internal ip
  • changed instance ip binding to 0.0.0.0
  • checked firewall for blocking any traffic to cubecoders licencing servers
  • checked correct dns resolving for the domain
  • deleted browser cache

Logs from CLI instance creation with docker: https://pastebin.com/1hku65ye

Logs from CLI instance creation withou docker: https://pastebin.com/mPJbRFVv

Order By: Standard | Newest | Votes
Mike posted this 06 March 2020

Don't use the command line tool to provision instances inside docker, set up ADS and let ADS create and manage the instances for you.

Skeltoras posted this 06 March 2020

The command line was only to check if the error occurs there too. I did the instance creation with running ADS instance in the web-GUI and encountered the problem there first.

Close