I did follow mullick instructions, seems fine for me with 8 active peers now. I will update my post if it goes bad.
{
"blocks" : 79651,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.18377558,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 0,
"testnet" : false
}
{
"blocks" : 79651,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.18377558,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 0,
"testnet" : false
}
Yes, you will have to do this every few hours... because you will again be booted from the chain you are on, or they will leave. (They = the one largest pool that becomes the new tallest chain, every time.)
I am making a list of every time I was severed from "the tall chain", when my program was forced to mine with the others who were booted off the chain, which leads us into creating the many small isolated chains. In hopes that this will help to identify the exact issue... but without knowing why "we are all seen as misbehaving"... it will be of no real use.
If misbehaving = resubmitting a block that is not acceptable... due to being beat by another block... then that code has to be changed. CGminer is told to resubmit up to 12 times, which is NOT misbehaving, that is called persistence when the client does not respond with a valid reason for rejection, or does not respond with a rejection at all.
This is where a port-snooper comes in handy. You can actually see what it is sending before the program chews it up and spits out something that can't be translated.
