Opened 6 months ago

Closed 13 days ago

#27783 closed defect (duplicate)

Chutney: Authorities are getting created but relays are not getting configured!

Reported by: teor Owned by: teor
Priority: Medium Milestone:
Component: Core Tor/Chutney Version:
Severity: Normal Keywords:
Cc: teor Actual Points:
Parent ID: #27784 Points:
Reviewer: Sponsor:

Description

Moved from https://github.com/torproject/chutney/commit/c889534dd5ae6620634720a4fa7a771be9858069#commitcomment-30558908

Hi, i am getting the following error, when i tried to configure chutney !
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
Authorities are getting created but relays are not getting configured!
What configurations and where i am missing? I am installing on a Ubuntu machine.
Please see the log below:

Using Python 2.7.12
NOTE: creating '/home/aakanksha/chutney/net/nodes.1537341356', linking to '/home/aakanksha/chutney/net/nodes'
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
(many times)
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
Creating identity key /home/aakanksha/chutney/net/nodes/000a/keys/authority_identity_key for test000a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/aakanksha/chutney/net/nodes/000a/keys/authority_identity_key -s /home/aakanksha/chutney/net/nodes/000a/keys/authority_signing_key -c /home/aakanksha/chutney/net/nodes/000a/keys/authority_certificate -m 12 -a 10.0.0.1:7000
Creating identity key /home/aakanksha/chutney/net/nodes/001a/keys/authority_identity_key for test001a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/aakanksha/chutney/net/nodes/001a/keys/authority_identity_key -s /home/aakanksha/chutney/net/nodes/001a/keys/authority_signing_key -c /home/aakanksha/chutney/net/nodes/001a/keys/authority_certificate -m 12 -a 10.2.0.0:7001
Creating identity key /home/aakanksha/chutney/net/nodes/002a/keys/authority_identity_key for test002a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/aakanksha/chutney/net/nodes/002a/keys/authority_identity_key -s /home/aakanksha/chutney/net/nodes/002a/keys/authority_signing_key -c /home/aakanksha/chutney/net/nodes/002a/keys/authority_certificate -m 12 -a 10.4.0.0:7002
Creating identity key /home/aakanksha/chutney/net/nodes/003a/keys/authority_identity_key for test003a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/aakanksha/chutney/net/nodes/003a/keys/authority_identity_key -s /home/aakanksha/chutney/net/nodes/003a/keys/authority_signing_key -c /home/aakanksha/chutney/net/nodes/003a/keys/authority_certificate -m 12 -a 10.6.0.0:7003
Creating identity key /home/aakanksha/chutney/net/nodes/004a/keys/authority_identity_key for test004a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/aakanksha/chutney/net/nodes/004a/keys/authority_identity_key -s /home/aakanksha/chutney/net/nodes/004a/keys/authority_signing_key -c /home/aakanksha/chutney/net/nodes/004a/keys/authority_certificate -m 12 -a 10.8.0.0:7004
Creating identity key /home/aakanksha/chutney/net/nodes/005a/keys/authority_identity_key for test005a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/aakanksha/chutney/net/nodes/005a/keys/authority_identity_key -s /home/aakanksha/chutney/net/nodes/005a/keys/authority_signing_key -c /home/aakanksha/chutney/net/nodes/005a/keys/authority_certificate -m 12 -a 10.10.0.0:7005
Creating identity key /home/aakanksha/chutney/net/nodes/006a/keys/authority_identity_key for test006a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/aakanksha/chutney/net/nodes/006a/keys/authority_identity_key -s /home/aakanksha/chutney/net/nodes/006a/keys/authority_signing_key -c /home/aakanksha/chutney/net/nodes/006a/keys/authority_certificate -m 12 -a 10.12.0.0:7006
Creating identity key /home/aakanksha/chutney/net/nodes/007a/keys/authority_identity_key for test007a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/aakanksha/chutney/net/nodes/007a/keys/authority_identity_key -s /home/aakanksha/chutney/net/nodes/007a/keys/authority_signing_key -c /home/aakanksha/chutney/net/nodes/007a/keys/authority_certificate -m 12 -a 10.14.0.0:7007
Creating identity key /home/aakanksha/chutney/net/nodes/008a/keys/authority_identity_key for test008a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/aakanksha/chutney/net/nodes/008a/keys/authority_identity_key -s /home/aakanksha/chutney/net/nodes/008a/keys/authority_signing_key -c /home/aakanksha/chutney/net/nodes/008a/keys/authority_certificate -m 12 -a 10.16.0.0:7008
Creating identity key /home/aakanksha/chutney/net/nodes/009a/keys/authority_identity_key for test009a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/aakanksha/chutney/net/nodes/009a/keys/authority_identity_key -s /home/aakanksha/chutney/net/nodes/009a/keys/authority_signing_key -c /home/aakanksha/chutney/net/nodes/009a/keys/authority_certificate -m 12 -a 10.18.0.0:7009
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
(many times)
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.

Child Tickets

Attachments (1)

nodes.1537874080.rar (317.9 KB) - added by sreenivassadhu@… 6 months ago.
Log with 15 nodes of chutney config

Download all attachments as: .zip

Change History (10)

comment:1 Changed 6 months ago by teor

Thanks for this bug report.

What command are you running?

Does the command return after the last output, or does it hang?

comment:2 Changed 6 months ago by sreenivassadhu@…

(What command are you running?)

I am running the following command:

./chutney configure /path/to/experiment

/path/to/experiment is my file (new_experiment) consisting of the Tor configuration files like below:

# By default, Authorities are not configured as exits
Authority = Node(tag="a", authority=1, relay=1, torrc="authority.tmpl")
ExitRelay = Node(tag="r", relay=1, exit=1, torrc="relay.tmpl")
Client = Node(tag="c", torrc="client.tmpl")

# We need 8 authorities/relays/exits to ensure at least 2 get the guard flag
# in 0.2.6
NODES = Authority.getN(10) + ExitRelay.getN(50) + Client.getN(100)

# Omit if you extracted the scripts to the PYTHONPATH
import sys
sys.path.append('/path/to/netmirage_tor')

import netmirage_tor
netmirage_tor.Assign(NODES, '/path/to/ip_addresses.txt')

ConfigureNodes(NODES)

(Does the command return after the last output, or does it hang?)
Yes! It returns after the last output.

The last out is as follows:
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
*
what configuration else is required in resolv.conf file? other than provided in the Chutney!?

comment:3 Changed 6 months ago by teor

what configuration else is required in resolv.conf file? other than provided in the Chutney!?

I don't think there is anything wrong with your resolv.conf file. That message is for your information. It is not an error or a warning.

When you configure chutney, all the keys are created, and then the script exits successfully.

NODES = Authority.getN(10) + ExitRelay.getN(50) + Client.getN(100)

To run 160 nodes, you will need at least 2*160*160 = 51200 file descriptors on your machine, 10s of gigabytes of RAM, and tens or hundreds of CPU cores.

Depending on your machine, you might be able to run 10 or 20 nodes using chutney.

If you need to run a network with hundreds of tor instances, try shadow at https://shadow.github.io

comment:4 Changed 6 months ago by sreenivassadhu@…

Thanks for the response!

