|
profitofthegods
|
 |
September 07, 2014, 05:43:48 PM |
|
This is getting ridiculous. I've spent countless hours trying to get a working Crypti node, and however many days it is waiting for the next release, then the next release, and so on. And in all this time the longest I've had it working for is a few hours.
I'm sorry to hear you have such experience with Crypti node. We have extensively tested the latest 0.1.6b release, however there might be still some issues pending. Please send me and Boris (crypti) the logs via PM, so we could review them. I'm sorry, but I don't know how to send you the logs. I'm using Amazon AWS and I don't know how to download a file from there. The funny thing is -- if I am on my own fork then how am I forging? Doesn't that mean that someone else is sending transactions on the same fork as me? In which case why do I seem to be the only node on that fork and why would anyone's wallet be on it?
A forging node in it's own fork will simply forge all the created blocks, which may or may not have transactions. Whose transactions? For there to be transactions someone else needs to be on the same fork, but I don't see how someone else has a wallet on this fork without there also being another node. |
|
|
|
|
schmelix
Newbie
 Offline
Activity: 49
Merit: 0
|
|
September 07, 2014, 05:52:23 PM |
|
I've noticed a similar behaviour. I've tried a couple of full resyncs with no success
Please send us the logs as well. K. I will send you the logs when a resync has failed again. I clean the logs and blockchain after a failure forever stop app.js; rm -f logs.log blockchain.db; forever start app.js |
|
|
|
|
schmelix
Newbie
Offline
Activity: 49
Merit: 0
|
|
September 07, 2014, 06:04:35 PM |
|
I think my node is on its own fork.
On the 'blockchain' page of the wallet all of the blocks shown are generated by me, and the balance is different from what I see if I log in to wallet.crypti.me.
How did I end up on a fork and what should I do?
Are you on 0.1.6b? Yes. Hmm, the devs will have to check that out. It seems that the forking problems from the 0.1.4 version have risen again. This is getting ridiculous. I've spent countless hours trying to get a working Crypti node, and however many days it is waiting for the next release, then the next release, and so on. And in all this time the longest I've had it working for is a few hours. I have 5 nodes up and running 3 at AWS and 2 at Digital Ocean (1) 512mb DO (2) 1gb AWS (1) 1gb DO (1) 2gb AWS The only one giving me a little trouble is the DO 512mb.. as soon as I see if I can get a stable node on a DO 512mb I will be releasing the DO guide... At the moment (3) 1gb nodes stable and syncing... (1) at DO and (2) at AWS the 2gb node at AWS is also stable...I have it just to compare performance In my opinion it has nothing or not directly to do with the hardware specs. I use three dedicated servers ( 2, 4 and 8GB ) RAM and all of them are out of sync and resyncing is failing all the time |
|
|
|
|
|
informer
|
|
September 07, 2014, 06:10:18 PM |
|
I think my node is on its own fork.
On the 'blockchain' page of the wallet all of the blocks shown are generated by me, and the balance is different from what I see if I log in to wallet.crypti.me.
How did I end up on a fork and what should I do?
I've noticed a similar behaviour. I've tried a couple of full resyncs with no success I'm dealing with the same issue on both AWS and DO nodes. AWS seems to get to about 25gb's each time and then stops. 0.1.6 didn't have this problem and I synced in 1hr 45mins. After 0.16b they both stop. AWS at around 25GB's and DO at around 18GB's. Logs.log is up to the second. Testing now again, with another new clean instance. informer |
|
|
|
|
canej
|
|
September 07, 2014, 06:13:24 PM |
|
So how do I get my local wallet to sync with web wallet with coins I have foraged? these do not sync up at all?
|
|
|
|
|
|
samsmith16
|
|
September 07, 2014, 06:22:00 PM |
|
I think my node is on its own fork.
On the 'blockchain' page of the wallet all of the blocks shown are generated by me, and the balance is different from what I see if I log in to wallet.crypti.me.
How did I end up on a fork and what should I do?
Are you on 0.1.6b? Yes. Hmm, the devs will have to check that out. It seems that the forking problems from the 0.1.4 version have risen again. This is getting ridiculous. I've spent countless hours trying to get a working Crypti node, and however many days it is waiting for the next release, then the next release, and so on. And in all this time the longest I've had it working for is a few hours. I have 5 nodes up and running 3 at AWS and 2 at Digital Ocean (1) 512mb DO (2) 1gb AWS (1) 1gb DO (1) 2gb AWS The only one giving me a little trouble is the DO 512mb.. as soon as I see if I can get a stable node on a DO 512mb I will be releasing the DO guide... At the moment (3) 1gb nodes stable and syncing... (1) at DO and (2) at AWS the 2gb node at AWS is also stable...I have it just to compare performance In my opinion it has nothing or not directly to do with the hardware specs. I use three dedicated servers ( 2, 4 and 8GB ) RAM and all of them are out of sync and resyncing is failing all the time The reason I ask is to look for trends from ppl dropping sync... not only in hardware but in could services... |
▐ Royalties▐ pays interest on Term Deposits up to 15%!! Yes even Cold Storage!! |
|
|
|
samsmith16
|
|
September 07, 2014, 06:26:01 PM |
|
So how do I get my local wallet to sync with web wallet with coins I have foraged? these do not sync up at all?
If your not seeing the same info on the web wallet then your local wallet is out of sync... |
▐ Royalties▐ pays interest on Term Deposits up to 15%!! Yes even Cold Storage!! |
|
|
|
profitofthegods
|
|
September 07, 2014, 06:28:33 PM |
|
The reason I ask is to look for trends from ppl dropping sync... not only in hardware but in could services...
Perhaps it could be in the way it is set up also. Do you do anything in your set up which somebody else might not do? For example, since you run multiple nodes do you add each of your nodes to the others' config files or anything like that? |
|
|
|
|
|
canej
|
|
September 07, 2014, 06:31:32 PM |
|
So how do I get my local wallet to sync with web wallet with coins I have foraged? these do not sync up at all?
If your not seeing the same info on the web wallet then your local wallet is out of sync... Ok this is the second machine that I have lost my foraging coins. How come they not syncing? Not sure what to do now? This happened on 0.1.5b and now on a new machine on 0.1.6b. Will DM the devs Thanks |
|
|
|
|
|
crypti (OP)
|
|
September 07, 2014, 06:36:02 PM |
|
So how do I get my local wallet to sync with web wallet with coins I have foraged? these do not sync up at all?
If your not seeing the same info on the web wallet then your local wallet is out of sync... Ok this is the second machine that I have lost my foraging coins. How come they not syncing? Not sure what to do now? This happened on 0.1.5b and now on a new machine on 0.1.6b. Will DM the devs Thanks Maybe you was in fork, and forge this coins in fork. After node detected that you in fork, it deleted fork blocks and sync again. Same can be in bitcoin, nxt and etc. |
|
|
|
|
|
samsmith16
|
|
September 07, 2014, 06:37:57 PM |
|
I think my node is on its own fork.
On the 'blockchain' page of the wallet all of the blocks shown are generated by me, and the balance is different from what I see if I log in to wallet.crypti.me.
How did I end up on a fork and what should I do?
I've noticed a similar behaviour. I've tried a couple of full resyncs with no success I'm dealing with the same issue on both AWS and DO nodes. AWS seems to get to about 25gb's each time and then stops. 0.1.6 didn't have this problem and I synced in 1hr 45mins. After 0.16b they both stop. AWS at around 25GB's and DO at around 18GB's. Logs.log is up to the second. Testing now again, with another new clean instance. informer When your talking about GB's what is this number referring to? Did you mean MB? atm the blockchain.db is only 82mb and both my 1gb AWS node are only using 6% of the 1gb ram... |
▐ Royalties▐ pays interest on Term Deposits up to 15%!! Yes even Cold Storage!! |
|
|
|
samsmith16
|
|
September 07, 2014, 06:42:17 PM |
|
The reason I ask is to look for trends from ppl dropping sync... not only in hardware but in could services...
Perhaps it could be in the way it is set up also. Do you do anything in your set up which somebody else might not do? For example, since you run multiple nodes do you add each of your nodes to the others' config files or anything like that? I make sure to follow the guides to the "T" I want to know someone without cloud/linux experience can follow the guide and come out with a fully functioning cloud node |
▐ Royalties▐ pays interest on Term Deposits up to 15%!! Yes even Cold Storage!! |
|
|
|
informer
|
|
September 07, 2014, 07:15:22 PM |
|
I think my node is on its own fork.
On the 'blockchain' page of the wallet all of the blocks shown are generated by me, and the balance is different from what I see if I log in to wallet.crypti.me.
How did I end up on a fork and what should I do?
I've noticed a similar behaviour. I've tried a couple of full resyncs with no success I'm dealing with the same issue on both AWS and DO nodes. AWS seems to get to about 25gb's each time and then stops. 0.1.6 didn't have this problem and I synced in 1hr 45mins. After 0.16b they both stop. AWS at around 25GB's and DO at around 18GB's. Logs.log is up to the second. Testing now again, with another new clean instance. informer When your talking about GB's what is this number referring to? Did you mean MB? atm the blockchain.db is only 82mb and both my 1gb AWS node are only using 6% of the 1gb ram... My eyeball conversion was a little off. It's in MB's not GB's. Thanks for catching that. I've started with a clean instance and its at 6.15 MB right now and climbing. Let's see how it goes. Also, I have not opened the web wallet on it yet this time and won't until the blockchain stops growing for 1 hour. Just to see if it makes a difference. informer |
|
|
|
|
canej
|
|
September 07, 2014, 07:15:34 PM |
|
So looks like I am back to sync problems again :-( deleted DB as seems I was on a fork. And now my syncing stops... Till I stop and restart the service....
|
|
|
|
|
|
crypti (OP)
|
|
September 07, 2014, 07:22:59 PM |
|
So looks like I am back to sync problems again :-( deleted DB as seems I was on a fork. And now my syncing stops... Till I stop and restart the service....
How it's stops? Loading or sync? Can be delay middle UI and api, because sometimes in UI you will not see sync message. And sync can take time. |
|
|
|
|
|
canej
|
|
September 07, 2014, 07:27:27 PM |
|
So looks like I am back to sync problems again :-( deleted DB as seems I was on a fork. And now my syncing stops... Till I stop and restart the service....
How it's stops? Loading or sync? Can be delay middle UI and api, because sometimes in UI you will not see sync message. And sync can take time. I check logs, they stop updating as well as the UI the block chain is not current. This has been waiting for over an hour to sync.... So stop and restarted and sync continued right away... |
|
|
|
|
|
crypti (OP)
|
|
September 07, 2014, 07:29:51 PM |
|
So looks like I am back to sync problems again :-( deleted DB as seems I was on a fork. And now my syncing stops... Till I stop and restart the service....
How it's stops? Loading or sync? Can be delay middle UI and api, because sometimes in UI you will not see sync message. And sync can take time. I check logs, they stop updating as well as the UI the block chain is not current. This has been waiting for over an hour to sync.... So stop and restarted and sync continued right away... What in logs? Why it's stopped? |
|
|
|
|
|
canej
|
|
September 07, 2014, 07:31:52 PM |
|
So looks like I am back to sync problems again :-( deleted DB as seems I was on a fork. And now my syncing stops... Till I stop and restart the service....
How it's stops? Loading or sync? Can be delay middle UI and api, because sometimes in UI you will not see sync message. And sync can take time. I check logs, they stop updating as well as the UI the block chain is not current. This has been waiting for over an hour to sync.... So stop and restarted and sync continued right away... What in logs? Why it's stopped? I have just restarted so will post here again when it happens.on 1100 block on initial sync it stopped at 215 last time. |
|
|
|
|
|
crypti (OP)
|
|
September 07, 2014, 07:33:02 PM |
|
So looks like I am back to sync problems again :-( deleted DB as seems I was on a fork. And now my syncing stops... Till I stop and restart the service....
How it's stops? Loading or sync? Can be delay middle UI and api, because sometimes in UI you will not see sync message. And sync can take time. I check logs, they stop updating as well as the UI the block chain is not current. This has been waiting for over an hour to sync.... So stop and restarted and sync continued right away... What in logs? Why it's stopped? I have just restarted so will post here again when it happens.on 1100 block on initial sync it stopped at 215 last time. Hm, can you send me your blockchain.db? |
|
|
|
|
|
canej
|
|
September 07, 2014, 07:34:09 PM |
|
So looks like I am back to sync problems again :-( deleted DB as seems I was on a fork. And now my syncing stops... Till I stop and restart the service....
How it's stops? Loading or sync? Can be delay middle UI and api, because sometimes in UI you will not see sync message. And sync can take time. I check logs, they stop updating as well as the UI the block chain is not current. This has been waiting for over an hour to sync.... So stop and restarted and sync continued right away... What in logs? Why it's stopped? I have just restarted so will post here again when it happens.on 1100 block on initial sync it stopped at 215 last time. Hm, can you send me your blockchain.db? Sure will DM you with link shortly |
|
|
|
|
|
