• Tried to use session ID - Session belongs to 127.0.0.1 - Unable to manage any Instance

Tried to use session ID - Session belongs to 127.0.0.1 - Unable to manage any Instance

  • 326 Views
  • Last Post 05 June 2019
  • Topic Is Solved
thecattastrophe posted this 04 June 2019

The OS you're using and its version
CentOS Linux 7 (Core)
The name and version of the Cubecoders product you are using. Make sure to specify the actual version, and not just that it's the 'latest' version.
v1.8.0.2
A description of the issue you are having.
I am unable to start any Instances other than the default ADS01. If I "Manage" ADS01 I get a spam of console messages that I can't find explanations to anywhere.
What you have tried so far to resolve the issue and what happened.
I have attempted all I could find. I tried looking all over the Wiki but there is no details and its barely filled out to help with this. I have tried looking over the support topics but I don't find a single person with this same issue. I tried a fresh install and clear out believing I might have done something wrong in installation however nothing was wrong at all from what I can see. I am making sure the user account I have set for AMP is different than my default login for the Linux installation just to be sure it was not that.
A paste of any relevant output from the log file for a given AMP instance (where applicable).
21:50:3447.205.147.2 tried to use session ID 875b28dd-ca94-48b1-a4a3-12e946a1c5c1 - but that session belongs to 127.0.0.1
21:50:3547.205.147.2 tried to use session ID 875b28dd-ca94-48b1-a4a3-12e946a1c5c1 - but that session belongs to 127.0.0.1

This will repeat forever until I restart the whole service or reboot.

Would greatly appreciate the help...

amp instance
Order By: Standard | Newest | Votes
thecattastrophe posted this 05 June 2019

Strange because that was the only way to get it to work. I checked for spaces and special characters. I had nothing extra aside from those dashes. The moment I removed them the key worked.

Mike posted this 05 June 2019

You don't need to remove the dashes. My guess is there was a stray space before/after the key.

thecattastrophe posted this 04 June 2019

Ok I see what happened... For some reason when you get the product key it includes dashes. However when the dashes are in the product key during installation or when reactivating it says the license key is invalid. I did not see in the email to remove the dashes or during installation.

Mike posted this 04 June 2019

You need to reactivate them using "ampinstmgr reactivate"

thecattastrophe posted this 04 June 2019

So I checked the logs and I get the following.

[09:44:32] [Core Info]            : Starting AMP version 1.8.0.2 (TITAN), built 22/05/2019 10:44
[09:44:32] [Core Info]            : Release spec: Release - built by CUBECODERS/BuildBot on CCL-DEV
[09:44:32] [Core Warning]         : Current time zone is set to MST - Servers should ideally be UTC to avoid time-zone related issues
[09:44:32] [Core Info]            : OS: Linux / x86_64
[09:44:32] [Core Info]            : CPU: Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz (4C/8T)
[09:44:32] [Core Info]            : AMP Instance ID: d8f6aec6-7f5a-4d45-bb2b-9a6f3820d78e
[09:44:32] [Core Info]            : Checking for AMP updates...
[09:44:32] [WebServer Info]       : Websockets are enabled.
[09:44:32] [ModuleLoader Info]    : Loaded MinecraftModule version 1.0.0.3 by CubeCoders Limited
[09:44:32] [ModuleLoader Info]    : Loaded FileManager version 1.0.0.0 by CubeCoders Limited
[09:44:32] [ModuleLoader Info]    : Loaded EmailSender version 1.0.0.0 by CubeCoders Limited
[09:44:32] [ModuleLoader Info]    : Loaded PushBulletPlugin version 1.0.0.0 by CubeCoders Limited
[09:44:32] [ModuleLoader Info]    : Loaded LocalFileBackupPlugin version 1.0.0.0 by CubeCoders Limited
[09:44:32] [Core Error]           : AMP may not run without a licence.

However I know I have the professional license allowing me 5 instances.

Mike posted this 04 June 2019

Have you checked the logs for the instances to see why they're not running?

thecattastrophe posted this 04 June 2019

Performed ampinstmgr rebind and set the ip and port for both instances. Still the same issue when I attempt to "Manage" ADS01. I also am unable to manage any new instances. It will attempt to Start the instance and show green. Then when I attempt to "Manage" it will state that I can only manage an instance that is currently running and turn red. I attempted to run ampinstmgr start and do it by command line. Then I tried to enter into the view of the instance using ampinstmgr view and was returned that the instance is not running. The port that I bound the second instance on is allowed public in firewall-cmd.

Mike posted this 04 June 2019

Rebind all your instances using ampinstmgr rebind (see ampinstmgr info to see which ip/port a given instance is currently using)

thecattastrophe posted this 04 June 2019

I made the correction on the main post.

thecattastrophe posted this 04 June 2019

I appologize Mike I was up late writing this post and apparently fully overlooked what the question stated. For some reason when I read the question I thought I read if it was the latest version then type latest. I must be going crazy.

The version I am running is v1.8.0.2

Mike posted this 04 June 2019

The name and version of the Cubecoders product you are using. Make sure to specify the actual version, and not just that it's the 'latest' version.

Latest

...

Live Chat Register to post
Categories
Search
Popular Tags
This Weeks High Earners
Hot Topics
Close