Closed NeoBelerophon closed 8 years ago
Seeing the same today, 2014-02-27 14:05:58 (DEBUG): minimum trade treshold: 2014-02-27 13:04:58 UTC 2014-02-27 14:05:58 (DEBUG): processing 11 trade(s) 2014-02-27 14:05:58 (DEBUG): from 2014-02-27T13:04:59+00:00 to 2014-02-27T13:05:44+00:00 c [ { s: 784, o: 561, h: 561, l: 560, c: 560.187, v: 11.165906700000003, p: 560.449578615886 }, { s: 785, o: 560.187, h: 560.187, l: 560, c: 560, v: 0.5427232, p: 560.014720650232 }, { s: 784, o: 560.187, h: 561, l: 560, c: 560, v: 0.16381405, p: 560.198739099302 } ] s { s: 784, o: 561, h: 561, l: 560, c: 560.187, v: 11.165906700000003, p: 560.449578615886 } e undefined
Weird error 2
After this gekko crashes
This error is killing me, fortunately I am currently rewriting the way Gekko handles 1 min candles (core part of gekko) and persisting them to disk. So that should really fix this once and for all!
I can confirm this also happens with the cryptsy exchange made by mlmurray. Most of them seem to go away when I added timeouts to the http requests but that might be unrelated.
Can confirm I am also seeing this on BTC-e with 0.1.2, pulled fresh from github. It comes up after a while, and gekko crashes. I also run a second gekko on cexio which does not seem to have this issue..
c [ { s: 248, o: 561.999, h: 562, l: 555, c: 555, v: 123.3367699, p: 555.4418553820594 }, { s: 249, o: 555, h: 555, l: 555, c: 555, v: 7.870041999999999, p: 555.0000000000001 }, { s: 248, o: 555, h: 560, l: 554.8, c: 560, v: 18.237196289999996, p: 557.5807985370706 } ] s { s: 248, o: 561.999, h: 562, l: 555, c: 555, v: 123.3367699, p: 555.4418553820594 } e undefined
I get the weird 2 error also. and this happens too:
2014-02-27 21:15:32 (INFO): We have new trading advice! 2014-02-27 21:15:32 (INFO): Position to take: long 2014-02-27 21:15:32 (INFO): Market price: 559 2014-02-27 21:15:32 (INFO): Based on market time: 2014-02-27 21:15: 00
2014-02-27 21:15:32 (DEBUG): Processed trades, sleeping for a minute...
TypeError: Cannot read property 'ticker' of undefined at set (c:\gekko\exchanges\btce.js:108:31) at bound (c:\gekko\node_modules\lodash\dist\lodash.js:729:21) at Request._callback (c:\gekko\node_modules\btc-e\btc-e.js:62:16) at self.callback (c:\gekko\node_modules\btc-e\node_modules\request\index.js: 142:22) at Request.EventEmitter.emit (events.js:95:17) at ClientRequest.self.clientErrorHandler (c:\gekko\node_modules\btc-e\node_m odules\request\index.js:246:10) at ClientRequest.EventEmitter.emit (events.js:95:17) at CleartextStream.socketErrorListener (http.js:1547:9) at CleartextStream.EventEmitter.emit (events.js:95:17) at Socket.onerror (tls.js:1445:17)
Same issue here. I haven't tried debugging but sharing the log in case this helps someone. Gekko was running fine for 10 hours before the error was thrown by candleManager.js: https://github.com/askmike/gekko/blob/69e2b17bf3a551ce984725317b2120f4746b9818/core/candleManager.js#L794
2014-02-28 10:13:23 (DEBUG): Requested BTC/USD trade data from BTC-e ...
2014-02-28 10:13:23 (DEBUG): Fetched 150 new trades, from 2014-02-28 10:05:10 UTC to 2014-02-28 10:12:49 UTC
2014-02-28 10:13:23 (DEBUG): minimum trade treshold: 2014-02-28 10:11:53 UTC
2014-02-28 10:13:23 (DEBUG): processing 28 trade(s)
2014-02-28 10:13:23 (DEBUG): from 2014-02-28T10:12:20+00:00 to 2014-02-28T10:12:49+00:00
2014-02-28 10:13:23 (DEBUG): Skipping creation of already loaded database 2014-02-28
2014-02-28 10:13:23 (DEBUG): inserting candle 611 (2014-02-28 10:11:00 UTC) volume: 19.956357200000006
2014-02-28 10:13:23 (DEBUG): Processed trades, sleeping for a minute...
2014-02-28 10:14:11 (DEBUG): Requested BTC/USD trade data from BTC-e ...
2014-02-28 10:14:27 (DEBUG): Fetched 150 new trades, from 2014-02-28 10:08:13 UTC to 2014-02-28 10:13:57 UTC
2014-02-28 10:14:27 (DEBUG): minimum trade treshold: 2014-02-28 10:12:49 UTC
2014-02-28 10:14:27 (DEBUG): processing 42 trade(s)
2014-02-28 10:14:27 (DEBUG): from 2014-02-28T10:12:59+00:00 to 2014-02-28T10:13:57+00:00
2014-02-28 10:14:27 (DEBUG): Skipping creation of already loaded database 2014-02-28
2014-02-28 10:14:27 (DEBUG): inserting candle 612 (2014-02-28 10:12:00 UTC) volume: 14.730925829999999
2014-02-28 10:14:27 (DEBUG): inserting candle 613 (2014-02-28 10:13:00 UTC) volume: 7.893141100000001
2014-02-28 10:14:27 (DEBUG): Processed trades, sleeping for a minute...
2014-02-28 10:15:15 (DEBUG): Requested BTC/USD trade data from BTC-e ...
2014-02-28 10:15:15 (DEBUG): Fetched 150 new trades, from 2014-02-28 10:09:43 UTC to 2014-02-28 10:14:45 UTC
2014-02-28 10:15:15 (DEBUG): minimum trade treshold: 2014-02-28 10:13:57 UTC
2014-02-28 10:15:15 (DEBUG): processing 33 trade(s)
2014-02-28 10:15:15 (DEBUG): from 2014-02-28T10:13:59+00:00 to 2014-02-28T10:14:45+00:00
c [ { s: 613,
o: 551.5,
h: 552.997,
l: 551.5,
c: 552.997,
v: 7.893141100000001,
p: 551.9916412373143 },
{ s: 614,
o: 552.997,
h: 553,
l: 552.997,
c: 552.997,
v: 3.6666197000000005,
p: 552.998530746971 },
{ s: 613,
o: 551.5,
h: 553.899,
l: 551.5,
c: 553.899,
v: 21.172104500000003,
p: 553.3696096081284 } ] s { s: 613,
o: 551.5,
h: 552.997,
l: 551.5,
c: 552.997,
v: 7.893141100000001,
p: 551.9916412373143 } e undefined
Just some extra info.... in case it helps... I did not get this error while trading on cexio, with 5,15, or 60 minute candles. I did however get it constantly on BTC-e with 5 and 15 minute candles, but since switching to 60 minute candles I have not seen it since. I'm not sure if the recent code push (I pull just about daily) addressed this issue, but for several days before that, using 60 minute candles eliminated this for me, even before that pull.
I am looking at this same issue.
I can tell you it has to do with the candles being out of order. For example, if you look at all the candle data for people with the issue above you will see they have one candle that is out of order "s: 614" then "s: 613" for example.
Found a fix that appears to be working
In candleManager.js:
Manager.prototype.addEmtpyCandles = function(candles, start, end) {
candles = this.sortCandles(candles); // add this line to fix
fix confirmed on cryptsy
+1 for this.sortCandles
should be fixed in gekko 0.2!
Hi,
I had running gekko for 3-4 days and it stopped with this message below. Also when I restart gekko this message is shown.