|
yeasee
|
 |
August 24, 2014, 01:24:19 PM |
|
XCR is better than any 2nd crypto.It's new and full of power.we need to build a strong community!  |
|
|
|
|
|
profitofthegods
|
|
August 24, 2014, 01:33:46 PM |
|
Just tried this on AWS and the same thing happened as before - looks fine until I edit the config file then the log shows not synched and the web wallet becomes unreachable.
You just added password, and the node stopped working? Please wait till until the wallet synced and try again, otherwise PM Boris (crypti) the logs.. Yes that is what happened. Found this in the logs, could this be the problem? {"level":"error","message":"Invalid payload length: 17075758229493073066 length: 496 buffer length: 440","timestamp":"2014-08-24T13:28:26.702Z"}
{"level":"info","message":"Crypti stopped!","timestamp":"2014-08-24T13:28:26.702Z"}
{"level":"error","message":"Error: Can't process block: 17075758229493073066","timestamp":"2014-08-24T13:28:26.702Z"}
|
|
|
|
|
|
SyRenity
|
|
August 24, 2014, 01:36:18 PM |
|
{"level":"error","message":"Invalid payload length: 17075758229493073066 length: 496 buffer length: 440","timestamp":"2014-08-24T13:28:26.702Z"}
{"level":"info","message":"Crypti stopped!","timestamp":"2014-08-24T13:28:26.702Z"}
{"level":"error","message":"Error: Can't process block: 17075758229493073066","timestamp":"2014-08-24T13:28:26.702Z"}
Please erase the old blockchain and try again. |
|
|
|
|
|
prix
|
|
August 24, 2014, 01:46:46 PM |
|
One of my nodes has created its own branch, but then these incorrect blocks were replaced by correct and now this node on the actual branch. Clear improvement compared to the previous version. I continue to watch.
|
|
|
|
|
|
SyRenity
|
|
August 24, 2014, 01:56:45 PM |
|
One of my nodes has created its own branch, but then these incorrect blocks were replaced by correct and now this node on the actual branch. Clear improvement compared to the previous version. I continue to watch.
This is actually the reason we skipped 0.1.4 and delayed a bit to get the 0.1.5 out of door, so the fork recovery could finally handle such situations as well. |
|
|
|
|
|
Wulfcastle
|
|
August 24, 2014, 01:58:34 PM |
|
One of my nodes has created its own branch, but then these incorrect blocks were replaced by correct and now this node on the actual branch. Clear improvement compared to the previous version. I continue to watch.
This is actually the reason we skipped 0.1.4 and delayed a bit to get the 0.1.5 out of door, so the fork recovery could finally handle such situations as well. SyRenity, could you explain the fork recovery a bit more in detail? |
|
|
|
|
|
profitofthegods
|
|
August 24, 2014, 02:11:17 PM |
|
Just tried this on AWS and the same thing happened as before - looks fine until I edit the config file then the log shows not synched and the web wallet becomes unreachable.
You just added password, and the node stopped working? Please wait till until the wallet synced and try again, otherwise PM Boris (crypti) the logs.. Yes that is what happened. Found this in the logs, could this be the problem? {"level":"error","message":"Invalid payload length: 17075758229493073066 length: 496 buffer length: 440","timestamp":"2014-08-24T13:28:26.702Z"}
{"level":"info","message":"Crypti stopped!","timestamp":"2014-08-24T13:28:26.702Z"}
{"level":"error","message":"Error: Can't process block: 17075758229493073066","timestamp":"2014-08-24T13:28:26.702Z"}
Found the problem! It doesn't like you editing files once its already running. I just started again from scratch but I edited the config file before running sudo npm install -g forever instead of afterwards as you have it in the instructions. Now I finally have Forging Enabled! |
|
|
|
|
|
informer
|
|
August 24, 2014, 02:11:42 PM |
|
{"level":"error","message":"Invalid payload length: 17075758229493073066 length: 496 buffer length: 440","timestamp":"2014-08-24T13:28:26.702Z"}
{"level":"info","message":"Crypti stopped!","timestamp":"2014-08-24T13:28:26.702Z"}
{"level":"error","message":"Error: Can't process block: 17075758229493073066","timestamp":"2014-08-24T13:28:26.702Z"}
Please erase the old blockchain and try again. I waited until my node synched with the most current block in the wallet Block section. I then shut it down, added my passphrase in config and then started app.js. After about two minutes the node/wallet came back up synched. 3815453598345862034 2014/08/24 09:05:55 0 0 15039240550091704731C Now mind you I have had a lot of problems with the SecretPhrase issue, so I don't know what is different this time, other than a refined product. informer |
|
|
|
|
SyRenity
|
|
August 24, 2014, 02:23:15 PM |
|
(Note, we found out some forging issues with the Docker version, hence this functionality, while possible, is not currently supported there. We will start investigating native Windows wallet shortly to avoid Docker altogether).
Is there any chance you will have another go at this before the native Windows wallets come out? Seems I said it incorrectly, the feature is present there and can be used, however if there will be any issues with it we won't support them, as we found the Boot2Docker VM networking quite unreliable (delays in PoT requests, etc...). To update you just need to follow: https://github.com/crypti/crypti-docs/blob/master/boot2docker.md#1-update-to-latest-crypti-docker-version |
|
|
|
|
BrokenRam
Newbie
 Offline
