[XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 287.

samsmith16

sr. member

Activity: 490

Merit: 250

Quote from: profitofthegods on September 07, 2014, 01:28:33 PM

Quote from: samsmith16 on September 07, 2014, 01:22:00 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

samsmith16

sr. member

Activity: 490

Merit: 250

Quote from: informer on September 07, 2014, 01:10:18 PM

Quote from: schmelix on September 07, 2014, 12:21:27 PM

Quote from: profitofthegods on September 07, 2014, 12:09:23 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...

crypti

hero member

Activity: 511

Merit: 500

Boris, Crypti Lead Developer, Lisk Advisor

Quote from: canej on September 07, 2014, 01:31:32 PM

Quote from: samsmith16 on September 07, 2014, 01:26:01 PM

Quote from: canej on September 07, 2014, 01: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?

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.

canej

full member

Activity: 278

Merit: 100

Quote from: samsmith16 on September 07, 2014, 01:26:01 PM

Quote from: canej on September 07, 2014, 01: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?

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

profitofthegods

sr. member

Activity: 378

Merit: 250

Quote from: samsmith16 on September 07, 2014, 01:22:00 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?

samsmith16

sr. member

Activity: 490

Merit: 250

Quote from: canej on September 07, 2014, 01: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?

If your not seeing the same info on the web wallet then your local wallet is out of sync...

samsmith16

sr. member

Activity: 490

Merit: 250

Quote from: schmelix on September 07, 2014, 01:04:35 PM

Quote from: samsmith16 on September 07, 2014, 12:42:19 PM

Quote from: profitofthegods on September 07, 2014, 12:23:01 PM

Quote from: Wulfcastle on September 07, 2014, 12:16:02 PM

Quote from: profitofthegods on September 07, 2014, 12:11:57 PM

Quote from: Wulfcastle on September 07, 2014, 12:11:28 PM

Quote from: profitofthegods on September 07, 2014, 12:09:23 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...

canej

full member

Activity: 278

Merit: 100

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?

informer

member

Activity: 238

Merit: 10

Quote from: schmelix on September 07, 2014, 12:21:27 PM

Quote from: profitofthegods on September 07, 2014, 12:09:23 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

schmelix

newbie

Activity: 49

Merit: 0

Quote from: samsmith16 on September 07, 2014, 12:42:19 PM

Quote from: profitofthegods on September 07, 2014, 12:23:01 PM

Quote from: Wulfcastle on September 07, 2014, 12:16:02 PM

Quote from: profitofthegods on September 07, 2014, 12:11:57 PM

Quote from: Wulfcastle on September 07, 2014, 12:11:28 PM

Quote from: profitofthegods on September 07, 2014, 12:09:23 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

schmelix

newbie

Activity: 49

Merit: 0

Quote from: SyRenity on September 07, 2014, 12:39:34 PM

Quote from: schmelix on September 07, 2014, 12:21:27 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

Code:

forever stop app.js; rm -f logs.log blockchain.db; forever start app.js

profitofthegods

sr. member

Activity: 378

Merit: 250

Quote from: SyRenity on September 07, 2014, 12:36:54 PM

Quote from: profitofthegods on September 07, 2014, 12:23:01 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.

Quote from: SyRenity on September 07, 2014, 12:38:29 PM

Quote from: profitofthegods on September 07, 2014, 12:28:29 PM

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.

samsmith16

sr. member

Activity: 490

Merit: 250

Quote from: profitofthegods on September 07, 2014, 12:23:01 PM

Quote from: Wulfcastle on September 07, 2014, 12:16:02 PM

Quote from: profitofthegods on September 07, 2014, 12:11:57 PM

Quote from: Wulfcastle on September 07, 2014, 12:11:28 PM

Quote from: profitofthegods on September 07, 2014, 12:09:23 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

SyRenity

hero member

Activity: 756

Merit: 502

Quote from: schmelix on September 07, 2014, 12:21:27 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.

SyRenity

hero member

Activity: 756

Merit: 502

Quote from: profitofthegods on September 07, 2014, 12:28:29 PM

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.

SyRenity

hero member

Activity: 756

Merit: 502

Quote from: profitofthegods on September 07, 2014, 12:23:01 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 issues with Crypti.

On the latest 0.1.6b release we have changed the fork recovery mechanism to avoid high RAM usage, and while we have extensively tested it, there still might be some issues pending.

Please send me and Boris (crypti) the logs via PM, so we could review them.

profitofthegods

sr. member

Activity: 378

Merit: 250

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?

profitofthegods

sr. member

Activity: 378

Merit: 250

Quote from: Wulfcastle on September 07, 2014, 12:16:02 PM

Quote from: profitofthegods on September 07, 2014, 12:11:57 PM

Quote from: Wulfcastle on September 07, 2014, 12:11:28 PM

Quote from: profitofthegods on September 07, 2014, 12:09:23 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.

schmelix

newbie

Activity: 49

Merit: 0

Quote from: profitofthegods on September 07, 2014, 12:09:23 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

Wulfcastle

hero member

Activity: 546

Merit: 500

Quote from: profitofthegods on September 07, 2014, 12:11:57 PM

Quote from: Wulfcastle on September 07, 2014, 12:11:28 PM

Quote from: profitofthegods on September 07, 2014, 12:09:23 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.

Topic: [XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 287. (Read 804700 times)