-
Notifications
You must be signed in to change notification settings - Fork 2k
Zenbot stuck with the "buying" message #326
Comments
possibly related: Mine is stuck with the "sold" message even though nothing was sold:
|
Assume this is not zenbot but the option --order_type=maker. If using --order_type=taker the fees are higher but the execution is faster. |
I'm seeing the same thing with GDAX. It happened recently. It's also seems c.order_poll_time and c.order_adjust_time is now being ignored. 2017-07-04 15:59:30 53.19 LTC-USD +0.0% 155 +++ -0.36% buying 0.00 LTC 37.68 USD -0.9% -2.2% Usually I'd get statistics back saying that it bought. The sim works fine. |
@typicalaimster Have you found a solution? |
Yes. If I recall, in my case, I found that I had two zenbot containers launched. They were both trading the same currency. One that I launched, then another one that auto launched. I edited the docker-compose.yml and removed restart:always.. Then I quickly outgrew the docker container. I've since deployed Zenbot and Mongo onto its own stand alone EC2 instance in the same region as GDAX. |
Zenbot stuck with the "buying" message even many hours after the buy, even it is not enough funds left for a new buy. The buy took place 4:20:28. Now it is 8:30
From the exchange log:
From Zenbot:
The text was updated successfully, but these errors were encountered: