What was the issue?
I recognized that thereâs still liquidity information of past sessions (0.3.2a_1451262162869_8d7dd5, 0.3.2a_1451153341336_52e85e) associated to the custodial addresses my Poloniex gateways have:
Overview:
Sat Jan 2 00:21:58 UTC 2016
status of sell side gateway:
nud getliquidityinfo B | grep BETwD8nSjtj9ADSvej2na34xmsMYwPRymv -A 2
"BETwD8nSjtj9ADSvej2na34xmsMYwPRymv" : {
"buy" : 15082.05,
"sell" : 0.0
status of buy side gateway:
nud getliquidityinfo B | grep BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP -A 2
"BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP" : {
"buy" : 0.07,
"sell" : 5233.1688
Details:
nud getliquiditydetails B | grep 0.3.2a_1451262162869_8d7dd5 -A 2
"1:NBTBTC:poloniex:0.3.2a_1451262162869_8d7dd5" : {
"buy" : 0.0,
"sell" : 0.0
--
"2:NBTBTC:poloniex:0.3.2a_1451262162869_8d7dd5" : {
"buy" : 15077.82,
"sell" : 0.0
[...]
nud getliquiditydetails B | grep 0.3.2a_1451153341336_52e85e -A 2
"1:NBTBTC:poloniex:0.3.2a_1451153341336_52e85e" : {
"buy" : 0.0,
"sell" : 0.0
--
"2:NBTBTC:poloniex:0.3.2a_1451153341336_52e85e" : {
"buy" : 0.03,
"sell" : 5229.0443
This messes up the reported T2 liquidity. How can I remove this information? The sessions have long been stopped by graceful shutdown of NuBot.
edit: just for the record - this issue was solved.
@desrever showed me how to correct that wrong broadcast information.
It seems that sessions were not set to 0 liquidity when NuBot was shut down, because nud had crashed (disk space was exchausted from the NuBot logs) and could not be used to reset the liquidity.
