Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #24453

Closed (moved)
Open
Opened Nov 28, 2017 by cypherpunks@cypherpunks

Reduce log spam when child process creation failed

One ERR instead of a lot of WARN would be enough.

Tor WARN: Failed to create child process TorBrowser\Tor\PluggableTransports\obfs4proxy: The process creation has been blocked.   
Tor WARN: Managed proxy at 'TorBrowser\Tor\PluggableTransports\obfs4proxy' failed at launch. 
Tor NOTICE: Switching to guard context "bridges" (was using "default") 
Tor WARN: Failed to create child process TorBrowser\Tor\PluggableTransports\obfs4proxy: The process creation has been blocked.   
Tor WARN: Managed proxy at 'TorBrowser\Tor\PluggableTransports\obfs4proxy' failed at launch. 
Tor WARN: Failed to create child process TorBrowser\Tor\PluggableTransports\obfs4proxy: The process creation has been blocked.   
Tor WARN: Managed proxy at 'TorBrowser\Tor\PluggableTransports\obfs4proxy' failed at launch. 
Tor WARN: Failed to create child process TorBrowser\Tor\PluggableTransports\obfs4proxy: The process creation has been blocked.   
Tor WARN: Managed proxy at 'TorBrowser\Tor\PluggableTransports\obfs4proxy' failed at launch. 
Tor NOTICE: Delaying directory fetches: No running bridges 
Tor WARN: We were supposed to connect to bridge '85.17.30.79:443' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '[2001:470:b381:bfff:216:3eff:fe23:d6c3]:443' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '154.35.22.10:15937' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '109.105.109.147:13764' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '154.35.22.12:80' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '154.35.22.9:12166' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '85.31.186.26:443' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '109.105.109.165:10527' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '154.35.22.9:443' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '154.35.22.13:16815' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '38.229.1.78:80' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '37.218.245.14:38224' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '154.35.22.10:80' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '192.99.11.54:443' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '154.35.22.13:443' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '38.229.33.83:80' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '154.35.22.10:443' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '154.35.22.12:4304' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '154.35.22.9:80' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '154.35.22.11:80' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '154.35.22.11:443' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '154.35.22.11:16488' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '37.218.240.34:40035' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '85.31.186.98:443' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '192.95.36.142:443' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 
Tor WARN: We were supposed to connect to bridge '83.212.101.3:50002' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#24453