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

Having issues installing AMP on a CentOS 7 VPS

  • 1.4K Views
  • Last Post 28 October 2017
  • Topic Is Solved
Spendy posted this 25 October 2017

Hey,

Having a bit of issue installing my AMP instance on my VPS. I do all the steps and when I get to this point: ./ampinstmgr ShowModuleList. It also does it on pretty much all commands after this. It spits out this error:

Native stacktrace:

    ./ampinstmgr() [0x63ff78]
    /lib64/libpthread.so.0(+0xf5e0) [0x7fe29e0645e0]
    /lib64/libc.so.6(gsignal+0x37) [0x7fe29dcc71f7]
    /lib64/libc.so.6(abort+0x148) [0x7fe29dcc88e8]
    ./ampinstmgr() [0x657314]
    ./ampinstmgr() [0x57f57b]
    ./ampinstmgr() [0x57f6dc]
    ./ampinstmgr() [0x5737e0]
    ./ampinstmgr() [0x486485]
    ./ampinstmgr() [0x59617f]
    ./ampinstmgr() [0x58873e]
    ./ampinstmgr() [0x58846b]
    ./ampinstmgr() [0x589720]
    ./ampinstmgr() [0x5899f4]
    ./ampinstmgr() [0x58dbf6]
    ./ampinstmgr() [0x597104]
    ./ampinstmgr() [0x597d07]
    ./ampinstmgr(GC_start_routine+0x38) [0x597f06]
    /lib64/libpthread.so.0(+0x7e25) [0x7fe29e05ce25]
    /lib64/libc.so.6(clone+0x6d) [0x7fe29dd8a34d]

Debug info from gdb:

monogdbrendernativebacktraces not supported on this platform, unable to find gdb or lldb

================================================================= Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application.

Any tips on how I can fix this?

Thanks,

Spendy

error installation centos-7 vps digitalocean
Order By: Standard | Newest | Votes
Spendy posted this 28 October 2017

All good Mike. Figured it out!

Thanks for your help!

Mike posted this 28 October 2017

Did you make sure to pick a new port number for the new instance? Each instance requires its own port number.

Spendy posted this 27 October 2017

Hey,

It was to do with the IP binding:

[Error] [0] (SocketException) : System.Net.Sockets.SocketException (0x80004005): Address already in use
  at System.Net.Sockets.Socket.Bind (System.Net.EndPoint localEP) [0x00043] in <284c8916baa7426e854207bb68427ea7>:0 
  at System.Net.Sockets.TcpListener.Start (System.Int32 backlog) [0x00044] in <284c8916baa7426e854207bb68427ea7>:0 
  at m.Http.HttpBackend.ConnectionLoop () [0x00000] in <6ba0f115d4834d51b3526e12d15cee09>:0 
  at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00014] in <3574b7750bbd4f3481d1561b74d01b33>:0 
  at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in <3574b7750bbd4f3481d1561b74d01b33>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <3574b7750bbd4f3481d1561b74d01b33>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in <3574b7750bbd4f3481d1561b74d01b33>:0 
  at System.Threading.ThreadHelper.ThreadStart () [0x00008] in <3574b7750bbd4f3481d1561b74d01b33>:0 
[Error] --- End Exception Data ---

Says it was already running on another port. I presume its the AMP IP Binding and not the MC Servers IP Binding that causing the issue? Can I ask what to do selecting the IP to use? I am running the web panel on the same server I am hosting it on.

Thanks,

Spendy

Spendy posted this 26 October 2017

[Error] Linux Jayzus 3.10.0-693.el7.x8664 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x8664 x8664 x8664 GNU/Linux

[Error] [0] (SocketException) : System.Net.Sockets.SocketException (0x80004005): Address already in use
  at System.Net.Sockets.Socket.Bind (System.Net.EndPoint localEP) [0x00043] in <284c8916baa7426e854207bb68427ea7>:0 
  at System.Net.Sockets.TcpListener.Start (System.Int32 backlog) [0x00044] in <284c8916baa7426e854207bb68427ea7>:0 
  at m.Http.HttpBackend.ConnectionLoop () [0x00000] in <6ba0f115d4834d51b3526e12d15cee09>:0 
  at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00014] in <3574b7750bbd4f3481d1561b74d01b33>:0 
  at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in <3574b7750bbd4f3481d1561b74d01b33>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <3574b7750bbd4f3481d1561b74d01b33>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in <3574b7750bbd4f3481d1561b74d01b33>:0 
  at System.Threading.ThreadHelper.ThreadStart () [0x00008] in <3574b7750bbd4f3481d1561b74d01b33>:0 
[Error] --- End Exception Data ---

[20:32:41] [Core:System Info]     : ###################################
[20:32:41] [Core:System Info]     : #         AMP DIAGNOSTICS         #
[20:32:41] [Core:System Info]     : ###################################
[20:32:41] [Core:System Info]     : The IP+Port combination requested by the socket is already in use by another application. Either end the other application or re-bind this AMP instance to a different IP/port.

