binance Child process has died
#1
hi
binance - live gekkos - paper trader

RECEIVED ERROR IN GEKKO 638778226990853

Child process has died.

It stopped after 23 hours of work.

ubuntu server -- gekko 0.5.12 -- gekko ui 0.2.0
------------------------------
uiconfig.js
const CONFIG = {

  headless: true,

----------------------------------------

I am working on the server computer, the terminal is not connected
---------------------------------------------

Why the logs folder is empty


picture is exciting
thank you


Attached Files
.png   fEkran Görüntüsü - 2018-01-21 18-39-04.png (Size: 261.51 KB / Downloads: 16)
  Reply
#2
self catering :=))

if you install ubuntu on the same computer and run gekko and make headless settings (true), you get this error, at the end of 23 hours in the binance market
---------------------------------------------------------
but you should install ubuntu headless and run the gekko script from the terminal, as you did in the headless settings (true)
---------------------------------------------------------

i am sure this error is in ubuntu or gekko or binance market
  Reply
#3
I have the exact same issue on Ubuntu Server running in the cloud using Binance exchange api. After about a day the strategy runner just stops and I have to restart it. Does anyone have a fix?
  Reply
#4
hi
You are running the ubuntu server headless

Is the server separate from the terminal ?
  Reply
#5
Can anyone who is still experiencing this upload logs and post a link to it here? If you experience this using the UI the logs are stored in the `gekko/logs` folder, else they are displayed in the terminal.
  Reply
#6
(02-03-2018, 11:36 AM)askmike Wrote: Can anyone who is still experiencing this upload logs and post a link to it here? If you experience this using the UI the logs are stored in the `gekko/logs` folder, else they are displayed in the terminal.
hi
logs file is empty



The terminal gives this ubuntu error in 2 or 3 days


get the image when it recreates
  Reply


Forum Jump:


Users browsing this thread: