Bot is stopping without any reason on OkCoin. Can i get some support please?
Same here, and others having the same problem. Haven't heard anything from Sai in days. Whats going on?
It might be helpful for everyone if you guys post your logs.
Hey guys, like @chowdan said, can you post your logs.
I know some of you're having problems with bots hanging completely. I often see rate limit errors in the logs and i am trying to figure out why bots are hitting the limit. I know one of you simply ran a bot that just logged the tick and it still hung up.
Ok the log just says the price at the certain time, and then no new ticks come though. It's the same problem I've been having for weeks now, and sent you log outputs from those. The ticks just stop, that's it.
It got much worse recently. before, my bots would run for a few days on okcoin without stopping, now only for a few hours. Can you please contact Okcoin and see what the problem is? I've sent them a few emails and haven't gotten any response. Apparently they are unwilling or incapable of coding a reliable API interface.
Maybe just say the hell with Okcoin.cn and get Huobi working instead? With all the hacking problems and API issues OKcoin has, I'd feel more secure trading on huobi anyway.
Thanks for looking at this issue
Ok here is a log from a bot that is still running, as you can see the logging just stops and the bot doesn't restart. Need better bot monitoring for OKcoin bots PLEASE!!! Or just add Huobi instead!! PLEASE!!
I have literally spent months writing this bot, paid almost 1000$ for Tradewave memberships, the bot works great, but only on 0 fee exchanges because the trade frequency is rather high, and now I can't use it.
I am terrible at manual trading, I've lost about 60% of my trading fund over the past 3 weeks because my damn bots won't run!!
CAN YOU PLEASE COME UP WITH A SOLUTION @sai
[2015-11-15 01:07:38] Starting...
[2015-11-15 01:07:39] Found existing storage containing 26 keys.
[2015-11-15 01:07:41] >> Starting portfolio:
[2015-11-15 01:07:42] >> [0.004 LTC, 0.01232 CNY]
[2015-11-15 01:08:00] fastd 46.283152 close 20.540000 mode 0.000000
[2015-11-15 01:08:00] currency: 0.01 assets: 0.00
[2015-11-15 01:08:00] Warning: you attempted to plot Numpy's NaN type for the key "DI_plus". We converted it to zero.
[2015-11-15 01:08:00] Start Date: 2015-11-15 06:07:42
[2015-11-15 01:08:00] Day: 0 Trades: 0 Frequency 0.0
[2015-11-15 01:08:00] CNY 0.1 / 0.1 / -0.0 ROI
[2015-11-15 01:08:00] LTC 0.0 / 0.0 / -0.2 ROI
[2015-11-15 01:08:00] ***************************************
[2015-11-15 01:23:00] fastd 66.159059 close 20.560000 mode 0.000000
[2015-11-15 01:38:00] fastd 100.000000 close 20.570000 mode 0.000000
[2015-11-15 01:53:00] fastd 100.000000 close 20.580000 mode 0.000000
[2015-11-15 02:08:00] fastd 61.160128 close 20.570000 mode 0.000000
[2015-11-15 02:23:00] fastd 11.453100 close 20.560000 mode 0.000000
[2015-11-15 02:38:00] fastd 33.708846 close 20.560000 mode 0.000000
[2015-11-15 02:53:00] fastd 44.123257 close 20.570000 mode 0.000000
[2015-11-15 03:08:00] fastd 64.086844 close 20.560000 mode 0.000000
[2015-11-15 03:23:00] fastd 55.893404 close 20.580000 mode 0.000000
[2015-11-15 03:38:00] fastd 79.714646 close 20.580000 mode 0.000000
[2015-11-15 03:38:00] currency: 0.01 assets: 0.00
[2015-11-15 03:53:00] We had trouble updating your portfolio so your tick() was not called this time around. This usually happens when the exchange is experiencing connectivity issues and should correct itself.
[2015-11-15 04:23:00] fastd 100.000000 close 20.640000 mode 0.000000
[2015-11-15 04:38:00] fastd 80.745763 close 20.650000 mode 0.000000
[2015-11-15 04:53:00] fastd 7.709298 close 20.600000 mode 0.000000
[2015-11-15 05:08:00] fastd 3.161704 close 20.580000 mode 0.000000
[2015-11-15 05:23:00] fastd 26.597461 close 20.600000 mode 0.000000
[2015-11-15 05:38:00] We had trouble updating your portfolio so your tick() was not called this time around. This usually happens when the exchange is experiencing connectivity issues and should correct itself.
[2015-11-15 06:08:00] fastd 21.548983 close 20.540000 mode 0.000000
[2015-11-15 06:08:00] currency: 0.01 assets: 0.00
[2015-11-15 06:23:00] fastd 0.000000 close 20.510000 mode 0.000000
You should move your funds before you incur any losses. As much as I want to release Huobi, I need to ensure it goes through all the testing channels. If you want to switch to another trading platform meanwhile, please do so and I will give you a month free when you want to trade again on TW after Huobi release.
Let me know
Appreciate the offer,that sounds good, I'll do that. If Huobi is functional now though, and you would be able to connect me, I don't mind the lack of backtest data, I've already tested on Huobi data also.
One reason i am sticking with TW is due to the way @sai handles everything.
@coinero - I would suggest jumping ship to another platform for a month or so, then taking up @sai on that offer when Huobi launches. I was never a fan of Cryptotrader, feel their site and functionality of their system and the performance was pretty crappy TBH, however I would not be confident in running a bot on a exchange that hasn't been fully tested. Its not about a lack of backtest data, its more about unknown bugs that could be there that cause your bot to send a sell/buy signal when not expected, or be flatout unstable causing your bot to not operate what so ever.
The chance of an unknown issue, due to lack of testing could cause you to lose far more than expected.
I agree about Tradewave vs Cryptotrader and I really like the way Sai handles things also.
However, as a test, I have been running a bot on Okcoin.cn through CT for the past few days and am not having any connection issues or bot-stopping issues, although the bot did automatically restart a few times. So maybe the bot auto-restart needs to be handled differently? Apparently pings are still being returned by the bots even though they are "frozen". Perhaps instead of pinging the bot, the engine could be changed so that running bots send a ping every tick they receive data from the exchange API. That way, if they are stuck and not getting data, they can be restarted automatically instead of being left in a "frozen" state.
Unfortunately my TW bot uses indicators with multiple intervals running on 5 minute ticks, and I'm a pretty novice programmer, so coding it up for CT will be very difficult for me. Guess I will have to give it a shot until this gets sorted out.
We are close to testing Huobi out. Remember that they changed their API from BitYes.com to Huobi , which would mean that we have to reimplement the entire exchange and then test again. We the resources we have, its bound to take some time. Furthermore, we hit some obstacles due to recent DDOS on chinese exchanges.
Having said that, we apologize for the Okcoin inconsistencies. I have started looking deeper into the issue starting this week. Hopefully something good comes out of it.
Glad to hear it Mike. Didn't realize all that about Huobi, sounds like a lot of work, Hope you guys are able to figure things out soon!
Is there any update / work-around on the issue of bots silently stopping on okcoin?
As this is my main exchange, the only reason I use TW is having a bot on okcoin watching my back when I´m afk.
for the time being an idea for a dead man switch would also help, since there is no way to get notified if the bot freezes, but doesnt "stop".
Best I can imagine now is haveing the bot sending an email on every single tick and a second bot checking emails and setting off an alarm when no email arrives. But then again, I could simply run a local bot from haas or qt in the first place.
Bitfinex and BTCe are very stable.
You could use the "channels" feature to send okcoin info.current_time to a channel. Then run a bot on btce or finex that reads that channel. Any time
if btce_time > (okcoin_time +x):
Yeah, the fees are the problem. My bot trades about once per day, and does very well with 0 fees, but the spread and fees on finex or BTC-e kills it
no... I'm saying you can run a bot on btce or finex just to give you email alerts whenever they sense the okcoin bot is dead.
So at okcoin you would run your trading code and broadcast a time stamp:
CHANNEL = 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
PAIR = info.primary_pair
if data[PAIR].ma(10) > data[PAIR].ma(90):
storage.okcoin_time = info.current_time
Then at btce:
CHANNEL = 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
storage.okcoin_time = storage.get('okcoin_time', info.current_time)
channel = storage(channel=CHANNEL)
storage.okcoin_time = channel.okcoin_time
latency = info.current_time - storage.okcoin_time
if latency > 3600:
# I haven't heard from okcoin in over an hour, send email
email(latency, subject="okcoin down")
I use a similar system to alert my users if the Honey Badger marketplace signal goes down.
I applied a patch for Okcoin that might fix the hung bot issue with okcoin. Can you guys please run your bots and let me know?
I had my okcny bot running last night and it froze/hung up after about 4 hours (while I was sleeping ofcourse).
Restarted just now and keeping fingers crossed.
Will post here if and when bot stops again.
Thanks to litepresence for the super fast and constructive reply!
There is just one thing with the channel/multi bot setup that worries me.
As it is not because of a connectivity issue that the bot freezes on okcoin (we all know the error message by now), but something that keeps the bot from even starting to execute the "tick" in his code, I dont really see how this can be okcoin specific.
next page →