Opened 16 months ago

Last modified 2 months ago

#24453 new defect

Reduce log spam when child process creation failed

Reported by: cypherpunks Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: bootstrap, 033-triage-20180320, 033-removed-20180320
Cc: catalyst Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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.

Child Tickets

Change History (5)

comment:1 Changed 14 months ago by catalyst

Cc: catalyst added
Keywords: bootstrap s8-errors added
Sponsor: Sponsor8-can

comment:2 Changed 12 months ago by nickm

Keywords: 033-triage-20180320 added

Marking all tickets reached by current round of 033 triage.

comment:3 Changed 12 months ago by nickm

Keywords: 033-removed-20180320 added

Mark all not-already-included tickets as pending review for removal from 0.3.3 milestone.

comment:4 Changed 12 months ago by nickm

Milestone: Tor: 0.3.3.x-finalTor: unspecified

These tickets were marked as removed, and nobody has said that they can fix them. Let's remember to look at 033-removed-20180320 as we re-evaluate our triage process, to see whether we're triaging out unnecessarily, and to evaluate whether we're deferring anything unnecessarily. But for now, we can't do these: we need to fix the 033-must stuff now.

comment:5 Changed 2 months ago by gaba

Keywords: s8-errors removed
Sponsor: Sponsor8-can
Note: See TracTickets for help on using tickets.