Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Cannot find peers on --chain=classic through tor #4343

Closed
studious3 opened this issue Jan 29, 2017 · 22 comments
Closed

Cannot find peers on --chain=classic through tor #4343

studious3 opened this issue Jan 29, 2017 · 22 comments
Labels
M4-core ⛓ Core client code / Rust. Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known.

Comments

@studious3
Copy link

I have tried both versions 1.4.10 and 1.5 on both debian-8 and whonix. Eth has no problems, it immediately finds peers and works. Classic worked on the older version (prior to 1.4.10), but I got to the hardfork and had to upgrade, ever since, I can't find any peers or download any blocks through tor. Is this a bug?
@studious3
Copy link
Author

actually, I think it's just going really slow, it looks like new .sst files are appearing in the db

@studious3 studious3 reopened this Jan 29, 2017
@studious3
Copy link
Author

I am reopening this because although I am getting new .sst files and it looks like it is getting more and more of the blockchain, the terminal and mist show me having 0 blocks. I switched it to --warp, and am having similar results. I will check back in soon. (again this is just on the classic chain)

@tomusdrw
Copy link
Collaborator

Could you post some logs? How many peers does Parity report?

@tomusdrw tomusdrw added M4-core ⛓ Core client code / Rust. Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known. labels Jan 29, 2017
@studious3
Copy link
Author

How do I upload logs?

@studious3
Copy link
Author

And 000049.sst is as high as it got. It never got any further. I tried --warp as well and that did nothing.

@studious3
Copy link
Author

Parity always reports 0/0/25 peers

@studious3
Copy link
Author

On my version 1.5 node, it only got to 000031.sst
Also 0/0/25 peers for hours and hours.

@studious3
Copy link
Author

It looks like every time are start the classic chain in the terminal it immediately adds a few numbers, for example the next time I started 1.4.10, It went from 000049.sst to 000052.sst. But then it stays at that no matter how long the node is running.

@tomusdrw
Copy link
Collaborator

*.sst files are internal files of RocksDB, they don't map directly to blockchain or anything. You can upload the logs here - attach them to this issue. Collect some logs using --log-file CLI flag or just copy terminal output and paste here.

Please note that running 1.5 and then back 1.4 won't work correctly. 1.5 uses different directory scheme and will not share the blockchain location.

It would be good if you could collect some logs, running Parity like this:

$ parity -lsync=trace --log-file sync.log

It should create sync.log in current working directory and please attach it to this issue.

@tomusdrw tomusdrw changed the title No problem running parity --chain=classic through tor on a version from early December (Don't remember which), got to the hardfork, had to upgrade and now neither 1.4.10 nor 1.5 work for classic through tor Cannot find peers on --chain=classic through tor Jan 30, 2017
@studious3
Copy link
Author

This is from my 1.4.10 instsall:

user@host:~/parity/parity-1.4.10$ ./target/release/parity --chain=classic -lsync=trace --log-file sync.log
2017-01-30 19:56:14 UTC main INFO parity::run Starting Parity/v1.4.10-stable-Could not find the database of available applications, run update-command-not-found as root to fix this-Could not find the database of available applications, run updatecommandnotfound as root to fix this/x86_64-linux-gnu/rustc1.13.0
2017-01-30 19:56:14 UTC main INFO parity::run State DB configuation: fast
2017-01-30 19:56:14 UTC main INFO parity::run Operating mode: active
2017-01-30 19:56:14 UTC main INFO ethcore::service Configured for Ethereum Classic using Ethash engine
2017-01-30 19:56:14 UTC main WARN ethcore::service Your chain is an alternative fork. TRANSACTIONS MAY BE REPLAYED ON THE MAINNET!
2017-01-30 19:56:19 UTC IO Worker #3 INFO network Public node URL: enode://3cd40df24a6bf0266fd23cd23275376666f517a3c4f6b32f2359a8d911d60fd7df7d116fda80d5f3096c339279ba46722913fab1949793a5263e3091027cccdc@10.137.3.6:30303
2017-01-30 19:56:39 UTC IO Worker #2 TRACE sync == Connected 8: 8
2017-01-30 19:56:39 UTC IO Worker #2 TRACE sync Sending status to 8, protocol version 63
2017-01-30 19:56:39 UTC IO Worker #0 TRACE sync == Disconnecting 8: 8
2017-01-30 19:56:44 UTC IO Worker #0 INFO import 0/ 0/25 peers 3 MiB db 7 KiB chain 0 bytes queue 448 bytes sync
2017-01-30 19:56:46 UTC IO Worker #0 TRACE sync == Connected 11: 11
2017-01-30 19:56:46 UTC IO Worker #0 TRACE sync Sending status to 11, protocol version 63
2017-01-30 19:56:46 UTC IO Worker #3 TRACE sync == Disconnecting 11: 11
2017-01-30 19:57:04 UTC IO Worker #0 TRACE sync == Connected 1: 1
2017-01-30 19:57:04 UTC IO Worker #0 TRACE sync Sending status to 1, protocol version 63
2017-01-30 19:57:05 UTC IO Worker #3 TRACE sync == Disconnecting 1: 1
2017-01-30 19:57:14 UTC IO Worker #2 INFO import 0/ 0/25 peers 3 MiB db 7 KiB chain 0 bytes queue 448 bytes sync
2017-01-30 19:57:31 UTC IO Worker #0 TRACE sync == Connected 10: 10
2017-01-30 19:57:31 UTC IO Worker #0 TRACE sync Sending status to 10, protocol version 63
2017-01-30 19:57:32 UTC IO Worker #3 TRACE sync New peer 10 (protocol: 63, network: 1, difficulty: Some(44188670175366988299), latest:492b…a44d, genesis:d4e5…8fa3, snapshot:None)
2017-01-30 19:57:32 UTC IO Worker #3 DEBUG sync Connected 10:10
2017-01-30 19:57:32 UTC IO Worker #3 TRACE sync 10 <- GetForkHeader: at 1920000
2017-01-30 19:57:36 UTC IO Worker #0 TRACE sync Timeout 10
2017-01-30 19:57:36 UTC IO Worker #0 TRACE sync == Disconnecting 10: 10
2017-01-30 19:57:36 UTC IO Worker #0 DEBUG sync Disconnected 10
2017-01-30 19:57:36 UTC IO Worker #0 TRACE sync Syncing with peers: 0 active, 0 confirmed, 0 total
2017-01-30 19:57:36 UTC IO Worker #3 TRACE sync == Disconnecting 10: 10
2017-01-30 19:57:44 UTC IO Worker #3 INFO import 0/ 0/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync
2017-01-30 19:58:14 UTC IO Worker #0 INFO import 0/ 0/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync
2017-01-30 19:58:44 UTC IO Worker #1 INFO import 0/ 0/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync
2017-01-30 19:59:14 UTC IO Worker #2 INFO import 0/ 0/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync
2017-01-30 19:59:44 UTC IO Worker #0 INFO import 0/ 0/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync
2017-01-30 19:59:52 UTC IO Worker #3 TRACE sync == Connected 9: 9
2017-01-30 19:59:52 UTC IO Worker #3 TRACE sync Sending status to 9, protocol version 63
2017-01-30 19:59:53 UTC IO Worker #0 TRACE sync New peer 9 (protocol: 63, network: 1, difficulty: Some(44188670175366988299), latest:492b…a44d, genesis:d4e5…8fa3, snapshot:None)
2017-01-30 19:59:53 UTC IO Worker #0 DEBUG sync Connected 9:9
2017-01-30 19:59:53 UTC IO Worker #0 TRACE sync 9 <- GetForkHeader: at 1920000
2017-01-30 19:59:57 UTC IO Worker #0 TRACE sync Timeout 9
2017-01-30 19:59:57 UTC IO Worker #0 TRACE sync == Disconnecting 9: 9
2017-01-30 19:59:57 UTC IO Worker #0 DEBUG sync Disconnected 9
2017-01-30 19:59:57 UTC IO Worker #0 TRACE sync Syncing with peers: 0 active, 0 confirmed, 0 total
2017-01-30 19:59:57 UTC IO Worker #3 TRACE sync == Disconnecting 9: 9
2017-01-30 20:00:14 UTC IO Worker #3 INFO import 0/ 0/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync
^C2017-01-30 20:00:15 UTC main INFO parity::run Finishing work, please wait...
2017-01-30 20:00:15 UTC main INFO parity

@studious3
Copy link
Author

studious3 commented Jan 30, 2017 •
edited
Loading

This is from the 1.5 install:

user@host:~$ parity -j --chain=classic -lsync=trace --log-file sync.log
Option '--jsonrpc' does nothing. It's on by default
2017-01-30 20:03:22 UTC main INFO parity::run Starting Parity/v1.5.0-beta-d2e6fc0-20170119/x86_64-linux-gnu/rustc1.14.0
2017-01-30 20:03:22 UTC main INFO parity::run State DB configuration: fast
2017-01-30 20:03:22 UTC main INFO parity::run Operating mode: active
2017-01-30 20:03:22 UTC main INFO ethcore::service Configured for Ethereum Classic using Ethash engine
2017-01-30 20:03:24 UTC hyper-client INFO miner Updated conversion rate to Ξ1 = US$10.56 (11273448000 wei/gas)
2017-01-30 20:03:28 UTC IO Worker #2 INFO network Public node URL: enode://d7b74e21a1784d80b188f3a38e60d1a0bd7419303c867d7be3d0042f8db09ebf06c371ef7161f6baea041b643a254a450f38b4aa02001259c913e94e15c39ceb@10.137.3.6:30303
2017-01-30 20:03:36 UTC IO Worker #3 TRACE sync == Connected 9: Geth/v1.4.10-stable-5f55d95a/linux/go1.6.2
2017-01-30 20:03:36 UTC IO Worker #3 TRACE sync Sending status to 9, protocol version 63
2017-01-30 20:03:37 UTC IO Worker #1 TRACE sync New peer 9 (protocol: 63, network: 1, difficulty: Some(44188670175366988299), latest:492b…a44d, genesis:d4e5…8fa3, snapshot:None)
2017-01-30 20:03:37 UTC IO Worker #1 DEBUG sync Connected 9:Geth/v1.4.10-stable-5f55d95a/linux/go1.6.2
2017-01-30 20:03:37 UTC IO Worker #1 TRACE sync 9 <- GetForkHeader: at 1920000
2017-01-30 20:03:42 UTC IO Worker #0 TRACE sync Timeout 9
2017-01-30 20:03:42 UTC IO Worker #0 TRACE sync == Disconnecting 9: Geth/v1.4.10-stable-5f55d95a/linux/go1.6.2
2017-01-30 20:03:42 UTC IO Worker #0 DEBUG sync Disconnected 9
2017-01-30 20:03:42 UTC IO Worker #0 TRACE sync Syncing with peers: 0 active, 0 confirmed, 0 total
2017-01-30 20:03:42 UTC IO Worker #0 TRACE sync == Disconnecting 9: Geth/v1.4.10-stable-5f55d95a/linux/go1.6.2
2017-01-30 20:03:58 UTC IO Worker #2 INFO import 0/ 0/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync
2017-01-30 20:04:28 UTC IO Worker #3 INFO import 0/ 0/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync
2017-01-30 20:04:58 UTC IO Worker #1 INFO import 0/ 0/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync
2017-01-30 20:05:28 UTC IO Worker #0 INFO import 0/ 0/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync
2017-01-30 20:05:58 UTC IO Worker #0 INFO import 0/ 0/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync
2017-01-30 20:05:58 UTC IO Worker #1 TRACE sync == Connected 1: Geth/v1.4.10-stable-5f55d95a/linux/go1.6.2
2017-01-30 20:05:58 UTC IO Worker #1 TRACE sync Sending status to 1, protocol version 63
2017-01-30 20:05:59 UTC IO Worker #3 TRACE sync New peer 1 (protocol: 63, network: 1, difficulty: Some(44188670175366988299), latest:492b…a44d, genesis:d4e5…8fa3, snapshot:None)
2017-01-30 20:05:59 UTC IO Worker #3 DEBUG sync Connected 1:Geth/v1.4.10-stable-5f55d95a/linux/go1.6.2
2017-01-30 20:05:59 UTC IO Worker #3 TRACE sync 1 <- GetForkHeader: at 1920000
2017-01-30 20:06:04 UTC IO Worker #1 TRACE sync Timeout 1
2017-01-30 20:06:04 UTC IO Worker #1 TRACE sync == Disconnecting 1: Geth/v1.4.10-stable-5f55d95a/linux/go1.6.2
2017-01-30 20:06:04 UTC IO Worker #1 DEBUG sync Disconnected 1
2017-01-30 20:06:04 UTC IO Worker #1 TRACE sync Syncing with peers: 0 active, 0 confirmed, 0 total
2017-01-30 20:06:04 UTC IO Worker #2 TRACE sync == Disconnecting 1: Geth/v1.4.10-stable-5f55d95a/linux/go1.6.2
2017-01-30 20:06:28 UTC IO Worker #0 INFO import 0/ 0/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync
2017-01-30 20:06:58 UTC IO Worker #2 INFO import 0/ 0/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync
^C2017-01-30 20:07:19 UTC main INFO parity::run Finishing work, please wait...

@studious3
Copy link
Author

I thought since maybe I built 1.4.10 from source and had to start it with ./target/release/parity, that it wouldn't interefere with the 1.5 install. And that seems to be the case, at least when I am runnin the Eth chain, everything seems to work great.

@studious3
Copy link
Author

Also the reason I installed 1.4.10 is because I am pressed for time. I do not know how to completely remove a program and thought I might run in to more problems trying to remove stuff and doing a fresh install rather than trying to install 1.4.10 in a different way so that it did not interfere.

@studious3
Copy link
Author

Interestingly when I do dpkg --list, I only see one parity install and it says "parity 1.5.0 ...". But when I start parity in the parity-1.4.10 subdirectory, the terminal output even says I am running v1.4.10. Then when I run parity -j the terminal always says its running v1.5.0

@studious3
Copy link
Author

Also I currently I am doing all this on a whonix-ws VM in Qubes. I had the exact same issue in a debian-8 VM in Qubes, where when I upgraded from the early December version (which ever it was) to 1.5, the classic chain did not work.

@tomusdrw
Copy link
Collaborator

Cannot tell anything from the log files, they are way to short, it didn't even connect to a single peer.

Please make sure your time is synchronized and you don't block incoming UDP traffic. Also try waiting a little bit longer, maybe it just needs to discover the peers over slow-ish tor connection.

@studious3
Copy link
Author

So after some research I deduce that 1.4.10 is not showing in dpkg because it was built from source. So I cant't just sudo apt-get --purge remove. What I notice off hand is .local subdirectories for parity and a .parity subdirectory still. I assume the .ethereum and .ethash belong to mist?

How might I go about uninstalling everything that remains so I can try a clean install?

@studious3
Copy link
Author

studious3 commented Jan 30, 2017 •
edited
Loading

I waited for 24 hours before and it did not connect, before.

UDP must be blocked because I am running through tor.

Actually I thought I could only run parity and not geth through tor in particular because tor doesnt run over UDP.

Is this where the problem is? Did parity push the classic chain over UDP after the hardfork?

@gavofyork
Copy link
Contributor

UDP is required for node discovery. looks like all classic bootnodes are down. if you know of running classic nodes, pass their enode URI into --reserved-peers.

needless to say, syncing over tor is going to be excruciatingly slow.

@studious3
Copy link
Author

gavofyork, Can I go to any websites to find a known list of nodes to add them manually? Are there any other ways for me to find the enode URI of other nodes?

@tomusdrw
Copy link
Collaborator

tomusdrw commented Feb 2, 2017

Try eth classic go-ethereum client bootnodes:
https://github.com/ethereumproject/go-ethereum/blob/master/cmd/utils/bootnodes.go#L26

@5chdn 5chdn mentioned this issue Mar 2, 2017
Closed
@elaineo
Copy link

elaineo commented Mar 2, 2017

We will try to keep this list better updated:
ethereumproject/volunteer#20

@5chdn 5chdn mentioned this issue Mar 3, 2017
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
M4-core ⛓ Core client code / Rust. Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@gavofyork @tomusdrw @elaineo @studious3