Activity: 16
Merit: 0
|
|
August 24, 2014, 02:23:49 PM |
|
Just tried this on AWS and the same thing happened as before - looks fine until I edit the config file then the log shows not synched and the web wallet becomes unreachable.
You just added password, and the node stopped working? Please wait till until the wallet synced and try again, otherwise PM Boris (crypti) the logs.. Yes that is what happened. Found this in the logs, could this be the problem? {"level":"error","message":"Invalid payload length: 17075758229493073066 length: 496 buffer length: 440","timestamp":"2014-08-24T13:28:26.702Z"}
{"level":"info","message":"Crypti stopped!","timestamp":"2014-08-24T13:28:26.702Z"}
{"level":"error","message":"Error: Can't process block: 17075758229493073066","timestamp":"2014-08-24T13:28:26.702Z"}
Found the problem! It doesn't like you editing files once its already running. I just started again from scratch but I edited the config file before running sudo npm install -g forever instead of afterwards as you have it in the instructions. Now I finally have Forging Enabled!Looks to be working from my end with Forging enabled. Likewise, instead of restarting the node. I stopped, edited configuration file and then started the node. |
|
|
|
|
|
SyRenity
|
|
August 24, 2014, 02:24:50 PM |
|
Looks to be working from my end with Forging enabled.
Likewise, instead of restarting the node. I stopped, edited configuration file and then started the node.
So the command forever restart app.js did not work for you, only stop/edit/start? |
|
|
|
|
|
Wulfcastle
|
|
August 24, 2014, 02:32:07 PM |
|
Hmm, I'm getting this error :  My node doesn't seem to be syncing. EDIT : Also everytime when I reboot my server, my node simply doesn't work anymore. I still run forever start app.js, everytime it reboots and everything seems to be working perfectly in the back end, but when I got to the web wallet, nothing loads |
|
|
|
|
|
atleticofa
|
|
August 24, 2014, 02:33:23 PM |
|
Everything fine now Good job devs |
|
|
|
|
|
informer
|
|
August 24, 2014, 02:36:36 PM |
|
Looks to be working from my end with Forging enabled.
Likewise, instead of restarting the node. I stopped, edited configuration file and then started the node.
So the command forever restart app.js did not work for you, only stop/edit/start? That's what worked for me. Without having to rebuild. I just downloaded 0.1.5.zip extracted it, ed25519 gyp fix and presto. informer |
|
|
|
BrokenRam
Newbie
Offline
Activity: 16
Merit: 0
|
|
August 24, 2014, 02:42:16 PM |
|
Looks to be working from my end with Forging enabled.
Likewise, instead of restarting the node. I stopped, edited configuration file and then started the node.
So the command forever restart app.js did not work for you, only stop/edit/start? Was getting "Can't forge, node not synchronized!" for over a minute, so just stopped the node. So might have sync'ed up given enough time... no patience on my part With stop/edit/start took under 10secs to synchronized. Also deleted the blockchain.db before starting up the node again. |
|
|
|
|
|
SyRenity
|
|
August 24, 2014, 02:47:58 PM |
|
I still run forever start app.js, everytime it reboots and everything seems to be working perfectly in the back end, but when I got to the web wallet, nothing loads
Your node might made it into a black-list that we implemented in 0.1.4 (which bans for some period the suspected attacking node). If you run on cloud, try to change the IP. Also make sure you erased the blockchain. |
|
|
|
|
|
informer
|
|
August 24, 2014, 02:49:51 PM |
|
I still run forever start app.js, everytime it reboots and everything seems to be working perfectly in the back end, but when I got to the web wallet, nothing loads
Your node might made it into a black-list that we implemented in 0.1.4 (which bans for some period the suspected attacking node). If you run on cloud, try to change the IP. Also make sure you erased the blockchain. Yes, you have to delete blockchain.db otherwise it becomes blockchain.db.1 AWS EC2 Ubuntu 14.04 informer |
|
|
|
|
elephantas1
|
|
August 24, 2014, 02:50:55 PM |
|
still no info about bter withdraws?
|
|
|
|
|
|
Wulfcastle
|
|
August 24, 2014, 02:51:09 PM |
|
I still run forever start app.js, everytime it reboots and everything seems to be working perfectly in the back end, but when I got to the web wallet, nothing loads
Your node might made it into a black-list that we implemented in 0.1.4 (which bans for some period the suspected attacking node). If you run on cloud, try to change the IP. Also make sure you erased the blockchain. No it runs fine and everything loads when I complete the installation process, I can access the web wallet fine, it's only once I reboot my server that it stops functioning. After rebooting the server the web wallet simply doesn't display anymore |
|
|
|
|
|
SyRenity
|
|
August 24, 2014, 02:52:53 PM |
|
That's what worked for me. Without having to rebuild. I just downloaded 0.1.5.zip extracted it, ed25519 gyp fix and presto.
Was getting "Can't forge, node not synchronized!" for over a minute, so just stopped the node. So might have sync'ed up given enough time... no patience on my part With stop/edit/start took under 10secs to synchronized. Also deleted the blockchain.db before starting up the node again. Thanks, I've updated the guide to stop/start just in case. |
|
|
|
|
|
