search

edollar-project / edollar

BSD 3-Clause "New" or "Revised" License
11 stars 7 forks source link

building on CentOS7.4 code not connecting #12

Closed kbuggenhout closed 6 years ago

kbuggenhout commented 6 years ago

haven successfully built edollard code, on invoking it does not connect, it fails with

[root@mine edollar]# edollard 2018-03-06 22:29:52.462 7fc3a7e12880 INFO global src/daemon/main.cpp:284 Edollar 'Mercury' (v0.1.0.0-87c178a) 2018-03-06 22:29:52.463 7fc3a7e12880 INFO global src/daemon/protocol.h:56 Initializing cryptonote protocol... 2018-03-06 22:29:52.463 7fc3a7e12880 INFO global src/daemon/protocol.h:61 Cryptonote protocol initialized OK 2018-03-06 22:29:52.464 7fc3a7e12880 INFO global src/daemon/p2p.h:64 Initializing p2p server... connect: Connection refused 2018-03-06 22:29:57.502 7fc3a7e12880 INFO global src/daemon/p2p.h:69 P2p server initialized OK 2018-03-06 22:29:57.502 7fc3a7e12880 INFO global src/daemon/rpc.h:59 Initializing core rpc server... 2018-03-06 22:29:57.502 7fc3a7e12880 INFO global contrib/epee/include/net/http_server_impl_base.h:75 Binding on 127.0.0.1:33031 2018-03-06 22:29:57.502 7fc3a7e12880 INFO global src/daemon/rpc.h:64 Core rpc server initialized OK on port: 33031 2018-03-06 22:29:57.502 7fc3a7e12880 INFO global src/daemon/core.h:74 Initializing core... 2018-03-06 22:29:57.502 7fc3a7e12880 INFO global src/cryptonote_core/cryptonote_core.cpp:321 Loading blockchain from folder /root/.edollar/lmdb ... 2018-03-06 22:29:57.503 7fc3a7e12880 INFO global src/cryptonote_core/cryptonote_core.cpp:419 Loading checkpoints 2018-03-06 22:29:57.572 7fc3a7e12880 INFO global src/daemon/core.h:79 Core initialized OK 2018-03-06 22:29:57.572 7fc3a7e12880 INFO global src/daemon/rpc.h:69 Starting core rpc server... 2018-03-06 22:29:57.573 [SRV_MAIN] INFO global src/daemon/rpc.h:74 Core rpc server started ok 2018-03-06 22:29:57.574 [SRV_MAIN] INFO global src/daemon/p2p.h:79 Starting p2p net loop... 2018-03-06 22:29:58.575 [P2P1] INFO global src/cryptonote_core/cryptonote_core.cpp:1240

The daemon will start synchronizing with the network. This may take a long time to complete.

You can set the level of process detailization through "set_log <level|categories>" command, where is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING)

Use the "help" command to see the list of available commands.

kbuggenhout commented 6 years ago

fixed in latest github pull