thanks for the info. some times i see 10-20 INFO “zero” lines (it means nothing is payed although order in place!)
then i may see 5-10 correct INFO lines and then the circle continues!
very sad
Yah, that’s not how it should be. I wish I knew the answer, but the code gets complicated sometimes. The only advice I can give, I guess, is to see how it behaves on restart and if you like that reduce your reset timer to 0.25 or possibly even lower.
Please keep reporting the bugs as you see them at your convenience. Every time I go through the code for whatever reason I try to keep my eyes open for potential bug fixes.
perhaps the socket errors (10060) are to blame? what they actually mean?
can you perform a server update/restart to see if it fixes somehow?
I’m being cautious about restarting and upgrading the server. I will look into it tonight though, as I was messing with the updated stuff last night for fixed cost. I also need to rearrange my server’s folder structure and possibly pull some stuff on github. I usually like to restart servers each term, but I can check it out.
Socket errors come from you not connecting well with the server. It has nothing to do with bter and is a problem with communication between operator and participant. A server restart could potentially fix it, but I would be surprised. The server is in New York.
the nupond server for bter nbt/btc is down?
but the bter nbt/cny is up! are they different servers?
is
server=nupond.net:3334
unit=btc
exchange=bter
but I received socket errors before I stopped the bot. Can’t get it running again…
is
server=nupond.net:3333
unit=cny
exchange=bter
and is running:
2015/09/30-06:17:54 INFO: starting PyBot for cny on bter
2015/09/30-06:18:32 INFO: successfully deleted all orders for cny on bter
2015/09/30-06:18:32 INFO: waiting 11.01 seconds to synchronize with other trading bots for cny on bter
2015/09/30-06:18:55 INFO: bter - balance: 0.00000000 rate: 0.00% ppm: 0.00000000 efficiency: 0.00% rejects: 0 missings: 0 - APIKEY
The server (nupond.net) is the same, the ports are different (3333, 3334!).
And there’s another server for the fixed cost test run:
server=45.55.55.197:3333
unit=btc
exchange=bter
As far as I’m aware, this test run doesn’t yet pay out - it’s a test run!
My logs state that I have ‘too many open files’. I’m in the process of restarting both servers and doing payouts.
Edit: There you are. I have no idea how to prevent this error in the future. Maybe when I change the file structure of the server it will be better. At the very least the error only occurs when the server has been running for a long time and somewhere there’s files being opened that aren’t getting closed. I’m guessing it’s the log files.
You aren’t using a reverse proxy, are you?
It’s a typical I/O error with nginx when load is getting too high
if i say i don’t know what a reverse proxy is, does that mean no?
I’m running both servers in one python directory (which is a bad idea because the logs get confusing, but it’s what I’m doing). I had both server scripts running for 27 days straight.
yes
A little off topic:
We do it with NuPool. In our case apache2 acts as reverse proxy (port 80), which is passing requests from the clients to the hidden alp server (port 3333) and forwards the answers back to the client.
It’s a stability plus, because we can switch out the alp server any time if we need to, and it increases the security of our core infrastructure, because our web traffic is 100% behind CloudFlare CDN. DDOSing us is not impossible, but it’s much harder that way.
We’re also able to reroute our client traffic within 1-5 minutes to a backup server, if we needed too.
I also use apache2, according to the guidelines specified by @woolly_sammoth. I do not use CloudFlare.
My LPs are having a hard time getting out of CNY, I feel. Remember that many of the alt coins on bter have cny pairs. I think someone could arbitrage BTS against poloniex right now with CNY back to NBT and make out on the deal, but I’d have to really do it out. With target reached on buy side, you could make more money getting back to the sell side anyway, so a small loss isn’t even that bad.
Alternatively, why are ya’ll selling on the btc pool and not the cny pool? If you don’t know about fill factor, we have a way (just ask if you don’t know ) to semi-continuously adjust funds such that when someone sells you NBT for your BTC, it puts a portion of that over to sell for CNY. The price feeds are such that the LP would be selling BTC for CNY at 0.7% above the Bitfinex price, so on a micro scale it’s a good deal. From a macro perspective, splitting your funds between the pools will get you the most funds if both become fixed cost or regularly operate at target.
I am taking down the server for a little while. I’m moving to the bigger server for real now.
Edit: Up and running. I broke the website, but I’ll fix that later. I also wasn’t able to import the full wallet, so I just dumped any private keys that had any balances (I have plenty of network addresses for submitting liquidity).
Ugh, so many issues. Ok, so I got the site up, but the bots are all being funky and either not running or not crediting properly. Please stand by.
Got BTC up and running, I was just dumb and ran server.py instead of fc_server.py. I’m still having troubles with CNY, the pool is currently not running as no one can connect to it anyway. I suspect something to do with port 3333, but I’m not sure.
Still issues?
I still don’t have the CNY pool up. I will work on it again in a little while. I’ll need to switch it over to fixed cost once the grant passes anyway, but I will try to get it up and running with fixed reward in the meantime.
No problem. Just saw that they were stuck. You do top notch work.
2015/11/11-15:52:57 INFO: bter - balance: 0.05963369 rate: 330.12% ppm: 4.56577188
AWESOME!
Thanks!
Things I’ve improved this time around (without the changes the grant will introduce):
- Bigger Server. Nud failed again last night, this should fix it.
- Fixed the deviation bug. This was serious, I’m really surprised we didn’t catch it earlier.
- Fillfactor now works on both buy and sell side. This constitutes a Tier 2 strategy.
- Shift is now adaptive. I’ll say more about what this means later.
- One more stab at the ordermatch bug, copying what sam did.
Most of these bugs are a combination of me having complicated ideals and not being a great programmer. I am trying not to spend a lot of time debugging old bugs like the order limit bug because of the parametric stuff coming out soon.
I assume you didn’t have a lot of funds in there? You shouldn’t be getting rates that high with any kind of volume (buy side is basically nonexistant right now).
@willy https://raw.nupool.net/nubits/ isn’t showing my BTC pool at all anymore. I think all I did was change IP’s, I’m still using the same custodial address.
Is your code on Github? I’d like to pull it to update my own server.