-
Notifications
You must be signed in to change notification settings - Fork 32
Open
Description
Hi, I'm trying to run my own open source console by following the official guide. I've created a fresh EC2 instance according to the instructions with below specifications.
EC2 Instance:
- Instance type: t2.xlarge
- Platform: Cent OS (Inferred)
- AMI ID: ami-002070d43b0a4f171
- Volume size (GiB): 150
I've done all the steps one by one but when I run the docker-compose up command, the helium_router container gives me a strange error, I even tried creating a new instance and retried everything from start, It's responding with the same error everytime.
Error:
helium_router | Crash dump is being written to: erl_crash.dump...done
helium_router | make: *** [Makefile:51: run] Error 1
helium_router | _build/default/rel/router/bin/router foreground
helium_router | Exec: /usr/local/lib/erlang/erts-12.3.1/bin/erlexec -noinput +Bd -boot /opt/router/_build/mainnet/rel/router/releases/1.0.0/start -mode embedded -boot_var SYSTEM_LIB_DIR /usr/local/lib/erlang/lib -config /opt/router/_build/mainnet/rel/router/releases/1.0.0/sys.config -args_file /opt/router/_build/mainnet/rel/router/releases/1.0.0/vm.args -- foreground
helium_router | Root: /opt/router/_build/mainnet/rel/router
helium_router | /opt/router/_build/mainnet/rel/router
helium_router | {"Kernel pid terminated",application_controller,"{application_start_failure,router,{{shutdown,{failed_to_start_child,router_console_sup,{shutdown,{failed_to_start_child,router_console_api,{bad_return_value,get_token}}}}},{router_app,start,[normal,[]]}}}"}
helium_router | Kernel pid terminated (application_controller) ({application_start_failure,router,{{shutdown,{failed_to_start_child,router_console_sup,{shutdown,{failed_to_start_child,router_console_api,{bad_return_value,get_token}}}}},{router_app,start,[normal,[]]}}})
Error Screenshot:
Can anyone please let me know what I'm missing or doing wrong ?
Metadata
Metadata
Assignees
Labels
No labels