Cool, I can see there its because the IP & Port is being used by another application is the socket being the AMP IP Binding or the IP Binding? I'm running the web panel on the same server as the MC server so I think I am getting confused for the settings I need to put in.

Thanks,

Spendy

Mike posted this 26 October 2017

That's not the instances log file. That's the instance manager/ADS log. You want to look in /home/AMP/.ampdata/instances/RedVerse-MC/AMPLogs

Spendy posted this 26 October 2017

[20:32:39] [InstanceManager:daspendy Activity] : Starting instance RedVerse-MC

[20:32:39] [InstanceManager:daspendy Debug] : Running /usr/bin/tmux -f /dev/null new-session -s "AMPRedVerse-MC" -d "cd '/home/AMP/.ampdata/instances/RedVerse-MC' --; /home/AMP/.ampdata/instances/RedVerse-MC/AMPLinuxx8664 "

[20:32:39] [ModuleShared:daspendy Debug] : Starting process /usr/bin/tmux

[20:32:39] [ModuleShared:daspendy Debug] : Working Directory: /home/AMP/.ampdata/instances/RedVerse-MC

[20:32:39] [ModuleShared:daspendy Debug] : Arguments: -f /dev/null new-session -s "AMPRedVerse-MC" -d "cd '/home/AMP/.ampdata/instances/RedVerse-MC' --; /home/AMP/.ampdata/instances/RedVerse-MC/AMPLinuxx8664 "

[20:32:39] [ModuleShared:daspendy Debug] : Started process with ID 539

[20:32:40] [InstanceManager:daspendy Notice] : AMP instance RedVerse-MC is now running.

That's what came from the log file.

Thanks,

Andrew

Mike posted this 26 October 2017

Check its log file, it'll be in the instances directory in ~/.ampdata

Spendy posted this 26 October 2017

Hey,

I am using AMP but when I try to start the server the instance just stays red. Any idea?

Thanks,

Spendy

Mike posted this 26 October 2017

Which type of key do you have? If you have an AMP key then you use the Minecraft module rather than the McMyAdmin module. They're the same thing aside from which type of key they take.

Spendy posted this 26 October 2017

Hey Mike,

Screen worked. Just wondering what I need to do to run McMyAdmin after I install AMP. I set up a new instance with MyMcAdmin selected but it seems to do nothing when I try and start the instance.

Do you guys have walkthrough on what to do once it is installed?

Thanks,

Spendy

Mike posted this 25 October 2017

Try running screen before starting the instance manager.

  • Liked by
  • Spendy
Spendy posted this 25 October 2017

Hey,

Did that now I am getting different types of errors than before:

