Coyote Miner | PPS Mining Pool

[yago]

Well I atleast can´t conect ...was there anything anounced that the server would go down?

Yes:
http://bitsharestalk.org/index.php?topic=236.msg3590#msg3590

[bahamapascal]

Hi guys.  Are we up yet?

Well I atleast can´t conect ...was there anything anounced that the server would go down?

[NineLives]

Hi guys.  Are we up yet?

[atavacron]

Does anyone know if there is a way to force the client miner to only use nodes listed in protoshares.conf?

Does USE_UPNP=- do that?

The idea being that, in the interim, use only peers known to be on the correct chain.

start it with connect = IPADDRESSEHERE

Thanks.  I'll give that a try.

BTW.  Does anyone have a list of nodes on the correct chain?

[barwizi]

Does anyone know if there is a way to force the client miner to only use nodes listed in protoshares.conf?

Does USE_UPNP=- do that?

The idea being that, in the interim, use only peers known to be on the correct chain.

start it with connect = IPADDRESSEHERE

[atavacron]

Does anyone know if there is a way to force the client miner to only use nodes listed in protoshares.conf?

Does USE_UPNP=- do that?

The idea being that, in the interim, use only peers known to be on the correct chain.

[glongsword]

they all work until one attempts to cross chains into the other. i have two windows boxes running the different ones, yet at some point one reported being connected to the other. i intend to try running them in a closed net just to make sure. they also report being on different block numbers, lets all post here current block numbers and cross check.


mine states 12301 for version 2

12400 on the older one

interesting

Hint: Compare the difficulty reported in addition to the block numbers.  I was seeing lots of weird numbers there before my client crashes.

[arubi]

they all work until one attempts to cross chains into the other. i have two windows boxes running the different ones, yet at some point one reported being connected to the other. i intend to try running them in a closed net just to make sure. they also report being on different block numbers, lets all post here current block numbers and cross check.


mine states 12301 for version 2

12400 on the older one

interesting

[barwizi]

they all work until one attempts to cross chains into the other. i have two windows boxes running the different ones, yet at some point one reported being connected to the other. i intend to try running them in a closed net just to make sure. they also report being on different block numbers, lets all post here current block numbers and cross check.


mine states 12301 for version 2

12400 on the older one

[arubi]

ok, it's been more than thirty minutes since arubi tried what i asked him to do, since then it has been more than twenty minutes without it crashing. I'll wait an additional 30 minutes for a response from hm again, but i am sure this temporary fix has resolved the issue of crashing. however, i need bytemaster to also confirm this, then we can implement the patch quickly.

good job! (+ 1BTC bounty?)

not yet it seems. this run was longer than before so we are on the right track. the issue is rouge peers, if you run it while connecting to functional clients that are on the right fork it seems to work.

just need to patch it to refuse connections from the old chain. if i can get my box working , i'll do it myself.

barwizi, I ran protosharesd with the --connect=192.241.150.158:3888 option
doesn't this means i was connected to only 1 peer all along?

also, protosharesd on my debian still has not crashed and it's talking to everyone, maybe I'm basically one of the "rough" nodes?
also this presents another question, will a "rough" node crash when talking to a legit one? or only the legit one crashes?

[barwizi]

ok, it's been more than thirty minutes since arubi tried what i asked him to do, since then it has been more than twenty minutes without it crashing. I'll wait an additional 30 minutes for a response from hm again, but i am sure this temporary fix has resolved the issue of crashing. however, i need bytemaster to also confirm this, then we can implement the patch quickly.

good job! (+ 1BTC bounty?)

not yet it seems. this run was longer than before so we are on the right track. the issue is rouge peers, if you run it while connecting to functional clients that are on the right fork it seems to work.

just need to patch it to refuse connections from the old chain. if i can get my box working , i'll do it myself.

[fav]

ok, it's been more than thirty minutes since arubi tried what i asked him to do, since then it has been more than twenty minutes without it crashing. I'll wait an additional 30 minutes for a response from hm again, but i am sure this temporary fix has resolved the issue of crashing. however, i need bytemaster to also confirm this, then we can implement the patch quickly.

good job! (+ 1BTC bounty?)

[barwizi]

ok, it's been more than thirty minutes since arubi tried what i asked him to do, since then it has been more than twenty minutes without it crashing. I'll wait an additional 30 minutes for a response from hm again, but i am sure this temporary fix has resolved the issue of crashing. however, i need bytemaster to also confirm this, then we can implement the patch quickly.

[mmx888]

come back sir!

+100

+10000...0000000000000

[NineLives]

come back sir!

+100