Qora | POS | Assets | Names | Polls | Automated Transactions | Social Network

[YukonCoinelius]

Running the wallet in forging mode several days.  
There are only ever 4 lasting connections (other ones show up transiently for a few seconds and go away).  
For example  (from  File-Debug-Peers)

Code:

106.187.42.214   271687
188.166.16.64    271690
128.199.45.81    271706
5.230.145.31     271705

The number after the IP above is "height".    The heights are all widely different!!  And they generally stay different, all counting up or jumping ahead to catch each other, but never in unison.  I've *never* seen them all the same height!

Why, what's going on?   Is this right, or just a debug display issue?  It seems worrisome, and maybe indicates why there are syncing/forking problems.   If all of these nodes were actively forging, seems they'd all be chaining up different blocks.

Also, why only 4 peers?  I thought there were more other nodes active by now?   Anyone have active node IPs not shown in that list?

I get up to 10 peers fade in and out. They try

to connect but dont.



Here are a few other IPs that try to connect:

60.29.233.154
60.172.227.64

Interesting,  our Peer lists match, but we're not seeing each other, and probably noone else is either.  Yes, I get lots of others showing up and immediately dropping off too, just like that.

Why is it not connecting to more?

Do we need to open a router port, or other configuration steps... ?
Maybe there are speed/latency assumptions in the code?
I'm on DSL, and then wifi,  in case that's relevant.

It seems many nodes that might have been trying to forge/sustain the network for a long time, were maybe not really connected, just like this.   (that would explain a good bit)

[1714259203]

1714259203

[1714259203]

1714259203

[1714259203]

1714259203

[1714259203]

1714259203

[1714259203]

1714259203

[MikeMike]

Running the wallet in forging mode several days.  
There are only ever 4 lasting connections (other ones show up transiently for a few seconds and go away).  
For example  (from  File-Debug-Peers)

Code:

106.187.42.214   271687
188.166.16.64    271690
128.199.45.81    271706
5.230.145.31     271705

The number after the IP above is "height".    The heights are all widely different!!  And they generally stay different, all counting up or jumping ahead to catch each other, but never in unison.  I've *never* seen them all the same height!

Why, what's going on?   Is this right, or just a debug display issue?  It seems worrisome, and maybe indicates why there are syncing/forking problems.   If all of these nodes were actively forging, seems they'd all be chaining up different blocks.

Also, why only 4 peers?  I thought there were more other nodes active by now?   Anyone have active node IPs not shown in that list?

I get up to 10 peers fade in and out. They try

to connect but dont.



Here are a few other IPs that try to connect:

60.29.233.154
60.172.227.64

Interesting,  our Peer lists match, but we're not seeing each other, and probably noone else is either.  Yes, I get lots of others showing up and immediately dropping off too, just like that.

Why is it not connecting to more?

Do we need to open a router port, or other configuration steps... ?
Maybe there are speed/latency assumptions in the code?
I'm on DSL, and then wifi,  in case that's relevant.

It seems many nodes that might have been trying to forge/sustain the network for a long time, were maybe not really connected, just like this.   (that would explain a good bit)

Thanks,
I have no idea and hope this info is helping.
I am on Cable then to a wifi router and VPN.

[Enema]

All your peers on the list show "initiator=you" so no incoming connections.
That's also what I have, no incoming but port is open.

[YukonCoinelius]

The heights are all widely different!!  And they generally stay different, all counting up or jumping ahead to catch each other, but never in unison.  I've *never* seen them all the same height!
Why, what's going on?   Is this right, or just a debug display issue?  It seems worrisome, and maybe indicates why there are syncing/forking problems.   If all of these nodes were actively forging, seems they'd all be chaining up different blocks.
Also, why only 4 peers?  I thought there were more other nodes active by now?   Anyone have active node IPs not shown in that list?

I would say your db is corrupt, maybe you were on a fork at one time. please delete it and download the one I linked above, and try that.
also, there's a new node @ 216.126.198.26

I think it's a network issue not db, maybe directly relating the fork/sync problems we've been seeing.  However I swapped in that db snapshot just for good measure.  Same exact 4 nodes.

Is there anyone with more or different nodes showing? 
Anyone have the Heights all matching, instead of varying like here?
(look in the gui under Menu-File-Debug-Peers)

[YukonCoinelius]

All your peers on the list show "initiator=you" so no incoming connections.
That's also what I have, no incoming but port is open.

Yes, mine the same, all "initiator=you".

So maybe those are the only 4 nodes accepting incoming, and everyone else has it blocked.

So how do we configure to allow incoming?   Settings flag... Open router ports? 

which port(s) did you open on router/firewall?
(it apparently wasn't the correct/enough ones yet though, since you didn't get incoming conxns either, but it's somewhere to start.  I don't recall there being a specified need to open ports for this coin.)

[Enema]

All your peers on the list show "initiator=you" so no incoming connections.
That's also what I have, no incoming but port is open.

Yes, mine the same, all "initiator=you".

So maybe those are the only 4 nodes accepting incoming, and everyone else has it blocked.

So how do we configure to allow incoming?   Settings flag... Open router ports? 

