Author

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

hero member
Activity: 511
Merit: 500
Boris, Crypti Lead Developer, Lisk Advisor
We have problems now with billing on crypti.me
Once i will get response from hoster support it will work again.

Some news, i'm now working with fork processing fixes, blockchain loading, and sync.
legendary
Activity: 1367
Merit: 1000
Tried to launch Crypti on Cubieboard (with full database from other node)  Embarrassed
What to say...  Roll Eyes
4 hours passed and it still not launched - Blockchain loading: (12668/18072 blocks)  Shocked

Devs, current implementaition is somewhat very wrong. Not saying about some ecology stuff, but this launching/syncung things are unacceptable  Angry

Remember NXT when it went public? It was horrible, there were up to few daily client updates with frequent redownloading of everything. Blockchain was going nuts and resync
was almost hourly occurence. It took NXT developers few months to iron all major bugs out but check NXT now - working well (few minor issues) and "glued" to top 5 marketcap.
Yes, you are talking with NXT genesis stakeholder.  Grin
And i also remember how supportive NXT devs were, how often new client versions come, how they cared about NXT network.  Cool
Do you see the same here?  Roll Eyes
newbie
Activity: 49
Merit: 0
No chance to get my nodes in sync again. one node freezes every time while resyncing and two other Nodes creating forks
legendary
Activity: 1288
Merit: 1043
:^)
Tried to launch Crypti on Cubieboard (with full database from other node)  Embarrassed
What to say...  Roll Eyes
4 hours passed and it still not launched - Blockchain loading: (12668/18072 blocks)  Shocked

Devs, current implementaition is somewhat very wrong. Not saying about some ecology stuff, but this launching/syncung things are unacceptable  Angry

Remember NXT when it went public? It was horrible, there were up to few daily client updates with frequent redownloading of everything. Blockchain was going nuts and resync
was almost hourly occurence. It took NXT developers few months to iron all major bugs out but check NXT now - working well (few minor issues) and "glued" to top 5 marketcap.

Bitcoin was not all shinny and glorious in the begining neither and same goes for any brand new tech.

@ Crypti developers

Is there any chance you could persuade Bter to lower withdrawal fee for XCR? 1% + 1 XCR is simply too much coins taken for action everyone else allow with minimum fees.
full member
Activity: 278
Merit: 100
Boris just an update - left service running over night about 7 hours and sync did not move on from the block it stopped at when we were talking last night. Have restarted it again to kick sync off.
full member
Activity: 150
Merit: 100
Both nodes have been running perfectly the whole day. No memory issues or hang ups. One node is on digital ocean and the other is at my house.

I did have an issue last night with one node (at home) after loading blocks. It would finally load all blocks then just stop. The log just showed the last blocks being loaded then nothing else. I was trying to use a previously saved blockchain tho. Stopping the node then deleting blockchain and starting again fixed it after it downloaded the blockchain again. It was weird and haven't seen the same issue since.

My only question now is what's with this admin panel? How do you access it? I've tried setting the parameters in the config file...user, pass, ip whitelist then restarted but don't see any buttons to access it anywhere. Can the devs give us more info on it? Not that I need it since my node is already set for forging, I just wanted to check it out tho.
hero member
Activity: 511
Merit: 500
Boris, Crypti Lead Developer, Lisk Advisor
Tried to launch Crypti on Cubieboard (with full database from other node)  Embarrassed
What to say...  Roll Eyes
4 hours passed and it still not launched - Blockchain loading: (12668/18072 blocks)  Shocked

Devs, current implementaition is somewhat very wrong. Not saying about some ecology stuff, but this launching/syncung things are unacceptable  Angry

Rome wasn't built in a day Smiley
I'm working on bugs
legendary
Activity: 1367
Merit: 1000
Tried to launch Crypti on Cubieboard (with full database from other node)  Embarrassed
What to say...  Roll Eyes
4 hours passed and it still not launched - Blockchain loading: (12668/18072 blocks)  Shocked

Devs, current implementaition is somewhat very wrong. Not saying about some ecology stuff, but this launching/syncung things are unacceptable  Angry
hero member
Activity: 518
Merit: 500
What is that old saying? Rome wasn't built in a day?  Grin
member
Activity: 80
Merit: 10
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.

This is unlike 99% of the other coins out there. It is being built from the ground up. So there is going to be a lot of testing and tweaking things to get everything working perfect. Think of it as a beta version of software.. If you do not have patience for it, sell your coins and move along.

Regards,
Brian

Please stay with us @profitofthegods, Smiley I appreciate your time spent, and recognize your efforts.
legendary
Activity: 1121
Merit: 1003
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.

This is unlike 99% of the other coins out there. It is being built from the ground up. So there is going to be a lot of testing and tweaking things to get everything working perfect. Think of it as a beta version of software.. If you do not have patience for it, sell your coins and move along.

Regards,
Brian
hero member
Activity: 511
Merit: 500
Boris, Crypti Lead Developer, Lisk Advisor
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

Ok, thanks
full member
Activity: 278
Merit: 100
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
hero member
Activity: 511
Merit: 500
Boris, Crypti Lead Developer, Lisk Advisor
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?
full member
Activity: 278
Merit: 100
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.
hero member
Activity: 511
Merit: 500
Boris, Crypti Lead Developer, Lisk Advisor
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?
full member
Activity: 278
Merit: 100
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...
hero member
Activity: 511
Merit: 500
Boris, Crypti Lead Developer, Lisk Advisor
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.
full member
Activity: 278
Merit: 100
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....

member
Activity: 238
Merit: 10
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
Jump to: