Opened 4 months ago

Last modified 2 weeks ago

#27517 needs_information defect

./run_nyx shows stem's debug output

Reported by: traumschule Owned by: atagar
Priority: Medium Milestone:
Component: Core Tor/Nyx Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I did not find out why I see stem's debug output with ./run_nyx from a fresh clone:

nyx_fresh$ ./run_nyx -d nyx.log
TRACE:stem:Nyx 2.0.4-dev Debug Dump
Stem Version: 1.6.0
Python Version: 2.7.15
Platform: Linux (debian buster/sid )
--------------------------------------------------------------------------------
Nyx Configuration (/home/user/.nyx/config):
[file doesn't exist]
--------------------------------------------------------------------------------
Saving a debug log to nyx.log, please check it for sensitive information before sharing it.
NOTICE:stem:No nyxrc loaded, using defaults. You can customize nyx by placing a configuration file at /home/user/.nyx/config (see https://nyx.torproject.org/nyxrc.sample for its options).
TRACE:stem:config entry 'tor_chroot' not found, defaulting to ''
TRACE:stem:Sent to tor: PROTOCOLINFO 1
TRACE:stem:Received from tor:
250-PROTOCOLINFO 1
250-AUTH METHODS=COOKIE,SAFECOOKIE,HASHEDPASSWORD COOKIEFILE="/var/run/tor/control.authcookie"
250-VERSION Tor="0.3.5.0-alpha-dev"
250 OK
Tor controller password:

(follow-up of #27350)

Child Tickets

Change History (1)

comment:1 Changed 2 weeks ago by atagar

Status: new → needs_information

Hi traumschule, sorry about letting this languish so long! Back on #27350 this pretty thoroughly confused me and I gotta admit, I'm still puzzled. I've tried a few different things to reproduce this but no luck.

Per chance have you modified Stem or Nyx at all? This certainly looks like we've called Stem's log_to_stdout() helper but that's never done within Nyx.

If you're certain Stem and Nyx are unmodified please double check that this issue reproduces with the latest git commits of Stem and Nyx, and provide your torrc and I'll try again with that.

Note: See TracTickets for help on using tickets.