which port(s) did you open on router/firewall?
(it apparently wasn't the correct/enough ones yet though, since you didn't get incoming conxns either, but it's somewhere to start.  I don't recall there being a specified need to open ports for this coin.)

9084 for your wallet and 9090 for web server.

You can test your ports here :
http://www.canyouseeme.org/
http://www.portchecktool.com/

You should get a green light as I do.

[laKING]

Here's a good copy of the chain in case anyone is having issues...

https://cloud.crowetic.com/s/3rUsS3CAEwc6Ze8

Also, some simple guidelines until we get the actual fix pushed...

Thanks!
Is forging here now.

[YukonCoinelius]

All your peers on the list show "initiator=you" so no incoming connections.
That's also what I have, no incoming but port is open.

Yes, mine the same, all "initiator=you".

So maybe those are the only 4 nodes accepting incoming, and everyone else has it blocked.

So how do we configure to allow incoming?   Settings flag... Open router ports? 

which port(s) did you open on router/firewall?
(it apparently wasn't the correct/enough ones yet though, since you didn't get incoming conxns either, but it's somewhere to start.  I don't recall there being a specified need to open ports for this coin.)

9084 for your wallet and 9090 for web server.

You can test your ports here :
http://www.canyouseeme.org/
http://www.portchecktool.com/

You should get a green light as I do.

Good testing links and port info.  I tunneled 9084 TCP to the server, but no change so far.  Seeing the same 4 Qora nodes.

Also I've seen mention of two other applicable ports:
123 UDP  for the NTP time server  (I tunneled that one too)
9085 TCP for RPC commands   (do *not* put that on public, presumably)

In settings.json I have:
        "maxconnections":100,
        "minconnections":10,


If anybody is getting more than those 4 node connections, or is seeing equal Heights, in the Debug-Peers,  please let us know.

[crowetic]

I didn't know if my other link for the chain download was working... some people were saying they couldn't see the file in the folder... So here's a direct link to the new chain.

https://cloud.crowetic.com/s/IDzrYBiqXnhNCvg


I'll likely be reworking the OP here as well. I'll put together some tutorials on how to run the wallet, download the sync'd chain, and close the wallet the right way to avoid db issues till we get that resolved on the coding level.


I've messaged poloniex with both of my hosted wallets, hopefully that will be enough for them to unblock deposit and withdrawals.

[okinawa]

https://s13.postimg.org/bndjyshnr/Capture.png

Been Forging all Day Everyday  

I am going to be rich 

[Caladonian]

https://s13.postimg.org/bndjyshnr/Capture.png

Been Forging all Day Everyday  

I am going to be rich 

good for you hope that can also help Qora's wallet from polo. good luck mate

[1btcdream]

https://s13.postimg.org/bndjyshnr/Capture.png

Been Forging all Day Everyday  

I am going to be rich 

Indeed, even if you forge 24/7 with zero rewards.   

[boomboom]

Lots of great stuff happening for Qora now ... well done!!

[MikeMike]

My wallet is in sync.
I did it the hard way....
 
When it stuck or did not operate nor close properly I right clicked the icon in my task bar
and closed it, waited awhile and reopened. Even when the wallet started syncng again no matter what point it was
some times it said it was on block 1 again. In time that changed to the current block.
I am running windows 10.

[YukonCoinelius]

My wallet is in sync.
I did it the hard way....
 
When it stuck or did not operate nor close properly I right clicked the icon in my task bar
and closed it, waited awhile and reopened. Even when the wallet started syncng again no matter what point it was
some times it said it was on block 1 again. In time that changed to the current block.
I am running windows 10.

Good work, MikeMike!

By the way, developers, note in the above screenshot another bug, I had seen it too.

BUG: In the Settings-KnownPeers list, sometimes the list gets repeated into 2 successive series.  For example, note in the screenshot above, there are really only 8 unique IPs.  They are listed, then listed again. 


(please crowetic and/or devs, pick up these bug reports from here into your tracking system)

[Ayle56]

The old qora.co.in website used to have a list of known stable peers that had been online for at least a week. You could add them to your wallet to help it sync. Putting a new list of peers on the new website would help the community.

[MikeMike]

Thanks for the coins Crow!
 

They are staking.

MM

[crowetic]

The old qora.co.in website used to have a list of known stable peers that had been online for at least a week. You could add them to your wallet to help it sync. Putting a new list of peers on the new website would help the community.

http://qora.tech:9090 is up for a portal to QORA internet.


I'll likely add extra sites to this that will have all necessary information. Hopefully this new blockex being up will help polo.

[boomboom]

Does Qora have a web wallet like blockchain.info or mynxt.info? Is one being planned?

[Ayle56]

The old qora.co.in website used to have a list of known stable peers that had been online for at least a week. You could add them to your wallet to help it sync. Putting a new list of peers on the new website would help the community.

http://qora.tech:9090 is up for a portal to QORA internet.


I'll likely add extra sites to this that will have all necessary information. Hopefully this new blockex being up will help polo.

Thanks for putting that site online. The new block explorer built into the wallet looks fantastic. The link to it should soon convince Poloniex to open withdrawals again.

http://qora.tech:9090/index/blockexplorer.html