Activation Error on creating new instance

  • 60 Views
  • Last Post 6 days ago
warezit posted this 2 weeks ago - Last edited 2 weeks ago

Hello!

I am having an issue with starting any new type of instance via AMP Instance Manager, or the ADS Web Panel. The 10 instances I have already created in the past still boot fine, it's just an issue with trying to start any newly created instances (instances 11+).

Software versions:

AMP Instance Manager v1.4.7.2
Ubuntu 16.04.2
Mono JIT compiler version 4.8.1 (Stable 4.8.1.0/22a39d7 Sun Jun  4 23:18:43 CDT 2017)

Looking at my newly created instance log files, I notice AMP fails to perform a licence check on launch: https://pastebin.com/N8pNVew3

After looking through the forums here, I found 2 different commands to force updating the AMP licence key:

./AMP_Linux_x86_64 +Core.AMP.AppModule MinecraftModule +Core.AMP.LicenceKey [MYKEYHERE]

and

./AMP_Linux_x86_64 +Core.AMP.LicenceKey [MYKEYHERE] -configonly

After putting in my license key, both of those commands return this error: https://pastebin.com/F181zDvG

[17:07:20] [<addlicence>d__16:Activation Error] : Couldn't activate: Error: SecureChannelFailure (/usr/local/lib/../lib/libmono-btls-shared.so) 
[17:07:20] [<addlicence>d__16:Activation Error] : /usr/local/lib/../lib/libmono-btls-shared.so

After looking into this issue, it seems to be related to Mono. So I have made sure to update all my software on my machine via: sudo apt-get update and sudo apt-get upgrade And made sure to reboot my machine when needed.

Furthermore, I have attempted to open the command line and run: ping cubecoders.com which fails from the CLI, BUT if I open the web browser on that machine, I can pull up the "cubecoders.com" website without any issues.

AMP@richard-Q500A:~/.ampdata/instances/Minecraft-ATM3$ ping cubecoders.com
PING cubecoders.com (5.135.23.99) 56(84) bytes of data.
^C
--- cubecoders.com ping statistics ---
8 packets transmitted, 0 received, 100% packet loss, time 7056ms

So, I checked ping google.com from the CLI, and it pings fine...

AMP@richard-Q500A:~/.ampdata/instances/Minecraft-ATM3$ ping google.com
PING google.com (64.233.177.139) 56(84) bytes of data.
64 bytes from yx-in-f139.1e100.net (64.233.177.139): icmp_seq=1 ttl=46 time=13.9 ms
64 bytes from yx-in-f139.1e100.net (64.233.177.139): icmp_seq=2 ttl=46 time=17.4 ms
64 bytes from yx-in-f139.1e100.net (64.233.177.139): icmp_seq=3 ttl=46 time=15.8 ms
64 bytes from yx-in-f139.1e100.net (64.233.177.139): icmp_seq=4 ttl=46 time=14.8 ms
^C
--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 13.914/15.508/17.490/1.335 ms

Thinking this might be firewall related, I made sure to check ufw status as root user:

root@richard-Q500A:/home/AMP/.ampdata/instances/Minecraft-ATM3# ufw status
Status: inactive

I have also run sudo iptables -L ,which returns this:

root@richard-Q500A:/home/AMP/AMP# sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

I have also made sure to check the firewall settings in the GUI, under Settings > Firewall - which also reports as being disabled.

I have also run sudo apt-get dist-upgrade, which returns this:

root@richard-Q500A:/home/AMP/AMP# sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

If I do a Google search for the error Couldn't activate: Error: SecureChannelFailure (/usr/local/lib/../lib/libmono-btls-shared.so), it shows some errors with Mono, but I am lost at that point.