[New LWP 11197] [New LWP 11195] [New LWP 11194] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x00007fcbe9ae0a0b in do_futex_wait.constprop.1 () from /lib64/libpthread.so.0   Id   Target Id         Frame   4    Thread 0x7fcbe28c2700 (LWP 11194) "ampinstmgr" 0x00007fcbe9ade945 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0   3    Thread 0x7fcbe20c1700 (LWP 11195) "Finalizer" 0x00007fcbe9ae0a0b in do_futex_wait.constprop.1 () from /lib64/libpthread.so.0   2    Thread 0x7fcbe1ec0700 (LWP 11197) "ampinstmgr" 0x00007fcbe9ae2189 in waitpid () from /lib64/libpthread.so.0
* 1    Thread 0x7fcbe9f04780 (LWP 11193) "ampinstmgr" 0x00007fcbe9ae0a0b in do_futex_wait.constprop.1 () from /lib64/libpthread.so.0
Thread 4 (Thread 0x7fcbe28c2700 (LWP 11194)):
#0  0x00007fcbe9ade945 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x0000000000598358 in GC_wait_marker () at pthread_support.c:1903
#2  0x00000000005911ae in GC_help_marker (my_mark_no=5) at mark.c:1116
#3  0x0000000000596e25 in GC_mark_thread (id=0x0) at pthread_support.c:555
#4  0x00007fcbe9adae25 in start_thread () from /lib64/libpthread.so.0
#5  0x00007fcbe980834d in clone () from /lib64/libc.so.6
Thread 3 (Thread 0x7fcbe20c1700 (LWP 11195)):
#0  0x00007fcbe9ae0a0b in do_futex_wait.constprop.1 () from /lib64/libpthread.so.0
#1  0x00007fcbe9ae0a9f in __new_sem_wait_slow.constprop.0 () from /lib64/libpthread.so.0
#2  0x00007fcbe9ae0b3b in sem_wait@@GLIBC_2.2.5 () from /lib64/libpthread.so.0
#3  0x00000000004ad7c9 in mono_os_sem_wait (flags=MONO_SEM_FLAGS_ALERTABLE, sem=0x25179e0 <finalizer_sem>) at ../../mono/utils/mono-os-semaphore.h:209
#4  mono_coop_sem_wait (sem=0x25179e0 <finalizer_sem>, flags=<optimized out="">) at ../../mono/utils/mono-coop-semaphore.h:40
#5  finalizer_thread (unused=unused@entry=0x0) at gc.c:907
#6  0x0000000000534ec8 in start_wrapper_internal (stack_ptr=0x7fcbe20c0d18, start_info=0x0) at threads.c:835
#7  start_wrapper (data=0x4319450) at threads.c:887
#8  0x00000000005741c2 in inner_start_thread (data=0x4328c80) at mono-threads.c:1165
#9  0x0000000000597f76 in GC_start_routine (arg=0x7fcbe9e60fc0) at pthread_support.c:1508
#10 0x00007fcbe9adae25 in start_thread () from /lib64/libpthread.so.0
#11 0x00007fcbe980834d in clone () from /lib64/libc.so.6
Thread 2 (Thread 0x7fcbe1ec0700 (LWP 11197)):
#0  0x00007fcbe9ae2189 in waitpid () from /lib64/libpthread.so.0
#1  0x0000000000640009 in mono_handle_native_crash (signal=<optimized out="">, ctx=<optimized out="">, info=<optimized out="">) at mini-exceptions.c:2567
#2  <signal handler="" called="">
#3  0x00007fcbe97451f7 in raise () from /lib64/libc.so.6
#4  0x00007fcbe97468e8 in abort () from /lib64/libc.so.6
#5  0x0000000000657314 in mono_log_write_logfile (log_domain=<optimized out="">, level=<optimized out="">, hdr=<optimized out="">, message=<optimized out="">) at mono-log-common.c:137
#6  0x000000000057f57b in monoeg_g_logv (log_domain=0x0, log_level=G_LOG_LEVEL_ERROR, format=0x2212dd0 "* Assertion at %s:%d, condition `%s' not met\n", args=0x7fcbe1ebfae8) at goutput.c:115
#7  0x000000000057f6dc in monoeg_assertion_message (format=0x2212dd0 "* Assertion at %s:%d, condition `%s' not met\n") at goutput.c:135
#8  0x00000000005737e0 in mono_thread_info_suspend_lock_with_info (info=0x0) at mono-threads.c:1026
#9  0x0000000000573835 in mono_thread_info_suspend_lock () at mono-threads.c:1041
#10 0x0000000000486485 in on_gc_notification (event=GC_EVENT_PRE_STOP_WORLD) at boehm-gc.c:502
#11 0x000000000059617f in GC_stop_world () at pthread_stop_world.c:613
#12 0x000000000058873e in GC_stopped_mark (stop_func=0x587d6b <gc_never_stop_func>) at alloc.c:503
#13 0x000000000058846b in GC_try_to_collect_inner (stop_func=0x587d6b <gc_never_stop_func>) at alloc.c:382
#14 0x0000000000589720 in GC_collect_or_expand (needed_blocks=1, ignore_off_page=0) at alloc.c:1053
#15 0x00000000005899f4 in GC_allocobj (sz=256, kind=1) at alloc.c:1133
#16 0x000000000058dbf6 in GC_generic_malloc_inner (lb=1656, k=1) at malloc.c:136
#17 0x0000000000597104 in GC_new_thread (id=140513645430528) at pthread_support.c:762
#18 0x0000000000597d07 in GC_start_routine_head (arg=0x7fcbe9d62e00, base_addr=0x7fcbe1ebfe9c, start=0x7fcbe1ebfe90, start_arg=0x7fcbe1ebfe88) at pthread_support.c:1416
#19 0x0000000000597f06 in GC_start_routine (arg=0x7fcbe9d62e00) at pthread_support.c:1502
#20 0x00007fcbe9adae25 in start_thread () from /lib64/libpthread.so.0
#21 0x00007fcbe980834d in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x7fcbe9f04780 (LWP 11193)):
#0  0x00007fcbe9ae0a0b in do_futex_wait.constprop.1 () from /lib64/libpthread.so.0
#1  0x00007fcbe9ae0a9f in __new_sem_wait_slow.constprop.0 () from /lib64/libpthread.so.0
#2  0x00007fcbe9ae0b3b in sem_wait@@GLIBC_2.2.5 () from /lib64/libpthread.so.0
#3  0x000000000059811e in GC_pthread_create (new_thread=0x7ffc83b7c9f0, attr=0x7ffc83b7ca00, start_routine=0x574140 <inner_start_thread>, arg=0x4718250) at pthread_support.c:1592
#4  0x0000000000487265 in mono_gc_pthread_create (new_thread=new_thread@entry=0x7ffc83b7c9f0, attr=attr@entry=0x7ffc83b7ca00, start_routine=start_routine@entry=0x574140 <inner_start_thread>, arg=arg@entry=0x4718250) at boehm-gc.c:1424</inner_start_thread></inner_start_thread></gc_never_stop_func></gc_never_stop_func></optimized></optimized></optimized></optimized></signal></optimized></optimized></optimized></optimized></finalizer_sem></finalizer_sem>

Mike posted this 25 October 2017

System libs are outdated, do a yum update and yum upgrade.

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