Last active
August 15, 2018 13:54
-
-
Save veox/028b81306eeb728d6c375c19261635a0 to your computer and use it in GitHub Desktop.
py-evm issue 1168: SUCCESS trinity start
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Starting trinity ethereum node... | |
INFO 08-15 16:50:41 main | |
______ _ _ __ | |
/_ __/____(_)___ (_) /___ __ | |
/ / / ___/ / __ \/ / __/ / / / | |
/ / / / / / / / / / /_/ /_/ / | |
/_/ /_/ /_/_/ /_/_/\__/\__, / | |
/____/ | |
INFO 08-15 16:50:41 main Trinity/eth-0.2.0a31/linux/cpython3.7.0 | |
INFO 08-15 16:50:41 main Trinity DEBUG log file is created at /home/veox/.local/share/trinity/ropsten/logs/trinity.log | |
INFO 08-15 16:50:41 plugin Cleaning up unclean shutdown... | |
INFO 08-15 16:50:41 plugin Searching for process id files in /home/veox/.local/share/trinity/ropsten... | |
INFO 08-15 16:50:41 plugin Found 1 process from a previous run. Closing... | |
INFO 08-15 16:50:41 ipc Process 1602 has already terminated | |
INFO 08-15 16:50:41 plugin Manually removed /home/veox/.local/share/trinity/ropsten/database.pid after killing process id 1602 | |
INFO 08-15 16:50:41 plugin Removed a dangling IPC socket file for database connections at /home/veox/.local/share/trinity/ropsten/db.ipc | |
trinity.service: Found left-over process 1622 (python) in control group while starting unit. Ignoring. | |
This usually indicates unclean termination of a previous run, or service implementation deficiencies. | |
Started trinity ethereum node. | |
INFO 08-15 16:50:42 main | |
______ _ _ __ | |
/_ __/____(_)___ (_) /___ __ | |
/ / / ___/ / __ \/ / __/ / / / | |
/ / / / / / / / / / /_/ /_/ / | |
/_/ /_/ /_/_/ /_/_/\__/\__, / | |
/____/ | |
INFO 08-15 16:50:42 main Trinity/eth-0.2.0a31/linux/cpython3.7.0 | |
INFO 08-15 16:50:42 main Trinity DEBUG log file is created at /home/veox/.local/share/trinity/ropsten/logs/trinity.log | |
INFO 08-15 16:50:42 main Started DB server process (pid=1629) | |
INFO 08-15 16:50:43 main Started networking process (pid=1631) | |
INFO 08-15 16:50:44 server Running server... | |
INFO 08-15 16:50:44 nat Setting up NAT portmap... | |
INFO 08-15 16:50:44 ipc IPC started at: /home/veox/.local/share/trinity/ropsten/jsonrpc.ipc | |
INFO 08-15 16:50:49 nat No UPNP-enabled devices found | |
INFO 08-15 16:50:49 server enode://1d0a016bce90c759e8894f93a23fa55f2054ff4c4678924c2ca15eadff6e1c58e5de6729aa33ada69da2b7e494dee20bfcde519f86def427baf947f5aaa09a99@0.0.0.0:30303 | |
INFO 08-15 16:50:49 server network: 3 | |
INFO 08-15 16:50:49 server peers: max_peers=25 | |
INFO 08-15 16:50:49 discovery Preferred peers: (<Node(0x053d2f57829e5785d10697fa6c5333e4d98cc564dbadd87805fd4fedeb09cbcb642306e3a73bd4191b27f821fb442fcf964317d6a520b29651e7dd09d1beb0ec@79.98.29.154:30303)>, <Node(0x94c15d1b9e2fe7c> | |
INFO 08-15 16:50:49 peer Connected peers: 0 inbound, 0 outbound | |
INFO 08-15 16:50:49 discovery boostrapping with (<Node(0x30b7ab30a01c124a6cceca36863ece12c4f5fa68e3ba9b0b51407ccc002eeed3b3102d20a88f1c1d3c3154e2449317b8ef95090e77b312d5cc39354f86d5d606@52.176.7.10:30303)>, <Node(0x865a63255b3bb68> | |
INFO 08-15 16:50:49 service Starting fast-sync; current head: #1577264 | |
INFO 08-15 16:50:49 peer Adding ETHPeer <Node(0x053d@79.98.29.154)> to pool | |
INFO 08-15 16:50:49 chain Starting sync with ETHPeer <Node(0x053d@79.98.29.154)> | |
... |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
INFO 08-15 16:50:41 main | |
______ _ _ __ | |
/_ __/____(_)___ (_) /___ __ | |
/ / / ___/ / __ \/ / __/ / / / | |
/ / / / / / / / / / /_/ /_/ / | |
/_/ /_/ /_/_/ /_/_/\__/\__, / | |
/____/ | |
INFO 08-15 16:50:41 main Trinity/eth-0.2.0a31/linux/cpython3.7.0 | |
INFO 08-15 16:50:41 main Trinity DEBUG log file is created at /home/veox/.local/share/trinity/ropsten/logs/trinity.log | |
INFO 08-15 16:50:41 plugin Cleaning up unclean shutdown... | |
INFO 08-15 16:50:41 plugin Searching for process id files in /home/veox/.local/share/trinity/ropsten... | |
INFO 08-15 16:50:41 plugin Found 1 process from a previous run. Closing... | |
INFO 08-15 16:50:41 ipc Process 1602 has already terminated | |
INFO 08-15 16:50:41 plugin Manually removed /home/veox/.local/share/trinity/ropsten/database.pid after killing process id 1602 | |
INFO 08-15 16:50:41 plugin Removed a dangling IPC socket file for database connections at /home/veox/.local/share/trinity/ropsten/db.ipc | |
DEBUG 08-15 16:50:41 plugin The IPC socket file for JSON-RPC connections at /home/veox/.local/share/trinity/ropsten/jsonrpc.ipc was already gone | |
INFO 08-15 16:50:42 main | |
______ _ _ __ | |
/_ __/____(_)___ (_) /___ __ | |
/ / / ___/ / __ \/ / __/ / / / | |
/ / / / / / / / / / /_/ /_/ / | |
/_/ /_/ /_/_/ /_/_/\__/\__, / | |
/____/ | |
INFO 08-15 16:50:42 main Trinity/eth-0.2.0a31/linux/cpython3.7.0 | |
INFO 08-15 16:50:42 main Trinity DEBUG log file is created at /home/veox/.local/share/trinity/ropsten/logs/trinity.log | |
INFO 08-15 16:50:42 main Started DB server process (pid=1629) | |
DEBUG 08-15 16:50:43 logging Logging initialized: PID=1629 | |
INFO 08-15 16:50:43 main Started networking process (pid=1631) | |
DEBUG 08-15 16:50:44 logging Logging initialized: PID=1631 | |
DEBUG 08-15 16:50:44 selector_events Using selector: EpollSelector | |
DEBUG 08-15 16:50:44 selector_events Using selector: EpollSelector | |
INFO 08-15 16:50:44 server Running server... | |
INFO 08-15 16:50:44 nat Setting up NAT portmap... | |
INFO 08-15 16:50:44 ipc IPC started at: /home/veox/.local/share/trinity/ropsten/jsonrpc.ipc | |
INFO 08-15 16:50:49 nat No UPNP-enabled devices found | |
INFO 08-15 16:50:49 server enode://1d0a016bce90c759e8894f93a23fa55f2054ff4c4678924c2ca15eadff6e1c58e5de6729aa33ada69da2b7e494dee20bfcde519f86def427baf947f5aaa09a99@0.0.0.0:30303 | |
INFO 08-15 16:50:49 server network: 3 | |
INFO 08-15 16:50:49 server peers: max_peers=25 | |
INFO 08-15 16:50:49 discovery Preferred peers: (<Node(0x053d2f57829e5785d10697fa6c5333e4d98cc564dbadd87805fd4fedeb09cbcb642306e3a73bd4191b27f821fb442fcf964317d6a520b29651e7dd09d1beb0ec@79.98.29.154:30303)>, <Node(0x94c15d1b9e2fe7c) | |
INFO 08-15 16:50:49 peer Connected peers: 0 inbound, 0 outbound | |
DEBUG 08-15 16:50:49 peer == Peer details == | |
DEBUG 08-15 16:50:49 peer == End peer details == | |
INFO 08-15 16:50:49 discovery boostrapping with (<Node(0x30b7ab30a01c124a6cceca36863ece12c4f5fa68e3ba9b0b51407ccc002eeed3b3102d20a88f1c1d3c3154e2449317b8ef95090e77b312d5cc39354f86d5d606@52.176.7.10:30303)>, <Node(0x865a63255b3bb68) | |
INFO 08-15 16:50:49 service Starting fast-sync; current head: #1577264 | |
DEBUG 08-15 16:50:49 peer Finished P2P handshake with <Node(0x053d@79.98.29.154)>, using sub-protocol (eth, 63) | |
DEBUG 08-15 16:50:49 proto Sending ETH/Status msg: {'protocol_version': 63, 'network_id': 3, 'td': 1697451851292791, 'best_hash': b'#\x150\xba\x1a\xad\x0f\xe8\x92m\xe9*\x1d\xaf`\r\x97\t\x8d,!W\x96T!L;\x91`\xaaf\x87', 'genesis_h} | |
DEBUG 08-15 16:50:49 peer Finished (eth, 63) handshake with <Node(0x053d@79.98.29.154)> | |
INFO 08-15 16:50:49 peer Adding ETHPeer <Node(0x053d@79.98.29.154)> to pool | |
INFO 08-15 16:50:49 chain Starting sync with ETHPeer <Node(0x053d@79.98.29.154)> | |
DEBUG 08-15 16:50:49 chain Fetching chain segment starting at #1577240 | |
DEBUG 08-15 16:50:49 managers Launching GetBlockBodiesRequestManager for peer ETHPeer <Node(0x053d@79.98.29.154)> | |
DEBUG 08-15 16:50:49 managers Launching GetBlockHeadersRequestManager for peer ETHPeer <Node(0x053d@79.98.29.154)> | |
DEBUG 08-15 16:50:49 managers Launching GetNodeDataRequestManager for peer ETHPeer <Node(0x053d@79.98.29.154)> | |
DEBUG 08-15 16:50:49 managers Launching GetReceiptsRequestManager for peer ETHPeer <Node(0x053d@79.98.29.154)> | |
DEBUG 08-15 16:50:49 chain Discarding header that we already have: <BlockHeader #1577240 c860b758> | |
... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment