BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

Started by Rob Andrews, October 03, 2017, 01:07:26 PM

Previous topic - Next topic

putzlappen

Quote from: jaapgvk on December 19, 2017, 06:47:42 AM
That's very interesting! Just a question: what's your 'genproclimit' on the happybeehost?

genproclimit = 4 on happybeehost.
Greetings from Germany <3

jaapgvk

Quote from: putzlappen on December 19, 2017, 06:51:13 AM
genproclimit = 4 on happybeehost.

Thanks :) Interesting.

I did a little bit of mining on the hyperexpert VPS, but I can't remember how much hps I got. I think it was around 400-500 HPS with a single-core and 1GB RAM.

tiras

Quote from: jaapgvk on December 19, 2017, 03:11:01 AM
I have no idea... Did you use the same vps for testing the testnet sanctuaries?

yes, I used the same VPS

jaapgvk

Quote from: tiras on December 19, 2017, 08:32:31 AM
yes, I used the same VPS

Okay, then I don't know what could be it. But I got another 'win' so maybe it will flatten out in the long run. Looking at the other winners, the list seems to diversify a bit. Did you win any, except the '1 part'?

tiras

Quote from: jaapgvk on December 19, 2017, 09:10:06 AM
Okay, then I don't know what could be it. But I got another 'win' so maybe it will flatten out in the long run. Looking at the other winners, the list seems to diversify a bit. Did you win any, except the '1 part'?

yes, I've got 2 more wins shortly after the 1st one.   
looking at other MN stats it's by far not a fair distribution for now. 
Rob was mentioning that some minor updates  will follow.
Hopefully they will improve round -robin algorithm here .

togoshigekata

https://en.wikipedia.org/wiki/Law_of_large_numbers

Have to be careful extrapolating from a small data set, there is going to be randomness / fluctuations with smaller amount of data

I think Rob mentioned the algorithm has something to do with a hash number being near a masternode's number, Id have to look into it, sounds interesting

putzlappen

Good Morning Community (its 08:30 am here )

I got a Problem with this happybeecloud-vps: randomly biblepay (v1.0.6.9) stopping. I dont know the reason. When i start it with

cd /home/root/biblepay/src
./biblepayd -daemon


and some seconds later i check status with:

./biblepay-cli getmininginfo

i only get an error: couldn't connect to server back.

But sometimes, everything works fine, and biblepay runs stable until it stopps random.
I was looking for a log to solve this but cant find something in /var/log or in biblepay directory.


An other thing: i want to testing such an 8-core vps from hyperexpert, but they dont sell any vps. Maybe they are in hollyday.
Greetings from Germany <3

jaapgvk

Quote from: togoshigekata on December 19, 2017, 10:11:36 AM
https://en.wikipedia.org/wiki/Law_of_large_numbers

Have to be careful extrapolating from a small data set, there is going to be randomness / fluctuations with smaller amount of data

I think Rob mentioned the algorithm has something to do with a hash number being near a masternode's number, Id have to look into it, sounds interesting

Yeah, you're absolutely right :) It's just that I didn't get any 'win' in the first 140 blocks (counting from block 21600), although my masternode was online or upgrading all that time, so I was getting worried that something might be wrong with my VPS.

jaapgvk

Quote from: putzlappen on December 20, 2017, 01:36:08 AM
Good Morning Community (its 08:30 am here )

I got a Problem with this happybeecloud-vps: randomly biblepay (v1.0.6.9) stopping. I dont know the reason. When i start it with

cd /home/root/biblepay/src
./biblepayd -daemon


and some seconds later i check status with:

./biblepay-cli getmininginfo

i only get an error: couldn't connect to server back.

But sometimes, everything works fine, and biblepay runs stable until it stopps random.
I was looking for a log to solve this but cant find something in /var/log or in biblepay directory.

An other thing: i want to testing such an 8-core vps from hyperexpert, but they dont sell any vps. Maybe they are in hollyday.

Good morning (also for me, living in the Netherlands) :)

When you get the 'couldn't connect to server' error, that indeed most probably means that biblepay crashed. I've had that in the past with a few installations. You could try a reindex, but I don't know if that would help to be honest. Maybe someone else can answer this question more accurately for you.

About hyperexpert: It checked, and it's probably something temporary and/of holidays, but I can't find an announcement no their blog.

About the hps vs hps2: the hps2 is what the pool is using as your 'actual hps', and uses that to calculate your payout (it's correlated to the amount of shares). And the hps is what your wallet reports, but I don't think it's really accurate as of yet. I don't have enough knowledge te explain the details, but you could try and find information about this on bitcointalk (although it might be kind of hard to find between the mountains of posts).

tiras

Quote from: putzlappen on December 20, 2017, 01:36:08 AM
Good Morning Community (its 08:30 am here )

I got a Problem with this happybeecloud-vps: randomly biblepay (v1.0.6.9) stopping. I dont know the reason. When i start it with

cd /home/root/biblepay/src
./biblepayd -daemon


and some seconds later i check status with:

./biblepay-cli getmininginfo

i only get an error: couldn't connect to server back.

But sometimes, everything works fine, and biblepay runs stable until it stopps random.
I was looking for a log to solve this but cant find something in /var/log or in biblepay directory.


An other thing: i want to testing such an 8-core vps from hyperexpert, but they dont sell any vps. Maybe they are in hollyday.

>> got a Problem with this happybeecloud-vps: randomly biblepay (v1.0.6.9) stopping. I dont know the reason. When i start it with

is that 1GB or 2GB RAM VPS you've got random daemon failures at ?

putzlappen

Quote from: tiras on December 20, 2017, 04:24:13 AM
>> got a Problem with this happybeecloud-vps: randomly biblepay (v1.0.6.9) stopping. I dont know the reason. When i start it with

is that 1GB or 2GB RAM VPS you've got random daemon failures at ?

Its the 2 GB RAM Quadcore VPS.
Greetings from Germany <3

tiras

Quote from: putzlappen on December 20, 2017, 04:31:10 AM
Its the 2 GB RAM Quadcore VPS.

I had the same thing on a 1GB VPS and I just dropped it . 
You could create some kind of a cron job calling a shell script checking if daemon is running and restarting it .
I guess provider does not favor mining on it's premises.  that's it . 
they can control the processes on VPSes .

alvin

Quote from: tiras on December 20, 2017, 04:50:29 AM
I had the same thing on a 1GB VPS and I just dropped it . 
You could create some kind of a cron job calling a shell script checking if daemon is running and restarting it .
I guess provider does not favor mining on it's premises.  that's it . 
they can control the processes on VPSes .

Same with you , I cancelled it as I tried many times to test,  look like the provider had a detector tool for monitor their vps ....

putzlappen

Quote from: alvin on December 20, 2017, 05:27:16 AM
Same with you , I cancelled it as I tried many times to test,  look like the provider had a detector tool for monitor their vps ....

Which Provider did you mean?
Greetings from Germany <3