NuBot issues

[masterOfDisaster]

It might be good for those who can’t create issues at Bitbucket to have a place for posting issues, discussing them, getting support here in the forum.

NuBot RPC connection issues to nud

I encountered a strange issue trying to help troubleshooting NuBot:

08:58:32.805 [main] ERROR - can't connect to Nu com.nubits.nubot.bot.NuBotConnectionException: Problem with nud connectivity [c.n.n.l.MainLaunch:173]

nud is version

"version" : "v2.1.1-RC1-4-g047e5fe-dirty-beta",

and runs locally.
The RPC settings are valid - I copied them from the Poloniex dual side and the hitBTC sell side NuBot that run on the same machine.
They can connect to the local nud and broadcast liquidity.

Is there a limit how many NuBots can use the same nud?

[nmei]

Good thread.

I’m using NuBot for LP to the pool. I don’t know if it is NuBot or Bittrex.
But I keep getting place order errors on Bittrex that causes the program to hang. It won’t place any more orders because there were too many errors. I will post the actual info this afternoon.

17:07:14.369 [checkOrders] ERROR - ApiError [3 : No Connection] [c.n.n.s.OrderManager:295]
17:07:21.584 [Strategy Secondary Task] ERROR - Method=returnOpenOrders failed too many times and timed out. attempts = 8 [c.n.n.t.w.PoloniexWrapper:615]

[masterOfDisaster]

There seems to be a strange limit of “trades”, but I’m sure that isn’t really related to trades, at least not literally.
I hit that limit freuqently and need to restart NuBot at hitBTC daily until this is fixed.
I think it’s related to NuBot, because the same limit is found with NuBot at hitBTC and Poloniex - it would be a strange coincidence to find the same limit at two independent exchanges.

From NuBot log:

2016-05-11
14:02:14.258 [checkOrders] WARN  - Liquidity info submitted:
        tier=1 buy=0.0 sell=500.0 identifier=1:NBTBTC:hitbtc:0.4.1_1462854354364_eebe17 response=true
        tier=2 buy=4.28 sell=1495.718 identifier=2:NBTBTC:hitbtc:0.4.1_1462854354364_eebe17 response=true [c.n.n.t.CheckOrdersTask:142]
14:02:30.154 [checkNud] INFO  - Executing class com.nubits.nubot.tasks.CheckNudTask [com.nubits.nubot.tasks.CheckNudTask:37]
14:02:49.942 [Strategy Secondary Task] INFO  - Sell-Wall size :  : 500.0 NBT [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:539]
14:02:49.950 [Strategy Secondary Task] INFO  - Buy-Wall size :  : 0.0 NBT [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:544]
14:02:59.834 [priceTriggerTask] INFO  - Price Updated. bitfinex:1 BTC = 453.2 USD [com.nubits.nubot.tasks.PriceMonitorTriggerTask:359]
14:03:00.154 [checkNud] INFO  - Executing class com.nubits.nubot.tasks.CheckNudTask [com.nubits.nubot.tasks.CheckNudTask:37]
14:03:30.154 [checkNud] INFO  - Executing class com.nubits.nubot.tasks.CheckNudTask [com.nubits.nubot.tasks.CheckNudTask:37]
14:03:30.947 [Strategy Secondary Task] INFO  - Sell-Wall size :  : 500.0 NBT [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:539]
14:03:30.954 [Strategy Secondary Task] INFO  - Buy-Wall size :  : 0.0 NBT [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:544]
14:04:00.154 [checkNud] INFO  - Executing class com.nubits.nubot.tasks.CheckNudTask [com.nubits.nubot.tasks.CheckNudTask:37]
14:04:01.711 [priceTriggerTask] INFO  - Price Updated. bitfinex:1 BTC = 453.04 USD [com.nubits.nubot.tasks.PriceMonitorTriggerTask:359]
14:04:11.930 [Strategy Secondary Task] INFO  - Sell-Wall size :  : 500.0 NBT [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:539]
14:04:11.937 [Strategy Secondary Task] INFO  - Buy-Wall size :  : 0.0 NBT [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:544]
14:04:24.473 [checkOrders] WARN  - Liquidity info submitted:
        tier=1 buy=0.0 sell=500.0 identifier=1:NBTBTC:hitbtc:0.4.1_1462854354364_eebe17 response=true
        tier=2 buy=4.28 sell=1495.718 identifier=2:NBTBTC:hitbtc:0.4.1_1462854354364_eebe17 response=true [c.n.n.t.CheckOrdersTask:142]
[...]
14:06:41.341 [pool-1-thread-1] WARN  - Maximum number of trades retrieved is 1000 due to technical limitation of HitBtc [c.n.n.t.w.HitbtcWrapper:646]
14:06:41.583 [Thread-6] INFO  - Order clear request successful [com.nubits.nubot.bot.NuBotBase:397]
14:06:41.587 [Thread-6] INFO  - Resetting Liquidity Info before quit [com.nubits.nubot.bot.NuBotBase:419]
14:06:41.704 [Thread-6] INFO  - Tier1 liquidityinfo reset OK  [com.nubits.nubot.bot.NuBotBase:428]
14:06:41.788 [Thread-6] INFO  - Tier2 liquidityinfo reset OK  [com.nubits.nubot.bot.NuBotBase:441]
14:06:41.791 [Thread-6] INFO  - session statistics [com.nubits.nubot.bot.NuBotBase:334]
14:06:41.794 [Thread-6] INFO  - totalOrdersSubmitted 460 [com.nubits.nubot.bot.NuBotBase:336]
14:06:41.962 [Thread-6] INFO  - after 1 day 9 hours 40 minutes 47 seconds uptime on hitbtc [nbt_btc] [com.nubits.nubot.bot.NuBotBase:345]
14:07:53.701 [Thread-6] INFO  - Logs of this session saved in logs/bot_sessions/0.4.1_1462854354364_eebe17.zip [com.nubits.nubot.bot.NuBotBase:461]
14:07:53.734 [Thread-6] INFO  - ** end of the session ** [com.nubits.nubot.bot.NuBotBase:464]
14:07:53.737 [Thread-6] INFO  - defined session log path logs/idles/1462854274426 [com.nubits.nubot.bot.Global:116]
14:07:54.060 [Thread-6] INFO  - Exit main [com.nubits.nubot.launch.ShutDownProcess:62]

@zoro, as soon as you find that pattern (liquidity broadcasts without T1 and T2 information for an extended time) in the log, it might be necessary to restart NuBot.
You know for sure that it was necessary, if you find

[pool-1-thread-1] WARN  - Maximum number of trades retrieved is 1000 due to technical limitation of...

in the shutdown sequence.

@desrever, can you give us a hint regarding this limit?