Re: [tor-relays] Failure from drain-fd

I added these items to the torrc file:

logtimegranularity 1
log [edge] debug file c:\tor\data\tor\logfile001.log

In the regular log I see this warning:

Nov 04 14:40:47.507 [warn] Failure from drain_fd: No error [4953 similar message(s) suppressed in last 7200 seconds]

In the debug logfile I see these events around the same timeframe:

Nov 04 14:40:26.965 [info] connection_edge_process_relay_cell(): sendme cell dropped, unknown stream (streamid 61113).
Nov 04 14:40:30.484 [debug] connection_edge_process_relay_cell(): Now seen 10957 relay cells here (command 6, stream 0).
Nov 04 14:40:33.043 [debug] connection_edge_process_relay_cell(): Now seen 10958 relay cells here (command 14, stream 0).
Nov 04 14:40:35.403 [debug] connection_edge_process_relay_cell(): Now seen 10959 relay cells here (command 14, stream 0).
Nov 04 14:40:36.975 [debug] connection_edge_process_relay_cell(): Now seen 10960 relay cells here (command 14, stream 0).
Nov 04 14:40:38.527 [debug] connection_edge_process_relay_cell(): Now seen 10961 relay cells here (command 6, stream 0).
Nov 04 14:40:43.288 [debug] connection_edge_process_relay_cell(): Now seen 10962 relay cells here (command 14, stream 0).
Nov 04 14:40:44.730 [debug] connection_edge_process_relay_cell(): Now seen 10963 relay cells here (command 33, stream 0).
Nov 04 14:40:46.067 [debug] connection_edge_process_relay_cell(): Now seen 10964 relay cells here (command 14, stream 0).
Nov 04 14:40:47.413 [debug] connection_edge_process_relay_cell(): Now seen 10965 relay cells here (command 14, stream 0).
Nov 04 14:40:47.912 [debug] connection_edge_process_relay_cell(): Now seen 10966 relay cells here (command 14, stream 0).
Nov 04 14:40:48.256 [debug] connection_edge_process_relay_cell(): Now seen 10967 relay cells here (command 6, stream 0).

Otherwise I also see lots of these:

Nov 04 14:40:20.037 [debug] connection_edge_package_raw_inbuf(): -1: Packaging 498 bytes (7677 waiting).
Nov 04 14:40:20.037 [debug] connection_edge_package_raw_inbuf(): conn->package_window is now 396
Nov 04 14:40:20.037 [debug] circuit_consider_stop_edge_reading(): considering circ->package_window 896
Nov 04 14:40:20.037 [debug] connection_edge_package_raw_inbuf(): -1: Packaging 498 bytes (7179 waiting).
Nov 04 14:40:20.037 [debug] connection_edge_package_raw_inbuf(): conn->package_window is now 395
Nov 04 14:40:20.037 [debug] circuit_consider_stop_edge_reading(): considering circ->package_window 895
Nov 04 14:40:20.037 [debug] connection_edge_package_raw_inbuf(): -1: Packaging 498 bytes (6681 waiting).

Is this helpful or should I remove the "[edge]" domain and let it log everything?

Thanks,
Brian

> Date: Thu, 29 Oct 2015 00:14:05 -0500
> To: tor-relays@xxxxxxxxxxxxxxxxxxxx
> From: starlight.2015q3@xxxxxxxxxxx
> Subject: Re: [tor-relays] Failure from drain-fd
>
> At 23:58 10/28/2015 -0500, starlight.2015q3@xxxxxxxxxxx wrote:
> > Log debug file logfile001
>
> If the volume of messages is too high,
> you might have luck with "domain"
> logging, which narrows it to
> particular functional realms, for
> example:
>
> setconf Log="[edge] debug file logfile001"
>
> where the "edge" domain relates to event
> processing. See
>
> Log [domain,...]
>
> in
>
> https://www.torproject.org/docs/tor-manual.html.en
>
> for details and the full list of message domains.
>
> _______________________________________________
> tor-relays mailing list
> tor-relays@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays