Indeed, even if you forge 24/7 with zero rewards.
Topic: Qora | POS | Assets | Names | Polls | Automated Transactions | Social Network - page 125. (Read 249452 times)
August 25, 2016, 10:22:50 PM
Indeed, even if you forge 24/7 with zero rewards.
August 25, 2016, 10:02:55 PM
good for you hope that can also help Qora's wallet from polo. good luck mate
August 25, 2016, 10:00:58 PM
August 25, 2016, 09:33:19 PM
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.
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.
August 25, 2016, 09:10:04 PM
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.
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.)
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.
August 25, 2016, 08:39:22 PM
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!https://cloud.crowetic.com/s/3rUsS3CAEwc6Ze8
Also, some simple guidelines until we get the actual fix pushed...
Is forging here now.
August 25, 2016, 06:29:30 PM
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.
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.)
You can test your ports here :
http://www.canyouseeme.org/
http://www.portchecktool.com/
You should get a green light as I do.
August 25, 2016, 05:30:22 PM
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.
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.)
August 25, 2016, 05:15:08 PM
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?
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)
August 25, 2016, 05:07:33 PM
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.
That's also what I have, no incoming but port is open.
August 25, 2016, 02:57:37 PM
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)
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?
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
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.
August 25, 2016, 02:26:28 PM
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)
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?
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
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)
August 25, 2016, 01:57:31 PM
This is the final piece remaining until I can give polo a link to a 'working blockexplorer' since they can't seem to figure out the local blockex on their end.
They/we need an external Block Explorer, because the built-in one is self-referential (it shows what the node itself is doing). It's helpful for quick reference, but if a forging node (like Poloniex) starts spinning away on it's own fork, their own block explorer can't show that. They need the external one to check if their blocks are getting out to the network.
I've successfully gotten two hosted wallets up, the first one may be slower than the second, I'm waiting on the DNS to propagate to the qora.tech domain.
I think I will also put it on qora.online
http://burstkore.ddns.net:9090/index/blockexplorer.html
http://qora.tech:9090/index/blockexplorer.html
I think I will also put it on qora.online
http://burstkore.ddns.net:9090/index/blockexplorer.html
http://qora.tech:9090/index/blockexplorer.html
I checked out the one at burstkore, looks good, nice work!
The other can be seen at http://216.126.198.26:9090/index/blockexplorer.html until the DNS propagates on qora.tech.
Thanks!
August 25, 2016, 01:56:03 PM
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)
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?
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
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 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
August 25, 2016, 01:49:37 PM
This is the final piece remaining until I can give polo a link to a 'working blockexplorer' since they can't seem to figure out the local blockex on their end.
They/we need an external Block Explorer, because the built-in one is self-referential (it shows what the node itself is doing). It's helpful for quick reference, but if a forging node (like Poloniex) starts spinning away on it's own fork, their own block explorer can't show that. They need the external one to check if their blocks are getting out to the network.
I've successfully gotten two hosted wallets up, the first one may be slower than the second, I'm waiting on the DNS to propagate to the qora.tech domain.
I think I will also put it on qora.online
http://burstkore.ddns.net:9090/index/blockexplorer.html
http://qora.tech:9090/index/blockexplorer.html
I think I will also put it on qora.online
http://burstkore.ddns.net:9090/index/blockexplorer.html
http://qora.tech:9090/index/blockexplorer.html
I checked out the one at burstkore, looks good, nice work!
August 25, 2016, 01:25:14 PM
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)
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?
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
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
August 25, 2016, 01:11:54 PM
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)
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?
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
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?
August 25, 2016, 12:59:00 PM
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...
1. ALWAYS close the wallet with file-quit to avoid db issues
2. The default settings.json file seems corrupted. IF you file-quit the wallet, wait for the db to save (don't kill it.) then DELETE the settings.json file, and restart the wallet, your settings will then save and be good.
oh yea, and now for a little showing off of what QORA hosting can do...
http://216.126.198.26:9090/2ndtest/nature
This image is hosted FULLY ON THE BLOCKCHAIN. Took about 300 tx to be there, but is now fully hosted decentralized via QORA.
I will be doing some more tests and putting up some more cool stuff on QORA hosting shortly!
https://cloud.crowetic.com/s/3rUsS3CAEwc6Ze8
Also, some simple guidelines until we get the actual fix pushed...
1. ALWAYS close the wallet with file-quit to avoid db issues
2. The default settings.json file seems corrupted. IF you file-quit the wallet, wait for the db to save (don't kill it.) then DELETE the settings.json file, and restart the wallet, your settings will then save and be good.
oh yea, and now for a little showing off of what QORA hosting can do...
http://216.126.198.26:9090/2ndtest/nature
This image is hosted FULLY ON THE BLOCKCHAIN. Took about 300 tx to be there, but is now fully hosted decentralized via QORA.
I will be doing some more tests and putting up some more cool stuff on QORA hosting shortly!
August 25, 2016, 12:56:49 PM
So, um, is Qora.co.in gone for good or just down?
I would assume that site is down for good, but I've successfully gotten two hosted wallets up, the first one may be slower than the second, I'm waiting on the DNS to propagate to the qora.tech domain.
I think I will also put it on qora.online
http://burstkore.ddns.net:9090/index/blockexplorer.html
http://qora.tech:9090/index/blockexplorer.html
August 25, 2016, 12:17:43 PM
Settings parameter "weballowed" is the list of IPs that can connect, and empty list apparently means all. You can set that by editing settings.json, or via the File-Settings dialog. However, there appears to be a bug:
BUG: File-Settings dialog is overwriting/truncating the settings.json file when you click Apply. It's only writing some of the settings, (maybe just the changed ones, or just the ones on that tab?), and ignoring the rest. And it overwrites the file in place, so you see the cruft from the prior settings still there, but they're past the closing bracket so won't be read. Observed on Wallet 0.26, Linux
EDIT: Also, it seems wrong that empty list on a parameter called "weballowed" means everyone allowed. Empty should mean none allowed. Should be something like "*" or "*.*.*.*", or a broadcast/mask address to mean everyone allowed.
Keep a backup of your settings.json
Here is a standard one:
BUG: File-Settings dialog is overwriting/truncating the settings.json file when you click Apply. It's only writing some of the settings, (maybe just the changed ones, or just the ones on that tab?), and ignoring the rest. And it overwrites the file in place, so you see the cruft from the prior settings still there, but they're past the closing bracket so won't be read. Observed on Wallet 0.26, Linux
EDIT: Also, it seems wrong that empty list on a parameter called "weballowed" means everyone allowed. Empty should mean none allowed. Should be something like "*" or "*.*.*.*", or a broadcast/mask address to mean everyone allowed.
Keep a backup of your settings.json
Here is a standard one:
Code:
{
"knownpeers":[
],
"rpcallowed":[
"127.0.0.1"
],
"weballowed":[
"127.0.0.1"
],
"guienabled":true,
"rpcenabled":true,
"webenabled":true,
"systray":true,
"maxconnections":100,
"minconnections":10,
"generatorkeycaching":true,
"checkpoint":true,
"soundreceivepayment":true,
"soundnewtransaction":true,
"soundreceivemessage":true
}
"knownpeers":[
],
"rpcallowed":[
"127.0.0.1"
],
"weballowed":[
"127.0.0.1"
],
"guienabled":true,
"rpcenabled":true,
"webenabled":true,
"systray":true,
"maxconnections":100,
"minconnections":10,
"generatorkeycaching":true,
"checkpoint":true,
"soundreceivepayment":true,
"soundnewtransaction":true,
"soundreceivemessage":true
}
Jump to: