Just for the record:
I received payouts of 0.0301 NBT - so that is working as well!
Looking at the log I found:
ERROR: unable to retrieve order book for btc on bter: exception caught: [Errno -2] Name or service not known
WARNING: need to resynchronize trading bot for btc on bter because the deviation reached 29.69
INFO: waiting 6.48 seconds to synchronize with other trading bots for btc on bter
Does that point to a problem on my RaPi of is it the bot?
edit:
I checked old logs. This error is happening several times per hour. Hmmā¦
edit2:
The nupool client by @creon produces error as well, but only rarely and due to timeouts (āThe read operation timed outā).
As this nupool client runs on a different RaPi it could still be RaPi related issuesā¦
Donāt worry too much (unless Iām not the only one with these kinds of errors) and for now consider it ājust for the recordā¦ā
āName or service not knownā really sounds like your own internet was down for a while. Your Raspi 1 with several coin daemons could lead to this effect. I had the client running on a raspi 1, but without anything else running there, and I also had some more errors than on a PC (but still only maybe one in 30 min).
Iām pretty sure I understand every change I made to the code, and you shouldnāt really be getting any exotic errors. The worst that should happen is either the bot will be shifting the orders around too often or your rate wonāt register. Iāve been running it all night and didnāt experience either of these problems, so I believe the update is stable.
If you are testing, you should set āprefunitā to anything other than nbt or btc (leave it blank) so that your bot uses the widest spread. This will test the outer limits. I have it on ābtcā by default.
# interest: minimal interest rate at which you want to get payouts in percent (0.25% = 0.25)
# Set to 0 for pool maximum. You can specify two interest rates for the bid and ask side
# by separating them with a comma, e.g. 0.25,0.1
interest = 0
# ordermatch: place orders even if they would match with an existing order
# set this value only to True if you know what you are doing.
ordermatch = False
# preferred unit uses a shorter spread on the unpreferred side. (nbt, btc, or blank)
prefunit = btc
Got it. Will give it a try. Was asking because the āDO NOT CHANGEā in that part of pool.conf made me cautious
Maybe Iāve downloaded the wrong branch - my pool.conf doesnāt have
# preferred unit uses a shorter spread on the unpreferred side. (nbt, btc, or blank)
prefunit = btc
ā¦
edit:
Iāve downloaded the branch āNagalim-prefunit-1vā to the RaPi that is running successfully @creonās nupool client for some time.
Settings for nupond pool.conf are:
# preferred unit uses a shorter spread on the unpreferred side. (nbt, btc, or blank)
prefunit =
Running smoothly, but I still get:
[Errno -2]
This is unique for the nupond client. Neither @cybnates liquidbits client nor creonās nupool client ever produced that error so far.
Iāve grepped through all logs I haveā¦
Iāve found nothing like āerrnoā in the liquidbits logs.
And the only numbered errors I found at the nupool logs are 8 (SSL related), 22 (debug message), 97 (address family not supported).
Only the nupond client creates āerrno -2ā and still in numbersā¦
Is it really related to my client or could it be something on bterās side?
exchanges.py uses data.bter.com for the connection. Replacing that with 141.101.121.207 for a test run didnāt work:
ERROR: unable to delete all orders for btc on bter: exception caught: No JSON object could be decode
Is it because of cloudflare or do I have to adjust more?
Btw, your āunitā in the general operations parameters section should definately be ābtcā, if it isnāt already. The bit you posted has it blank.
I have not seen that. Iāll check it out later tonight when I get home from work.
Do you see the āerrno -2ā when you use innuitwallet on my server? I.e. is it just my experimental version of the nu-pool directory that throws this error, or is my server throwing this error despite what client you use?
I have it with the older version as well. I had not investigated the logs before, because all was running fine - at least fine enough not to dig in logs
Hereās an example of the non experimental version of the nupond bot:
2015/05/01-11:19:31 ERROR: unable to retrieve order book for btc on bter: exception caught: [Errno -2] Name or service not known
2015/05/01-11:53:20 ERROR: unable to retrieve order book for btc on bter: exception caught: [Errno -2] Name or service not known
2015/05/01-14:17:37 ERROR: unable to retrieve order book for btc on bter: exception caught: [Errno -2] Name or service not known
2015/05/01-16:30:52 ERROR: unable to retrieve order book for btc on bter: exception caught: [Errno -2] Name or service not known
2015/05/01-16:43:14 ERROR: unable to retrieve order book for btc on bter: exception caught: [Errno -2] Name or service not known
2015/05/01-17:17:15 ERROR: unable to retrieve order book for btc on bter: exception caught: [Errno -2] Name or service not known
2015/05/03-21:43:03 ERROR: unable to retrieve order book for btc on bter: exception caught: [Errno -2] Name or service not known
2015/05/03-21:49:16 ERROR: unable to retrieve order book for btc on bter: exception caught: [Errno -2] Name or service not known
2015/05/04-05:17:15 ERROR: unable to retrieve order book for btc on bter: exception caught: [Errno -2] Name or service not known
2015/05/04-08:05:11 ERROR: unable to retrieve order book for btc on bter: exception caught: [Errno -2] Name or service not known
ā¦
This is a trading bot error, not a server error. Again, āName or service not knownā is what you get if you unplug your router and open a website. It really means āYou donāt have internet, why are you asking me to open a connection?ā.
I googled a bit and if this only happens this rarely then some people could improve their situation by adding additional DNS servers. But actually in your case it is really not that often. If you want I can disable the error message for you.
Thank you for your offer, but I donāt think itās necessary at all.
In the end the bot is running fine. Those few errors donāt hurt at all.
I was only trying to report findings that my help improving the botā¦
ā¦looks like I need to improve my infrastructure
Itās a bit strange though, that the same Raspberry that meanwhile hosts the (experimental) version of the nupond bot doesnāt have problems running the classic nupool bot.
As the DNS settings are the same for both bots I canāt explain why one bot throws these errors and the other doesnāt.
The log excerpt in one of my recent posts here in this thread is from the classic nupond bot running on bter.
It was running on a RaPi which also hosts some other applications.
Iāve recognized the errors after having started the experimental version of nupond bot.
Later I found out that the non-experimental version had created these errors as well.
I meanwhile moved the experimental version of nupond bot to a RaPi2 which hosts @creonās nupool bot which has never reported such an error - the nupool bot is running ()more or less) continuously since 23rd April.
I still believe that itās not worth looking into this any further as long as Iām the only one with that error (that doesnāt even hurt the operation of the bot)ā¦
Iāve started a test run with @creonās bot using your server (45.55.253.18:3333) and bter (running at the same RaPi2 where @creonās nupool but operates flawless on bittrex).
I expect to see the same error (āerrno -2ā), because Iām almost sure it has to do with bter (and maybe in some way my internet accessā¦).
Weāll see.
Iāll keep you informed, but will be away most part of the weekend with no feasible access to my RaPis.
You might need to wait until anytime on Monday for a report.
[edit]
Got the first āerrno -2ā after less than 20 minutes.
So it has nothing to do with the nupond bot - it might have to do with bter or with my client. As the same machine is running fine with @creonās nupool bot on bittrex, I wouldnāt wonder if other people got āerrno -2ā from time to time when running a bot on bter.
As this doesnāt seem to impact the bot operation, Iām going to ignore it
[/edit]
Thanks for your support and for providing nupond!
And thank you, @creon, for having created the nupool bot to make TLLP possible!
I fine-tuned trading.py to outperform other LPCs on bittrex for nupool:
I also created on thatās more gentle for markets that havenāt reached target yet:
These branches are basically abusing the current config.py settings of TLLP servers, so limited time offer. They do not offer any new mechanics, just a tuning of the spread and perfunit parameters.
Edit: Ok, they are now updated and running properly, I think. Spread = .007, max deviation = .0015, prefunit = .0061 for champion and .002 for grass.
Alright, I manually distributed from before the grant passed. Iāll be restarting the server again this weekend to change the sampling. I will do a manual distribution for that after the restart.
Edit: Increased sampling to 24, restarted server, manually distributed.
The new server is:
NBT/CNY:
45.55.228.61:3333
NBT/BTC:
45.55.228.61:3334
I am not processing payouts, but the rates and targets reflect the beginning draft of nupond operation. This server will be linked from nupond.net after the grant passes.
Iām looking for testers for all pools. This update includes a modified directory structure and 3 new parameters:
offset (used to be spread)
deviation (keep between 0.001 and 0.003, make as large as possible)
restime (resets every 15 minutes to keep bugs away)
All three of these can be left out of the config file if you want (defaults: 0.002,0.0025,24 works on all operating pools). Note that all config files are now tuned to the pool.
I also fixed the executable and notepad issue for unix and windows directories respectively that @cybnateās branch was having issues with.
Iām sorry to @woolly_sammoth and @willy for >70 commits. Me and github are currently in an abusive relationship. Hopefully we will resolve our issues soon, you donāt have to pull from my branch if you donāt want to. I made 0 server side changes, and I think all the client changes I made are ultimately beneficial.