BTCe: bitcoincharts returned an error, retrying..

[brampower]

It seems like the BTCe bot is not working anymore. With debug turned on, I only get this error message:

2013-12-11 21:01:29 (DEBUG): bitcoincharts returned an error, retrying..
2013-12-11 21:01:31 (DEBUG): bitcoincharts returned an error, retrying..
2013-12-11 21:01:34 (DEBUG): bitcoincharts returned an error, retrying..
2013-12-11 21:01:34 (DEBUG): bitcoincharts returned an error, retrying..

And it keeps going. The website is definitely up, so that's not the problem.

[nikita-leonov]

Looks more like a bitcoincharts issue now. It does not work for any exchange.

[nikita-leonov]

Could it be a quote limit? "Don't query more often than once every 15 minutes!" - http://bitcoincharts.com/about/markets-api/

[GoodDragon]

I' using 30 interval but and just noticed from log file that bitcoincharts didn't respond between 02:30 - 4:00 (GMT time).

That have been happening sometimes earlier too.

Only good solution this would be change Gekko to get trades from BTC-e directly but like you see from #23
it isn't so easy job.

[GoodDragon]

Actually this just happened again. There was at least 10 retrying and then I stopped gekko and restarted it and looks that it is working again.

Probably 10 seconds retry time is little too short? I just changed it to 30. You can find it for here if you want try: https://github.com/askmike/gekko/blob/master/exchanges/bitcoincharts.js#L56

[askmike]

I want to up the retry time, but I need to be sure it works. If anybody has any information if a retry of 30 seconds fixes it, please let me know.

[GoodDragon]

Actually looks that it is not totally fix that. There is still lot of these errors on sometimes.

[askmike]

Is this still effecting anyone?

[GoodDragon]

I just checked my Gekko logs from 18th December to now and haven't see any see any retries there (and yes. I have debug mode enabled). Probably there have been some problem on bitcoincharts side earlier.

[askmike]

A new version of Gekko (in development, need help testing) uses the BTC-e API and holds a local database of all historical data. As soon as that's done we are not stuck with the BTC-e API anymore. If you guys can help me test / figure it out we can have this version as soon as possible.

More info here.

[bugron]

@askmike is this still an issue?

[askmike]

No!