Crypti Review + Score (3.0/5 Great) now available on Coins Source
http://www.coinssource.com/crypto-coins/crypti/
Topic: [XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 331. (Read 804713 times)
August 25, 2014, 06:20:09 PM
August 25, 2014, 06:19:03 PM
{"level":"warn","message":"Request already added: 4481046574929300723/6127372741261621508C","timestamp":"2014-08-25T04:53:30.540Z"}
{"level":"info","message":"Process blocks from peer: 72.95.14.201","timestamp":"2014-08-25T04:53:31.541Z"}
{"level":"info","message":"Process requests...","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Get requests from 107.170.126.199","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Process unconfirmed transactions...","timestamp":"2014-08-25T04:53:32.975Z"}
These are my last lines from the cat logs.log. Now I am trying to access my wallet as per "After it starts,open: http://serverip:6040/ <--- Replace "serverip" with Your Public IP" but It keeps getting stuck on Unable to connect.
{"level":"info","message":"Process blocks from peer: 72.95.14.201","timestamp":"2014-08-25T04:53:31.541Z"}
{"level":"info","message":"Process requests...","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Get requests from 107.170.126.199","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Process unconfirmed transactions...","timestamp":"2014-08-25T04:53:32.975Z"}
These are my last lines from the cat logs.log. Now I am trying to access my wallet as per "After it starts,open: http://serverip:6040/ <--- Replace "serverip" with Your Public IP" but It keeps getting stuck on Unable to connect.
What about your firewall or security settings?
You have to allow TCP incomming connections to port 6040
August 25, 2014, 05:59:47 PM
If you trying to launch the wallet before it is fully synchronized it will cause the Node to restart the sync process...
This is not true. 
I can see blockchain syncronizing from scratch in browser on another node.
Not 20 minutes, 2 hours and no blockchain.
Docker will launch empty and sync
However this was in reference to a Forging node on AWS
August 25, 2014, 05:36:31 PM
I'm not sure what you mean by forever list. This is my first install of Ubuntu/Linux, and it was done for the sole purpose of putting up a node and forging Crypti.
When you run 'forever list' it will tell you how long its been up.
In this image you can see mine has been up 4 hours, 29 minutes, and 20 seconds.
August 25, 2014, 05:35:20 PM
Why is this coin so under valued? Less than 2,000 BTC?
It's not heavily developed yet. As you can read from the past few pages there are alot of people having trouble with the Linux install.
There are no problems right now. Everything is working fine and smoothly.
This is not true, see my problem with 0.1.5 and 0.1.5b. Crypti does not work at all on Ubuntu 14.04 desktop with nothing else installed but Crypti + the components it needs:
https://bitcointalksearch.org/topic/m.8528786
August 25, 2014, 05:32:10 PM
The docker install instructions are much easier to follow if you are having trouble with the manual setup.
Docker install is more awfull When i run Start it now says that docker daemon is not running (was somehow running and installed Crypti)
Boot2Docker will not install correctly in many cases if you have already VMWare on your system, as it installs Oracle Virtual Box in the background, and VMWare + Virtual Box network components often do not like each other. In more detail, if you have VMNet on Slot #8 with VMWare, Virtual Box will not install giving a meaningless error. Boot2Docker does not check if Virtual Box installed successfully or not.
August 25, 2014, 05:29:12 PM
If you trying to launch the wallet before it is fully synchronized it will cause the Node to restart the sync process...
This is not true. I can see blockchain syncronizing from scratch in browser on another node.
Not 20 minutes, 2 hours and no blockchain.
I'll tell you something that changed things up for me that aren't quite clear in the instruction is adding the legacy properly. In step 1
Code:
On debian repositories must be found, on ubuntu if repositories not found:
Use this tutorial to add nodejs ppa repo:
https://launchpad.net/~chris-lea/+archive/ubuntu/node.js-legacy
Again update your system repositories and install nodejs:
Use this tutorial to add nodejs ppa repo:
https://launchpad.net/~chris-lea/+archive/ubuntu/node.js-legacy
Again update your system repositories and install nodejs:
It took me a second to read through that page and realize you have to:
sudo apt-add-repository ppa:chris-lea/node.js-legacy
Then when you run sudo apt-get you'll see the ppa node.js-legacy in the list.
August 25, 2014, 05:23:19 PM
I started the whole process yesterday but could not make it run so I just went to bed and now I'm back at it. Must be 12hr's+/
I'm not sure what you mean by forever list. This is my first install of Ubuntu/Linux, and it was done for the sole purpose of putting up a node and forging Crypti.
What's your
forever list
uptime? How long have you been up?
forever list
uptime? How long have you been up?
I'm not sure what you mean by forever list. This is my first install of Ubuntu/Linux, and it was done for the sole purpose of putting up a node and forging Crypti.
August 25, 2014, 05:19:35 PM
{"level":"warn","message":"Request already added: 4481046574929300723/6127372741261621508C","timestamp":"2014-08-25T04:53:30.540Z"}
{"level":"info","message":"Process blocks from peer: 72.95.14.201","timestamp":"2014-08-25T04:53:31.541Z"}
{"level":"info","message":"Process requests...","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Get requests from 107.170.126.199","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Process unconfirmed transactions...","timestamp":"2014-08-25T04:53:32.975Z"}
These are my last lines from the cas logs.log. Now I am trying to access my wallet as per "After it starts,open: http://serverip:6040/ <--- Replace "serverip" with Your Public IP" but It keeps getting stuck on Unable to connect.
{"level":"info","message":"Process blocks from peer: 72.95.14.201","timestamp":"2014-08-25T04:53:31.541Z"}
{"level":"info","message":"Process requests...","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Get requests from 107.170.126.199","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Process unconfirmed transactions...","timestamp":"2014-08-25T04:53:32.975Z"}
These are my last lines from the cas logs.log. Now I am trying to access my wallet as per "After it starts,open: http://serverip:6040/ <--- Replace "serverip" with Your Public IP" but It keeps getting stuck on Unable to connect.
What's your
forever list
uptime? It usually takes me about twenty minutes to start forging but it comes up within two before I change my secrePhrase.
August 25, 2014, 05:16:15 PM
{"level":"warn","message":"Request already added: 4481046574929300723/6127372741261621508C","timestamp":"2014-08-25T04:53:30.540Z"}
{"level":"info","message":"Process blocks from peer: 72.95.14.201","timestamp":"2014-08-25T04:53:31.541Z"}
{"level":"info","message":"Process requests...","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Get requests from 107.170.126.199","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Process unconfirmed transactions...","timestamp":"2014-08-25T04:53:32.975Z"}
These are my last lines from the cat logs.log. Now I am trying to access my wallet as per "After it starts,open: http://serverip:6040/ <--- Replace "serverip" with Your Public IP" but It keeps getting stuck on Unable to connect.
{"level":"info","message":"Process blocks from peer: 72.95.14.201","timestamp":"2014-08-25T04:53:31.541Z"}
{"level":"info","message":"Process requests...","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Get requests from 107.170.126.199","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Process unconfirmed transactions...","timestamp":"2014-08-25T04:53:32.975Z"}
These are my last lines from the cat logs.log. Now I am trying to access my wallet as per "After it starts,open: http://serverip:6040/ <--- Replace "serverip" with Your Public IP" but It keeps getting stuck on Unable to connect.
August 25, 2014, 05:14:51 PM
If you trying to launch the wallet before it is fully synchronized it will cause the Node to restart the sync process...
This is not true. I can see blockchain syncronizing from scratch in browser on another node.
Not 20 minutes, 2 hours and no blockchain.
August 25, 2014, 05:12:07 PM
Dev's any sign of getting your BTC? To get things flying....
http://blog.crypti.me/crypti-foundation-btc-funds/
informer
August 25, 2014, 05:03:00 PM
Dev's any sign of getting your BTC? To get things flying....
August 25, 2014, 04:54:21 PM
Why is this coin so under valued? Less than 2,000 BTC?
It's not heavily developed yet. As you can read from the past few pages there are alot of people having trouble with the Linux install.
There are no problems right now. Everything is working fine and smoothly.
August 25, 2014, 04:51:31 PM
The docker install instructions are much easier to follow if you are having trouble with the manual setup.
Docker install is more awfull When i run Start it now says that docker daemon is not running (was somehow running and installed Crypti)
Forging is explained in detail throughout this thread and in some of our documentation. What questions do you have about how forging works? Maybe if you pose them here myself or others can explain to help clear up the confusion.
Whitepaper is very vague... What weights in PoT and what exactly is weighted? 
Also, if you post whatever errors you are getting, the community here is very quick to respond and help out!
No errors. Node is running but blockchain in browser is empty well if it's a bit technical. You can wait for the Windows wallet
August 25, 2014, 04:49:51 PM
Yes you must wait for the Node to fully synchronized before trying to launch the wallet in your browser... If you trying to launch the wallet before it is fully synchronized it will cause the Node to restart the sync process... So either monitor your Log or just wait 20 mins to launch the wallet in your browser..
To monitor your Node logs Run this command
To monitor your Node logs Run this command
Code:
cat logs.log
you could also use tail -f logs.log to see a real time updating view of the logfile in the console, ctrl+c to stop it
August 25, 2014, 04:41:08 PM
Terrible coin
Client setup is far more worse than first versions of NXT
Forging algo is mystery
Somehow i get node running, logs are updating, but in browser i see no blockchain, no transactions in my account
Client setup is far more worse than first versions of NXT
Forging algo is mystery
Somehow i get node running, logs are updating, but in browser i see no blockchain, no transactions in my account
If you're node is setup correctly, you should see a green Forging enabled logo in the top right of the forging tab. It takes about 20 minutes or so after you forever start app.js to sync up (at least for me running on AWS E2 Ubuntu 14.04). You're blockchain page should match https://wallet.crypti.me/blockchain exactly. If you need help, reach and touch somebody. This is a very helpful community supporting this coin. Good luck!
informer
Yes you must wait for the Node to fully synchronized before trying to launch the wallet in your browser... If you trying to launch the wallet before it is fully synchronized it will cause the Node to restart the sync process... So either monitor your Log or just wait 20 mins to launch the wallet in your browser..
To monitor your Node logs Run this command
Code:
cat logs.log
August 25, 2014, 04:37:25 PM
gives me a no such file or directory error, opening it in browser gives me a access denied xml error
Please try again.
August 25, 2014, 04:33:54 PM
Why did the block time changed from 61 seconds to 120 seconds?
August 25, 2014, 04:32:37 PM
gives me a no such file or directory error, opening it in browser gives me a access denied xml error
Please try again.
Jump to: