Opened 3 years ago

Closed 3 years ago

#18404 closed defect (fixed)

"make test-network" failed for test010bc

Reported by: toralf Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version: Tor: 0.2.8.1-alpha
Severity: Minor Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

~/devel/tor $ make test-network        
make  all-am
make[1]: Entering directory '/home/tfoerste/devel/tor'
make[1]: Leaving directory '/home/tfoerste/devel/tor'
./src/test/test-network.sh --hs-multi-client 1
Using Python 2.7.10
Sending SIGINT to nodes
Waiting for nodes to finish.
Removing stale lock file for test000a ...
Removing stale lock file for test001a ...
Removing stale lock file for test002a ...
Removing stale lock file for test003ba ...
Removing stale lock file for test004r ...
Removing stale lock file for test005r ...
Removing stale lock file for test006r ...
Removing stale lock file for test007r ...
Removing stale lock file for test008br ...
Removing stale lock file for test009c ...
Removing stale lock file for test011h ...
bootstrap-network.sh: boostrapping network: bridges+hs
Using Python 2.7.10
NOTE: renaming '/home/tfoerste/devel/chutney/net/nodes' to '/home/tfoerste/devel/chutney/net/nodes.1456675056'
Creating identity key /home/tfoerste/devel/chutney/net/nodes/000a/keys/authority_identity_key for test000a with /home/tfoerste/devel/tor/src/tools/tor-gencert --create-identity-key --passphrase-fd 0 -i /home/tfoerste/devel/chutney/net/nodes/000a/keys/authority_identity_key -s /home/tfoerste/devel/chutney/net/nodes/000a/keys/authority_signing_key -c /home/tfoerste/devel/chutney/net/nodes/000a/keys/authority_certificate -m 12 -a 127.0.0.1:7000
Creating identity key /home/tfoerste/devel/chutney/net/nodes/001a/keys/authority_identity_key for test001a with /home/tfoerste/devel/tor/src/tools/tor-gencert --create-identity-key --passphrase-fd 0 -i /home/tfoerste/devel/chutney/net/nodes/001a/keys/authority_identity_key -s /home/tfoerste/devel/chutney/net/nodes/001a/keys/authority_signing_key -c /home/tfoerste/devel/chutney/net/nodes/001a/keys/authority_certificate -m 12 -a 127.0.0.1:7001
Creating identity key /home/tfoerste/devel/chutney/net/nodes/002a/keys/authority_identity_key for test002a with /home/tfoerste/devel/tor/src/tools/tor-gencert --create-identity-key --passphrase-fd 0 -i /home/tfoerste/devel/chutney/net/nodes/002a/keys/authority_identity_key -s /home/tfoerste/devel/chutney/net/nodes/002a/keys/authority_signing_key -c /home/tfoerste/devel/chutney/net/nodes/002a/keys/authority_certificate -m 12 -a 127.0.0.1:7002
Creating identity key /home/tfoerste/devel/chutney/net/nodes/003ba/keys/authority_identity_key for test003ba with /home/tfoerste/devel/tor/src/tools/tor-gencert --create-identity-key --passphrase-fd 0 -i /home/tfoerste/devel/chutney/net/nodes/003ba/keys/authority_identity_key -s /home/tfoerste/devel/chutney/net/nodes/003ba/keys/authority_signing_key -c /home/tfoerste/devel/chutney/net/nodes/003ba/keys/authority_certificate -m 12 -a 127.0.0.1:7003
Using Python 2.7.10
Starting nodes
Couldn't launch test010bc (/home/tfoerste/devel/tor/src/or/tor --quiet -f /home/tfoerste/devel/chutney/net/nodes/010bc/torrc): 1

Using Python 2.7.10
test000a is running with PID 25161
test001a is running with PID 25164
test002a is running with PID 25167
test003ba is running with PID 25174
test004r is running with PID 25177
test005r is running with PID 25192
test006r is running with PID 25199
test007r is running with PID 25202
test008br is running with PID 25209
test009c is running with PID 25216
test011h is running with PID 25226
11/12 nodes are running
Makefile:7238: recipe for target 'test-network' failed
make: *** [test-network] Error 2

Child Tickets

Change History (5)

comment:1 Changed 3 years ago by nickm

Any information on why that node isn't starting? If you try running the command to launch it manually, without the --quiet part, what happens?

comment:2 Changed 3 years ago by nickm

Status: newneeds_information

Any information on why that node isn't starting? If you try running the command to launch it manually, without the --quiet part, what happens?

comment:3 Changed 3 years ago by toralf

Hhm, it is the only one torrc with "UseBridges 1".

 $ /home/tfoerste/devel/tor/src/or/tor -f /home/tfoerste/devel/chutney/net/nodes/010bc/torrc
Feb 28 18:25:27.128 [notice] Tor v0.2.8.1-alpha-dev (git-69fc025e956f5a87) running on Linux with Libevent 2.0.22-stable, OpenSSL 1.0.2f and Zlib 1.2.8.
Feb 28 18:25:27.128 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Feb 28 18:25:27.128 [notice] This version is not a stable Tor release. Expect more bugs than usual.
Feb 28 18:25:27.128 [notice] Read configuration file "/home/tfoerste/devel/chutney/net/nodes/010bc/torrc".
Feb 28 18:25:27.134 [warn] You have used DirAuthority or AlternateDirAuthority to specify alternate directory authorities in your configuration. This is potentially dangerous: it can make you look different from all other Tor users, and hurt your anonymity. Even if you've specified the same authorities as Tor uses by default, the defaults could change in the future. Be sure you know what you're doing.
Feb 28 18:25:27.134 [warn] The DirAuthority options 'hs' and 'no-hs' are obsolete; you don't need them any more.
Feb 28 18:25:27.134 [warn] The DirAuthority options 'hs' and 'no-hs' are obsolete; you don't need them any more.
Feb 28 18:25:27.134 [warn] The DirAuthority options 'hs' and 'no-hs' are obsolete; you don't need them any more.
Feb 28 18:25:27.134 [warn] TestingTorNetwork is set. This will make your node almost unusable in the public Tor network, and is therefore only advised if you are building a testing Tor network!
Feb 28 18:25:27.135 [notice] Opening Socks listener on 127.0.0.1:9010
Feb 28 18:25:27.135 [notice] Opening Control listener on 127.0.0.1:8010
Feb 28 18:25:27.135 [warn] Could not bind to 127.0.0.1:8010: Address already in use. Is Tor already running?
Feb 28 18:25:27.135 [notice] Closing partially-constructed Socks listener on 127.0.0.1:9010
Feb 28 18:25:27.135 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Feb 28 18:25:27.135 [err] Reading config failed--see warnings above.

FWIW "netstat --tcp --udp --program -W | grep 8010" is empty

Last edited 3 years ago by toralf (previous) (diff)

comment:4 Changed 3 years ago by toralf

one of the last commits solved this now in tor-0.2.8.1-alpha-292-g65db5ae

comment:5 Changed 3 years ago by toralf

Resolution: fixed
Status: needs_informationclosed
Note: See TracTickets for help on using tickets.