Scrape requests not showing in logfile

[gunzip]

after running two torrents for several hours overnight, the logfile (message level = 3) only documents one scrape request:

$ grep -i -e 'scrape' -e 'scraping' ./logfile
Torrent_1 Scrape successful. Rescraping in 1800 seconds. (announcer.c:1336)

there is no record of a scrape request on the second torrent, nor is there any indication of subsequent scrapes at the scheduled intervals.

i believe this behavior has been present with the last several stable releases also.

transmission-daemon 2.33+ (12605), Linux Debian

[jordan]

This sounds like a repeat of #4187. If the announce response contains the scrape response fields too, as some trackers do, then the Transmission doesn't send a redundant scrape.

[gunzip]

yes this is definitely related but in #4187 i thought (wrongly) that TR was making extra unneeded scrape requests, but here i just was curious about the lack of the info in the logfile.

in this particular example, both torrents had exact same tracker both nothing re scrapes ever showed for Torrent_2.

[gunzip]

Replying to jordan:

If the announce response contains the scrape response fields too, as some trackers do, then the Transmission doesn't send a redundant scrape.

would it be possible to write this scrape info that is embedded in the announce response to the logfile? .. assuming the coding doesn't become overly complicated.

[jordan]

r12683 should fix this.

[gunzip]

Replying to jordan:

r12683 should fix this.

perfect .. it's nice to finally see the scrape logs unhidden