Simplewallet error

Technical discussions related to CryptoNote repository and the forking process

Simplewallet error

Postby tingyeeh » Fri Mar 11, 2016 6:37 am

Hi, first, I'd like to thank you, anyone could help.
After finish complied, I got error,
Code: Select all
ubuntu@i-0jygrlx0:~/youthcoin/build/release/src$ ./simplewallet --generate-new-wallet test --password test
youthcoin wallet v1.1.1.1()
Error: failed to save new wallet: error opening file: test.wallet
Error: failed to generate new wallet: error opening file: test.wallet
account creation failed
Failed to initialize wallet
Error: wallet failed to connect to daemon (http://localhost:17362).
Error: wallet failed to connect to daemon (http://localhost:17362).

Can I know what is going on?
tingyeeh
 
Posts: 6
Joined: Fri Mar 11, 2016 5:14 am

Re: Simplewallet error

Postby Clever Crypto » Fri Mar 11, 2016 1:49 pm

It's not clear why you got creating wallet error. There could be plenty of reasons. Maybe you don't have write permission to a folder, maybe you're out of free space or maybe this is something else.
Regarding connecting to the daemon error - you have to run daemon before running simplewallet.
Clever Crypto
 
Posts: 33
Joined: Tue May 26, 2015 12:25 pm

Re: Simplewallet error

Postby tingyeeh » Fri Mar 11, 2016 2:41 pm

Dear Clever Crypto,
Thank you for kind reply,
It's new clould hosting, full of space.
Am I type blow that mean run the daemon, or have should do something first.
I still can't figur it out.
Code: Select all
ubuntu@i-0jygrlx0:~/youthcoin/build/release/src$ ./youthcoind --print-genesis-tx
tingyeeh
 
Posts: 6
Joined: Fri Mar 11, 2016 5:14 am

Re: Simplewallet error

Postby Clever Crypto » Tue Mar 15, 2016 10:57 am

To run the daemon you use ./youthcoind.

And - you use ./youthcoind --print-genesis-tx command just once during the coin creating process. The output of this command is saved in the src/CryptoNoteConfig.h file and after that the whole project is recompiled. And after that you'd get your daemon files (youthcoind) and wallet files (simplewallet), and you must use them in the future.
Wallet (simplewallet) communictaes with the daemon (youthcoind), so before launching the wallet you must launch the daemon.
Clever Crypto
 
Posts: 33
Joined: Tue May 26, 2015 12:25 pm

Re: Simplewallet error

Postby tingyeeh » Wed Mar 16, 2016 8:41 am

Dear Clever Crypto,
Thank you for you support all the time,
After I tried, show below:
Code: Select all
root@iZ62xml6b7mZ:~/youthcoin/build/release/src# ./youthcoind
15:30:09.981763 INFO youthcoin v1.1.1.1()
15:30:09.982432 INFO Module folder: ./youthcoind
15:30:09.984455 INFO Initializing p2p server...
15:30:09.984939 INFO Binding on 0.0.0.0:16362
15:30:09.985117 INFO Net service binded on 0.0.0.0:16362
15:30:09.985235 INFO Attempting to add IGD port mapping.
15:30:13.989625 INFO No IGD was found.
15:30:13.989863 INFO P2p server initialized OK
15:30:13.990009 INFO Initializing core...
15:30:13.990273 INFO Loading blockchain...
15:30:13.990508 INFO - loading block index...
15:30:13.990616 INFO - loading transaction map...
15:30:13.990697 INFO - loading spent keys...
15:30:13.990773 INFO - loading outputs...
15:30:13.990901 INFO - loading multi-signature outputs...
15:30:13.990994 INFO Serialization time: 0ms
15:30:13.991074 INFO Loading blockchain indices for BlockchainExplorer...
15:30:13.991204 INFO - loading paymentID index...
15:30:13.991296 INFO - loading timestamp index...
15:30:13.991373 INFO - loading generated transactions index...
15:30:13.991492 INFO Blockchain initialized. last block: 0, d1351.h2.m30.s13 time ago, current difficulty: 1
15:30:13.991611 INFO Core initialized OK
15:30:13.991834 INFO Starting core rpc server on address 127.0.0.1:17362
15:30:13.992148 INFO Core rpc server started ok
15:30:13.992281 INFO Starting p2p net loop...
15:30:13.992363 INFO Starting node_server
15:30:18.996068 INFO
15:30:18.996068 INFO **********************************************************************
15:30:18.996068 INFO You are now synchronized with the network. You may now start simplewallet.
15:30:18.996068 INFO
15:30:18.996068 INFO Please note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command.
15:30:18.996068 INFO Otherwise, you will possibly need to synchronize the blockchain again.
15:30:18.996068 INFO
15:30:18.996068 INFO Use "help" command to see the list of available commands.
15:30:18.996068 INFO **********************************************************************
15:30:18.997375 INFO
15:30:18.997375 INFO **********************************************************************
15:30:18.997375 INFO The daemon will start synchronizing with the network. It may take up to several hours.
15:30:18.997375 INFO
15:30:18.997375 INFO You can set the level of process detailization* through "set_log <level>" command*, where <level> is between 0 (no details) and 4 (very verbose).
15:30:18.997375 INFO
15:30:18.997375 INFO Use "help" command to see the list of available commands.
15:30:18.997375 INFO
15:30:18.997375 INFO Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved.
15:30:18.997375 INFO **********************************************************************
15:30:18.998437 WARNING [47.89.45.133:33424 INC] Exception in connectionHandler: TcpConnection::read
15:30:21.002050 WARNING [47.89.45.133:46106 INC] Exception in connectionHandler: TcpConnection::read
15:30:23.005560 WARNING [47.89.45.133:35786 INC] Exception in connectionHandler: TcpConnection::read
15:30:24.009101 WARNING [47.89.45.133:58099 INC] Exception in connectionHandler: TcpConnection::read
15:30:31.013389 WARNING [47.89.45.133:50080 INC] Exception in connectionHandler: TcpConnection::read
15:30:33.016093 WARNING [47.89.45.133:52392 INC] Exception in connectionHandler: TcpConnection::read
15:30:40.020276 WARNING [47.89.45.133:52778 INC] Exception in connectionHandler: TcpConnection::read
^C15:30:41.738268 INFO Stop signal sent
15:30:41.738531 INFO Stopping NodeServer and it's0 connections...
15:30:41.738818 INFO NodeServer loop stopped
15:30:41.739005 INFO p2p net loop stopped
15:30:41.739090 INFO Stopping core rpc server...
15:30:41.739279 INFO Deinitializing core...
15:30:41.739375 INFO Mining has been stopped, 0 finished
15:30:41.739693 INFO Saving blockchain...
15:30:41.739867 INFO - saving block index...
15:30:41.740023 INFO - saving transaction map...
15:30:41.740124 INFO - saving spent keys...
15:30:41.740227 INFO - saving outputs...
15:30:41.740394 INFO - saving multi-signature outputs...
15:30:41.740481 INFO Serialization time: 0ms
15:30:41.740644 INFO Saving blockchain indices...
15:30:41.740798 INFO - saving paymentID index...
15:30:41.740910 INFO - saving timestamp index...
15:30:41.741012 INFO - saving generated transactions index...
15:30:41.741177 INFO Deinitializing p2p...
15:30:41.741601 INFO Mining has been stopped, 0 finished
SwappedVector cache hits: 5, misses: 1 (16.67%)
15:30:41.742370 INFO Node stopped.

My Public IP 47.89.45.133, Internal IP 10.172.73.134
P2P port 16362, RPC port 17362
After I google, is that mean I under the NAT,
So I tried ./youthcoind --p2p-external-port=16362 show below
Code: Select all
root@iZ62xml6b7mZ:~/youthcoin/build/release/src# ./youthcoind --p2p-external-port=16362
15:38:02.085060 INFO youthcoin v1.1.1.1()
15:38:02.085441 INFO Module folder: ./youthcoind
15:38:02.086788 INFO Initializing p2p server...
15:38:02.087155 INFO Binding on 0.0.0.0:16362
15:38:02.087341 INFO Net service binded on 0.0.0.0:16362
15:38:02.087480 INFO External port defined as 16362
15:38:02.087588 INFO Attempting to add IGD port mapping.
15:38:06.092427 INFO No IGD was found.
15:38:06.092740 INFO P2p server initialized OK
15:38:06.092894 INFO Initializing core...
15:38:06.093189 INFO Loading blockchain...
15:38:06.093461 INFO - loading block index...
15:38:06.093624 INFO - loading transaction map...
15:38:06.093769 INFO - loading spent keys...
15:38:06.093919 INFO - loading outputs...
15:38:06.094028 INFO - loading multi-signature outputs...
15:38:06.094113 INFO Serialization time: 0ms
15:38:06.094239 INFO Loading blockchain indices for BlockchainExplorer...
15:38:06.094425 INFO - loading paymentID index...
15:38:06.094521 INFO - loading timestamp index...
15:38:06.094638 INFO - loading generated transactions index...
15:38:06.095127 INFO Blockchain initialized. last block: 0, d1351.h2.m38.s6 time ago, current difficulty: 1
15:38:06.095518 INFO Core initialized OK
15:38:06.095997 INFO Starting core rpc server on address 127.0.0.1:17362
15:38:06.096581 INFO Core rpc server started ok
15:38:06.096946 INFO Starting p2p net loop...
15:38:06.097248 INFO Starting node_server
15:38:11.101778 INFO
15:38:11.101778 INFO **********************************************************************
15:38:11.101778 INFO You are now synchronized with the network. You may now start simplewallet.
15:38:11.101778 INFO
15:38:11.101778 INFO Please note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command.
15:38:11.101778 INFO Otherwise, you will possibly need to synchronize the blockchain again.
15:38:11.101778 INFO
15:38:11.101778 INFO Use "help" command to see the list of available commands.
15:38:11.101778 INFO **********************************************************************
15:38:11.104628 INFO
15:38:11.104628 INFO **********************************************************************
15:38:11.104628 INFO The daemon will start synchronizing with the network. It may take up to several hours.
15:38:11.104628 INFO
15:38:11.104628 INFO You can set the level of process detailization* through "set_log <level>" command*, where <level> is between 0 (no details) and 4 (very verbose).
15:38:11.104628 INFO
15:38:11.104628 INFO Use "help" command to see the list of available commands.
15:38:11.104628 INFO
15:38:11.104628 INFO Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved.
15:38:11.104628 INFO **********************************************************************
15:38:11.105984 WARNING [47.89.45.133:38668 INC] Exception in connectionHandler: TcpConnection::read
15:39:47.194695 WARNING [47.89.45.133:44998 INC] Exception in connectionHandler: TcpConnection::read
15:39:54.199121 WARNING [47.89.45.133:44752 INC] Exception in connectionHandler: TcpConnection::read
^C15:39:55.782992 INFO Stop signal sent
15:39:55.783514 INFO Stopping NodeServer and it's0 connections...
15:39:55.784073 INFO NodeServer loop stopped
15:39:55.784337 INFO p2p net loop stopped
15:39:55.784731 INFO Stopping core rpc server...
15:39:55.785062 INFO Deinitializing core...
15:39:55.785214 INFO Mining has been stopped, 0 finished
15:39:55.785508 INFO Saving blockchain...
15:39:55.785749 INFO - saving block index...
15:39:55.785908 INFO - saving transaction map...
15:39:55.786028 INFO - saving spent keys...
15:39:55.786146 INFO - saving outputs...
15:39:55.786283 INFO - saving multi-signature outputs...
15:39:55.786394 INFO Serialization time: 0ms
15:39:55.786585 INFO Saving blockchain indices...
15:39:55.786779 INFO - saving paymentID index...
15:39:55.786941 INFO - saving timestamp index...
15:39:55.787066 INFO - saving generated transactions index...
15:39:55.787242 INFO Deinitializing p2p...
15:39:55.787539 INFO Mining has been stopped, 0 finished
SwappedVector cache hits: 5, misses: 1 (16.67%)
15:39:55.788212 INFO Node stopped.
tingyeeh
 
Posts: 6
Joined: Fri Mar 11, 2016 5:14 am

Re: Simplewallet error

Postby MaxJameson » Wed Mar 16, 2016 12:27 pm

Could you please be more specific - what exactly do you want to do and what result do you expect?

I don't quite get your intentions yet, so i'm speculating here.
If you just want to run the daemon, you did it with the first command. But just launching the daemon gives you nothing.
If you want to launch a currency, you have to run a seed node, as it described in the documentation. You have to set the address of this seed node in CryptoNoteConfig.h.
Then you have to run a daemon on the different computer, it will connect to the seed node and after this mining process could be started.
If other daemon has some issues with connecting to seed node, you ll deal with it then - check port, for instance. If it's closed, you have to open it, and only in that case you could need --p2p-external-port parameter. But the port in question must be NAT open, a simple indication of this parameter gives you nothing.
MaxJameson
 
Posts: 6
Joined: Wed Mar 26, 2014 3:21 pm

Re: Simplewallet error

Postby tingyeeh » Wed Mar 16, 2016 3:53 pm

Dear MaxJameson,
Tks for your kind reply,
I want to run the daeman and mining, still can not mining.
After I tried several way, still can not fix, may some problem with my
1. I complied the daeman,
2. I put the IP in to the src/CryptoNoteConfig.h before the complied,
Code: Select all
"118.193.143.78:16362", #second daeman
"47.89.45.133:16362", #local hosting

3. I successed print the HX, and recomplied,
4. After finished above, can not mining, so I going to find out what is the problem in side.
Above reply were the result when I tried.
Could you help to fingure out what's problem inside?
tingyeeh
 
Posts: 6
Joined: Fri Mar 11, 2016 5:14 am

Re: Simplewallet error

Postby MaxJameson » Mon Mar 21, 2016 11:18 am

You can try this:
You have to add to src/CryptoNoteConfig.h daemons addresses, which you constantly run on hosting. Only those addresses, nothing else. Those gonna be seeds.

For mining you have to run at least two daemons, which are not seeds. Common daemons connect to the seeds and disconnect right away. Seeds are not common daemons!

Actually, to test mining you can run few daemons even on one computer, they will be connected to each other and disconnected from seeds.
You could visit this topic to learn more -
https://forum.cryptonote.org/viewtopic. ... =956#p2127
You will have to use --add-exclusive-node parameter.
MaxJameson
 
Posts: 6
Joined: Wed Mar 26, 2014 3:21 pm


Return to Reference Code & Forking

Who is online

Users browsing this forum: No registered users and 4 guests

cron