Any insight with this? Is this an issue with Mono, after running software updates (possibly)?? (I have tried removing and reinstalling mono-complete, but that doesn't seem to make any changes.)

Any help with this is greatly appreciated!! Thank you for reading and any/all help!!

Cheers!

-warezit

10 Comments
Order By: Standard | Newest | Votes
Mike posted this 2 weeks ago

You're running an outdated version of AMP, delete your AMPCache files and the instance manager and get a new copy of ampinstmgr. Don't install mono-complete, remove it if its still installed.

warezit posted this 2 weeks ago - Last edited 2 weeks ago

You're running an outdated version of AMP, delete your AMPCache files and the instance manager and get a new copy of ampinstmgr. Don't install mono-complete, remove it if its still installed.

See "Update #1" in the original post below

warezit posted this 2 weeks ago

Update #1

Ran sudo apt-get remove --auto-remove mono-complete which completes fine: https://pastebin.com/9p4D8AHX

Removed all AMP Cache .zip files from /home/AMP/.ampdata/instances (and 2 other zip files I manually placed in the same folder)

Updated AMP Instance Manager via:

wget http://cubecoders.com/Downloads/ampinstmgr.zip
unzip ampinstmgr.zip
rm -i ampinstmgr.zip

Overwrote all files upon extraction, no problems there. But, I accidentally extracted this .zip as root user, so I made sure to run chown AMP:AMP -R /home/AMP/ after extracting this zip - and then switch back to the AMP user using su AMP

Updated all Instances, using: ./ampinstmgr -p which completes fine: https://pastebin.com/CHiETxZU

Same errors now - fails Licence Activation when trying to start Instance #11 (the newly created instance which was failing to start before)

Tried running this command again, to force a key update using ./AMP_Linux_x86_64 +Core.AMP.LicenceKey [MYKEYHERE] -configonly which gives the exact same libmono-btls-shared.so error as before. https://pastebin.com/wDVanvZh

warezit posted this 2 weeks ago

Update #2

In Update #1, I said:

Ran sudo apt-get remove --auto-remove mono-complete which completes fine: https://pastebin.com/9p4D8AHX

This is not the correct way to completely remove mono-complete from a system. The correct way should be running this:

sudo apt-get purge libmono* cli-common mono-runtime
sudo apt-get autoremove

That removed approx. 227 MB of data...

Tried running this command again, to force a key update using ./AMP_Linux_x86_64 +Core.AMP.LicenceKey [MYKEYHERE] -configonly which gives the exact same libmono-btls-shared.so error as before.

Made sure to shutdown all modules, downloaded a new version of AMP again, re-extracted the zip file, as the correct AMP user. Still fails to authentication when launching/creating a new instance.

Running ping cubecoders.com still fails also - while ping google.com still succeeds.

I am giving the machine a reboot now - and taking a 30 min break for food, and to think about this...

Mike posted this 2 weeks ago

cubecoders servers don't respond to ICMP requests, so no ping.

Search your machine for any AMPCache-XXXX.zip files and make sure they're nuked.

Also could you pastebin.net the output of export so I can check there's no env var forcing AMP to try and use btls.

warezit posted this 1 weeks ago - Last edited 1 weeks ago

Hey Mike,

Thanks for clearing that up about the ping situation. That makes sense now why ping cubecoders.com wasn't responding.

Running find /home/ -iname 'AMPCache*' finds only 1 file, from the last AMP update I did two days ago...

root@richard-Q500A:~# find /home/ -iname 'AMPCache*'
/home/AMP/.ampdata/instances/AMPCache-1472.zip

Running export returns this: https://pastebin.com/A2L4eLXW

Running printenv returns this: https://pastebin.com/rDy6iTRZ

warezit posted this 1 weeks ago - Last edited 1 weeks ago

I don't know if this will help, but Nickr (on Discord) and I were talking about this issue, and then you joined in later also... he had mentioned that he saw this issue on 16.04.2 distros of Ubuntu before possibly, and he was digging around on the interwebs and said it might be "threading" related... Not sure if what he is suggesting is an actual solution, but I just wanted to make sure I shared that info... http://i.imgur.com/KCBTC8a.png

Mike posted this 6 days ago

What's the md5sum of your copy of ampinstmgr?

warezit posted this 6 days ago

Running md5sum ampinstmgr returns this:

root@richard-Q500A:/home/AMP/AMP# md5sum ampinstmgr
7c73c5b3d6b1d5ee7713134dcc01dc4a  ampinstmgr

Running sha1sum ampinstmgr returns this:

root@richard-Q500A:/home/AMP/AMP# sha1sum ampinstmgr
564672dca597378d2afc3d18e88cf2d95079b702  ampinstmgr

Nickr posted this 6 days ago - Last edited 6 days ago

I did find a similar error on another application using Mono, that could be fixed by setting the environment variable MONO_TLS_PROVIDER to legacy (TLS standing for Thread Local Storage, just to confuse you), and you did say, Mike, that it had something to do with btls being removed, which is Mono's default value for that variable afaik...

I have still not been able to replicate the error myself though so I have no idea whether this would work.

Try entering 'MONO_TLS_PROVIDER=legacy' and reactivating AMP. If this works, add the same on a new line to /etc/environment... (if you copy-pasted the variable before when I said this on Discord, please note I had typed it incorrectly with a double underscore between MONO and TLS, so it might be worth trying again)