(I don't think there is anything wrong with your resolv.conf file. That message is for your information. It is not an error or a warning.)

Because of this, relays are not getting configured! Authorities and nodes are getting created! Relay DNS is the local host and its mentioned in resolve.conf file.
Why its using '/etc/resolv.conf' file? We have got resolve.conf in Chutney itself!

I will try with minimal nos i.e 2,5,8 respectively!

Pls help

Changed 6 months ago by sreenivassadhu@…

Attachment: nodes.1537874080.rar added

Log with 15 nodes of chutney config

comment:5 Changed 6 months ago by sreenivassadhu@…

Hi, i tried with 2,5,8 respectively! (total 15 nodes)

This time also i am getting the transmission failure problem.

Where i am going wrong!?

Pls help!

Attached log above with 15 nodes!

aakanksha@aakanksha-HP-Z238-Microtower-Workstation:~/chutney$ sudo ./chutney configure /home/aakanksha/new_exp1
[sudo] password for aakanksha:
Using Python 2.7.12
NOTE: creating '/home/aakanksha/chutney/net/nodes.1537874080', linking to '/home/aakanksha/chutney/net/nodes'
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
Creating identity key /home/aakanksha/chutney/net/nodes/000a/keys/authority_identity_key for test000a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/aakanksha/chutney/net/nodes/000a/keys/authority_identity_key -s /home/aakanksha/chutney/net/nodes/000a/keys/authority_signing_key -c /home/aakanksha/chutney/net/nodes/000a/keys/authority_certificate -m 12 -a 10.0.0.1:7000
Creating identity key /home/aakanksha/chutney/net/nodes/001a/keys/authority_identity_key for test001a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/aakanksha/chutney/net/nodes/001a/keys/authority_identity_key -s /home/aakanksha/chutney/net/nodes/001a/keys/authority_signing_key -c /home/aakanksha/chutney/net/nodes/001a/keys/authority_certificate -m 12 -a 10.2.0.0:7001
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
CHUTNEY_DNS_CONF not specified, using '/etc/resolv.conf'.
aakanksha@aakanksha-HP-Z238-Microtower-Workstation:~/chutney$ sudo ./chutney start /home/aakanksha/new_exp1
Using Python 2.7.12
Starting nodes
Couldn't launch test000a (tor -f /home/aakanksha/chutney/net/nodes/000a/torrc --quiet): 1
Couldn't launch test001a (tor -f /home/aakanksha/chutney/net/nodes/001a/torrc --quiet): 1
Couldn't launch test004r (tor -f /home/aakanksha/chutney/net/nodes/004r/torrc --quiet): 1
Couldn't launch test005r (tor -f /home/aakanksha/chutney/net/nodes/005r/torrc --quiet): 1
Couldn't launch test006r (tor -f /home/aakanksha/chutney/net/nodes/006r/torrc --quiet): 1
Couldn't launch test007c (tor -f /home/aakanksha/chutney/net/nodes/007c/torrc --quiet): 1
Couldn't launch test008c (tor -f /home/aakanksha/chutney/net/nodes/008c/torrc --quiet): 1
Couldn't launch test009c (tor -f /home/aakanksha/chutney/net/nodes/009c/torrc --quiet): 1
Couldn't launch test010c (tor -f /home/aakanksha/chutney/net/nodes/010c/torrc --quiet): 1
Couldn't launch test011c (tor -f /home/aakanksha/chutney/net/nodes/011c/torrc --quiet): 1
Couldn't launch test012c (tor -f /home/aakanksha/chutney/net/nodes/012c/torrc --quiet): 1
Couldn't launch test013c (tor -f /home/aakanksha/chutney/net/nodes/013c/torrc --quiet): 1
Couldn't launch test014c (tor -f /home/aakanksha/chutney/net/nodes/014c/torrc --quiet): 1

aakanksha@aakanksha-HP-Z238-Microtower-Workstation:~/chutney$ sudo ./chutney verify /home/aakanksha/new_exp1
Using Python 2.7.12
Verifying data transmission: (retrying for up to 60 seconds)
Connecting:

Exit to 127.0.0.1:4747 via client localhost:9007
Exit to 127.0.0.1:4747 via client localhost:9008
Exit to 127.0.0.1:4747 via client localhost:9009
Exit to 127.0.0.1:4747 via client localhost:9010
Exit to 127.0.0.1:4747 via client localhost:9011
Exit to 127.0.0.1:4747 via client localhost:9012
Exit to 127.0.0.1:4747 via client localhost:9013
Exit to 127.0.0.1:4747 via client localhost:9014

Transmitting Data:

Connecting:

Exit to 127.0.0.1:4747 via client localhost:9007
Exit to 127.0.0.1:4747 via client localhost:9008
Exit to 127.0.0.1:4747 via client localhost:9009
Exit to 127.0.0.1:4747 via client localhost:9010
Exit to 127.0.0.1:4747 via client localhost:9011
Exit to 127.0.0.1:4747 via client localhost:9012
Exit to 127.0.0.1:4747 via client localhost:9013
Exit to 127.0.0.1:4747 via client localhost:9014

Transmitting Data:

[[B[[B[[B[[B[[B[[B[[B[[B[[B[[B[[B[[B[[B[[B[[B[[Connecting:

Exit to 127.0.0.1:4747 via client localhost:9007
Exit to 127.0.0.1:4747 via client localhost:9008
Exit to 127.0.0.1:4747 via client localhost:9009
Exit to 127.0.0.1:4747 via client localhost:9010
Exit to 127.0.0.1:4747 via client localhost:9011
Exit to 127.0.0.1:4747 via client localhost:9012
Exit to 127.0.0.1:4747 via client localhost:9013
Exit to 127.0.0.1:4747 via client localhost:9014

Transmitting Data:

Connecting:

Exit to 127.0.0.1:4747 via client localhost:9007
Exit to 127.0.0.1:4747 via client localhost:9008
Exit to 127.0.0.1:4747 via client localhost:9009
Exit to 127.0.0.1:4747 via client localhost:9010
Exit to 127.0.0.1:4747 via client localhost:9011
Exit to 127.0.0.1:4747 via client localhost:9012
Exit to 127.0.0.1:4747 via client localhost:9013
Exit to 127.0.0.1:4747 via client localhost:9014

Transmitting Data:

Connecting:

Exit to 127.0.0.1:4747 via client localhost:9007
Exit to 127.0.0.1:4747 via client localhost:9008
Exit to 127.0.0.1:4747 via client localhost:9009
Exit to 127.0.0.1:4747 via client localhost:9010
Exit to 127.0.0.1:4747 via client localhost:9011
Exit to 127.0.0.1:4747 via client localhost:9012
Exit to 127.0.0.1:4747 via client localhost:9013
Exit to 127.0.0.1:4747 via client localhost:9014

Transmitting Data:
verification failed!

Connecting:

Exit to 127.0.0.1:4747 via client localhost:9007
Exit to 127.0.0.1:4747 via client localhost:9008
Exit to 127.0.0.1:4747 via client localhost:9009
Exit to 127.0.0.1:4747 via client localhost:9010
Exit to 127.0.0.1:4747 via client localhost:9011
Exit to 127.0.0.1:4747 via client localhost:9012
Exit to 127.0.0.1:4747 via client localhost:9013
Exit to 127.0.0.1:4747 via client localhost:9014

Transmitting Data:

Connecting:

Exit to 127.0.0.1:4747 via client localhost:9007
Exit to 127.0.0.1:4747 via client localhost:9008
Exit to 127.0.0.1:4747 via client localhost:9009
Exit to 127.0.0.1:4747 via client localhost:9010
Exit to 127.0.0.1:4747 via client localhost:9011
Exit to 127.0.0.1:4747 via client localhost:9012
Exit to 127.0.0.1:4747 via client localhost:9013
Exit to 127.0.0.1:4747 via client localhost:9014

Transmitting Data:

Connecting:

Exit to 127.0.0.1:4747 via client localhost:9007
Exit to 127.0.0.1:4747 via client localhost:9008
Exit to 127.0.0.1:4747 via client localhost:9009
Exit to 127.0.0.1:4747 via client localhost:9010
Exit to 127.0.0.1:4747 via client localhost:9011
Exit to 127.0.0.1:4747 via client localhost:9012
Exit to 127.0.0.1:4747 via client localhost:9013
Exit to 127.0.0.1:4747 via client localhost:9014

Transmitting Data:

Transmission: Failure
Set CHUTNEY_DEBUG to diagnose.

comment:6 Changed 6 months ago by teor

Hi, I'm sorry I can't help much for the next two weeks. I am at the Tor meeting in Mexico City.

Transmission: Failure
Set CHUTNEY_DEBUG to diagnose.

Please set the CHUTNEY_DEBUG environmental variable to 1, and post the logs.

Please also try reading the notice.log for each tor instance. Most problems show up in that log.

comment:7 Changed 13 days ago by teor

Resolution: user disappeared
Status: assignedclosed

I am sorry that I ran out of time to help you with these issues.

comment:8 Changed 13 days ago by teor

Resolution: user disappeared
Status: closedreopened

comment:9 Changed 13 days ago by teor

Parent ID: #27784
Resolution: duplicate
Status: reopenedclosed
Note: See TracTickets for help on using tickets.