Re: [tor-bugs] #28733 [Core Tor/Tor]: {CONSDIFF} Refusing to apply consensus diff
#28733: {CONSDIFF} Refusing to apply consensus diff
--+---
Reporter: traumschule | Owner: (none)
Type: defect| Status: needs_information
Priority: Medium| Milestone: Tor: unspecified
Component: Core Tor/Tor |Version:
Severity: Normal| Resolution:
Keywords: consensus | Actual Points:
Parent ID: #26310| Points:
Reviewer:|Sponsor:
--+---
Comment (by cypherpunks):
Possibly related to #28614 (from
https://blog.torproject.org/comment/279659#comment-279659).
--
Ticket URL:
Tor Bug Tracker & Wiki
Re: [tor-bugs] #28733 [Core Tor/Tor]: {CONSDIFF} Refusing to apply consensus diff
#28733: {CONSDIFF} Refusing to apply consensus diff
--+---
Reporter: traumschule | Owner: (none)
Type: defect| Status: needs_information
Priority: Medium| Milestone: Tor: unspecified
Component: Core Tor/Tor |Version:
Severity: Normal| Resolution:
Keywords: consensus | Actual Points:
Parent ID: #26310| Points:
Reviewer:|Sponsor:
--+---
Comment (by traumschule):
This time with Tor Browser after applying diffs from two DG. The only way
to solve this was to remove both files and restart tor. First failing:
> Jan 21 04:29:55.000 [warn] Refusing to apply consensus diff because the
base consensus doesn't match the digest as found in the consensus diff
header.
--
Ticket URL:
Tor Bug Tracker & Wiki
Re: [tor-bugs] #28733 [Core Tor/Tor]: {CONSDIFF} Refusing to apply consensus diff
#28733: {CONSDIFF} Refusing to apply consensus diff
--+---
Reporter: traumschule | Owner: (none)
Type: defect| Status: needs_information
Priority: Medium| Milestone: Tor: unspecified
Component: Core Tor/Tor |Version:
Severity: Normal| Resolution:
Keywords: consensus | Actual Points:
Parent ID: #26310| Points:
Reviewer:|Sponsor:
--+---
Changes (by traumschule):
* Attachment "cached-microdescs.tar.xz" added.
It happened again.
--
Ticket URL:
Tor Bug Tracker & Wiki
Re: [tor-bugs] #28733 [Core Tor/Tor]: {CONSDIFF} Refusing to apply consensus diff
#28733: {CONSDIFF} Refusing to apply consensus diff
--+---
Reporter: traumschule | Owner: (none)
Type: defect| Status: needs_information
Priority: Medium| Milestone: Tor: unspecified
Component: Core Tor/Tor |Version:
Severity: Normal| Resolution:
Keywords: consensus | Actual Points:
Parent ID: #26310| Points:
Reviewer:|Sponsor:
--+---
Changes (by teor):
* status: new => needs_information
* milestone: => Tor: unspecified
--
Ticket URL:
Tor Bug Tracker & Wiki
Re: [tor-bugs] #28733 [Core Tor/Tor]: {CONSDIFF} Refusing to apply consensus diff
#28733: {CONSDIFF} Refusing to apply consensus diff
--+
Reporter: traumschule | Owner: (none)
Type: defect| Status: new
Priority: Medium| Milestone:
Component: Core Tor/Tor |Version:
Severity: Normal| Resolution:
Keywords: consensus | Actual Points:
Parent ID: #26310| Points:
Reviewer:|Sponsor:
--+
Comment (by nickm):
So the consensus diff is supposed to include the starting hash and the
ending hash. If the consensus diff is not corrupted, and if we're
checking the starting hash, then applying the diff should result in the
ending hash.
So probably one of those conditions is violated? Maybe we're not checking
the starting hash, or maybe we're applying the diff to the wrong thing, or
maybe the consensus diff is corrupted.
The fact that this happens over and over makes me wonder if we're
downloading the diff over and over. If we are, then maybe there's a
problem with the initial consensus that we're applying it to?
--
Ticket URL:
Tor Bug Tracker & Wiki
Re: [tor-bugs] #28733 [Core Tor/Tor]: {CONSDIFF} Refusing to apply consensus diff
#28733: {CONSDIFF} Refusing to apply consensus diff
--+
Reporter: traumschule | Owner: (none)
Type: defect| Status: new
Priority: Medium| Milestone:
Component: Core Tor/Tor |Version:
Severity: Normal| Resolution:
Keywords: consensus | Actual Points:
Parent ID: #26310| Points:
Reviewer:|Sponsor:
--+
Comment (by teor):
Replying to [comment:5 nickm]:
> Teor: Hm, I don't _think_ that race is possible, but I'm not sure. Does
the log make you think that might be what's happening here?
A race is one option, if both sides are behaving correctly.
Another option is that one side could be sending the wrong data or hash.
--
Ticket URL:
Tor Bug Tracker & Wiki
Re: [tor-bugs] #28733 [Core Tor/Tor]: {CONSDIFF} Refusing to apply consensus diff
#28733: {CONSDIFF} Refusing to apply consensus diff
--+
Reporter: traumschule | Owner: (none)
Type: defect| Status: new
Priority: Medium| Milestone:
Component: Core Tor/Tor |Version:
Severity: Normal| Resolution:
Keywords: consensus | Actual Points:
Parent ID: #26310| Points:
Reviewer:|Sponsor:
--+
Comment (by nickm):
Teor: Hm, I don't _think_ that race is possible, but I'm not sure. Does
the log make you think that might be what's happening here?
--
Ticket URL:
Tor Bug Tracker & Wiki
Re: [tor-bugs] #28733 [Core Tor/Tor]: {CONSDIFF} Refusing to apply consensus diff
#28733: {CONSDIFF} Refusing to apply consensus diff
--+
Reporter: traumschule | Owner: (none)
Type: defect| Status: new
Priority: Medium| Milestone:
Component: Core Tor/Tor |Version:
Severity: Normal| Resolution:
Keywords: consensus | Actual Points:
Parent ID: #26310| Points:
Reviewer:|Sponsor:
--+
Comment (by teor):
Replying to [comment:2 traumschule]:
> Where can i find the diff? It seems the received diff is not cached on
disk. The rejected string
{{{308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308}}}
can't be found in any file. The folder diff-cache only contains files from
Aug and Sep - did the file structure change since Tor 0.3.3.7?
We might not store the diff on disk.
Look for your CacheDirectory, which might not be the same as your
DataDirectory.
> Looking for this line brought up a local log from July, #24300
Possibly related, set parent to #26310.
> and
> comment:7:issue:27315
> > Downloading consensus from $consensus_guard using /tor/status-
vote/current/consensus-
microdesc/0232AF+14C131+23D15D+27102B+49015F+D586D1+E8A9C4+ED03BB+EFCBE7.z
This is just a normal log when downloading a consensus.
--
Ticket URL:
Tor Bug Tracker & Wiki
Re: [tor-bugs] #28733 [Core Tor/Tor]: {CONSDIFF} Refusing to apply consensus diff
#28733: {CONSDIFF} Refusing to apply consensus diff
--+
Reporter: traumschule | Owner: (none)
Type: defect| Status: new
Priority: Medium| Milestone:
Component: Core Tor/Tor |Version:
Severity: Normal| Resolution:
Keywords: consensus | Actual Points:
Parent ID: #26310| Points:
Reviewer:|Sponsor:
--+
Old description:
> Since todays HUP by lograte these CONSDIFF warnings showed up. Could the
> connection failures be related?
>
> {{{
> Dec 05 00:00:07.000 [notice] Tor 0.4.0.0-alpha-dev opening new log file.
> Dec 05 00:00:22.000 [warn] {CONSDIFF} Refusing to apply consensus diff
> because the base consensus doesn't match the digest as found in the
> consensus diff header.
> Dec 05 00:00:22.000 [warn] {CONSDIFF} Expected:
> 6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
> 308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
> Dec 05 00:00:22.000 [warn] {DIR} Could not apply consensus diff received
> from server '$directory_guard'
> Dec 05 00:00:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
> because the base consensus doesn't match the digest as found in the
> consensus diff header.
> <...>
> Dec 05 00:50:40.000 [warn] {DIR} Could not apply consensus diff received
> from server '$directory_guard'
> Dec 05 00:53:02.000 [warn] {CONSDIFF} Refusing to apply consensus diff
> because the base consensus doesn't match the digest as found in the
> consensus diff header.
> Dec 05 00:53:02.000 [warn] {CONSDIFF} Expected:
> 6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
> 308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
> Dec 05 00:53:02.000 [warn] {DIR} Could not apply consensus diff received
> from server '$directory_guard'
> Dec 05 00:53:08.000 [notice] {APP} Tried for 120 seconds to get a
> connection to
> 5gdvpfoh6kb2iqbizb37lzk2ddzrwa47m6rpdueg2m656fovmbhoptqd:993. Giving up.
> (waiting for rendezvous desc)
> Dec 05 00:58:09.000 [notice] {APP} Tried for 120 seconds to get a
> connection to
> 5gdvpfoh6kb2iqbizb37lzk2ddzrwa47m6rpdueg2m656fovmbhoptqd:993. Giving up.
> (waiting for rendezvous desc)
> }}}
>
> Additionally info log shows
> {{{
> Dec 05 00:00:07.000 [info] {DIR} directory_send_command(): Downloading
> consensus from $directory_guard using /tor/status-vote/current/consensus-
> microdesc/0232AF+14C131+23D15D+27102B+49015F+D586D1+E8A9C4+ED03BB+EFCBE7.z
> <...>
> Dec 05 02:00:40.000 [info] {DIR} directory_send_command(): Downloading
> consensus from $directory_guard using /tor/status-vote/current/consensus-
> microdesc/0232AF+14C131+23D15D+27102B+49015F+D586D1+E8A9C4+ED03BB+EFCBE7.z
> }}}
>
> = directory guard versions
> - Tor 0.3.2.10 on Linux
> - Tor 0.3.1.10 on Linux
> - Tor 0.3.4.8 on Linux
>
> To avoid fingerprinting (#10969) addresses are scrubbed and are available
> on request.
New description:
Since todays HUP by lograte these CONSDIFF warnings showed up. Could the
connection failures be related?
{{{
Dec 05 00:00:07.000 [notice] Tor 0.4.0.0-alpha-dev opening new log file.
Dec 05 00:00:22.000 [warn] {CONSDIFF} Refusing to apply consensus diff
because the base consensus doesn't match the digest as found in the
consensus diff header.
Dec 05 00:00:22.000 [warn] {CONSDIFF} Expected:
6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
Dec 05 00:00:22.000 [warn] {DIR} Could not apply consensus diff received
from server '$directory_guard'
Dec 05 00:00:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
because the base consensus doesn't match the digest as found in the
consensus diff header.
Dec 05 00:00:40.000 [warn] {CONSDIFF} Expected:
6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
Dec 05 00:00:40.000 [warn] {DIR} Could not apply consensus diff received
from server '$directory_guard'
Dec 05 00:01:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
because the base consensus doesn't match the digest as found in the
consensus diff header.
Dec 05 00:01:40.000 [warn] {CONSDIFF} Expected:
6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
Dec 05 00:01:40.000 [warn] {DIR} Could not apply consensus diff received
from server '$directory_guard'
Dec 05 00:02:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
because the base consensus doesn't match the digest as found in the
consensus diff header.
Dec 05 00:02:40.000 [warn] {CONSDIFF} Expected:
6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
Dec 05
Re: [tor-bugs] #28733 [Core Tor/Tor]: {CONSDIFF} Refusing to apply consensus diff
#28733: {CONSDIFF} Refusing to apply consensus diff
--+
Reporter: traumschule | Owner: (none)
Type: defect| Status: new
Priority: Medium| Milestone:
Component: Core Tor/Tor |Version:
Severity: Normal| Resolution:
Keywords: consensus | Actual Points:
Parent ID: #26310| Points:
Reviewer:|Sponsor:
--+
Changes (by traumschule):
* Attachment "cached-microdesc.tar.xz" added.
cached-microdesc* files
--
Ticket URL:
Tor Bug Tracker & Wiki
Re: [tor-bugs] #28733 [Core Tor/Tor]: {CONSDIFF} Refusing to apply consensus diff
#28733: {CONSDIFF} Refusing to apply consensus diff
--+
Reporter: traumschule | Owner: (none)
Type: defect| Status: new
Priority: Medium| Milestone:
Component: Core Tor/Tor |Version:
Severity: Normal| Resolution:
Keywords: consensus | Actual Points:
Parent ID: #26310| Points:
Reviewer:|Sponsor:
--+
Old description:
> Since todays HUP by lograte these CONSDIFF warnings showed up. Could the
> connection failures be related?
>
> {{{
> Dec 05 00:00:07.000 [notice] Tor 0.4.0.0-alpha-dev opening new log file.
> Dec 05 00:00:22.000 [warn] {CONSDIFF} Refusing to apply consensus diff
> because the base consensus doesn't match the digest as found in the
> consensus diff header.
> Dec 05 00:00:22.000 [warn] {CONSDIFF} Expected:
> 6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
> 308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
> Dec 05 00:00:22.000 [warn] {DIR} Could not apply consensus diff received
> from server '$directory_guard'
> Dec 05 00:00:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
> because the base consensus doesn't match the digest as found in the
> consensus diff header.
> Dec 05 00:00:40.000 [warn] {CONSDIFF} Expected:
> 6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
> 308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
> Dec 05 00:00:40.000 [warn] {DIR} Could not apply consensus diff received
> from server '$directory_guard'
> Dec 05 00:01:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
> because the base consensus doesn't match the digest as found in the
> consensus diff header.
> Dec 05 00:01:40.000 [warn] {CONSDIFF} Expected:
> 6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
> 308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
> Dec 05 00:01:40.000 [warn] {DIR} Could not apply consensus diff received
> from server '$directory_guard'
> Dec 05 00:02:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
> because the base consensus doesn't match the digest as found in the
> consensus diff header.
> Dec 05 00:02:40.000 [warn] {CONSDIFF} Expected:
> 6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
> 308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
> Dec 05 00:02:40.000 [warn] {DIR} Could not apply consensus diff received
> from server '$directory_guard'
> Dec 05 00:02:58.000 [notice] {APP} Tried for 120 seconds to get a
> connection to
> 5gdvpfoh6kb2iqbizb37lzk2ddzrwa47m6rpdueg2m656fovmbhoptqd:993. Giving up.
> (waiting for rendezvous desc)
> Dec 05 00:03:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
> because the base consensus doesn't match the digest as found in the
> consensus diff header.
> Dec 05 00:03:40.000 [warn] {CONSDIFF} Expected:
> 6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
> 308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
> Dec 05 00:03:40.000 [warn] {DIR} Could not apply consensus diff received
> from server '$directory_guard'
> Dec 05 00:04:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
> because the base consensus doesn't match the digest as found in the
> consensus diff header.
> Dec 05 00:04:40.000 [warn] {CONSDIFF} Expected:
> 6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
> 308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
> Dec 05 00:04:40.000 [warn] {DIR} Could not apply consensus diff received
> from server '$directory_guard'
> Dec 05 00:05:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
> because the base consensus doesn't match the digest as found in the
> consensus diff header.
> Dec 05 00:05:40.000 [warn] {CONSDIFF} Expected:
> 6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
> 308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
> Dec 05 00:05:40.000 [warn] {DIR} Could not apply consensus diff received
> from server '$directory_guard'
> Dec 05 00:06:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
> because the base consensus doesn't match the digest as found in the
> consensus diff header.
> Dec 05 00:06:40.000 [warn] {CONSDIFF} Expected:
> 6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
> 308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
> Dec 05 00:06:40.000 [warn] {DIR} Could not apply consensus diff received
> from server '$directory_guard'
> Dec 05 00:07:49.000 [warn] {CONSDIFF} Refusing to apply consensus diff
> because the base consensus doesn't match the digest as found in the
> consensus diff header.
> Dec 05 00:07:49.000 [warn] {CONSDIFF} Expected:
> 6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
>
Re: [tor-bugs] #28733 [Core Tor/Tor]: {CONSDIFF} Refusing to apply consensus diff
#28733: {CONSDIFF} Refusing to apply consensus diff
--+
Reporter: traumschule | Owner: (none)
Type: defect| Status: new
Priority: Medium| Milestone:
Component: Core Tor/Tor |Version:
Severity: Normal| Resolution:
Keywords: consensus | Actual Points:
Parent ID: #26310| Points:
Reviewer:|Sponsor:
--+
Changes (by teor):
* cc: nickm (added)
* parent: => #26310
Comment:
It would be really helpful to have the base consensus and the diff that
was received.
I wonder if we need to modify these logs to get more useful info.
I hope nickm can help diagnose this issue.
--
Ticket URL:
Tor Bug Tracker & Wiki
[tor-bugs] #28733 [Core Tor/Tor]: {CONSDIFF} Refusing to apply consensus diff
#28733: {CONSDIFF} Refusing to apply consensus diff
--+---
Reporter: traumschule | Owner: (none)
Type: defect| Status: new
Priority: Medium| Milestone:
Component: Core Tor/Tor |Version:
Severity: Normal| Keywords: consensus
Actual Points:| Parent ID:
Points:| Reviewer:
Sponsor:|
--+---
Since todays HUP by lograte these CONSDIFF warnings showed up. Could the
connection failures be related?
{{{
Dec 05 00:00:07.000 [notice] Tor 0.4.0.0-alpha-dev opening new log file.
Dec 05 00:00:22.000 [warn] {CONSDIFF} Refusing to apply consensus diff
because the base consensus doesn't match the digest as found in the
consensus diff header.
Dec 05 00:00:22.000 [warn] {CONSDIFF} Expected:
6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
Dec 05 00:00:22.000 [warn] {DIR} Could not apply consensus diff received
from server '$directory_guard'
Dec 05 00:00:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
because the base consensus doesn't match the digest as found in the
consensus diff header.
Dec 05 00:00:40.000 [warn] {CONSDIFF} Expected:
6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
Dec 05 00:00:40.000 [warn] {DIR} Could not apply consensus diff received
from server '$directory_guard'
Dec 05 00:01:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
because the base consensus doesn't match the digest as found in the
consensus diff header.
Dec 05 00:01:40.000 [warn] {CONSDIFF} Expected:
6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
Dec 05 00:01:40.000 [warn] {DIR} Could not apply consensus diff received
from server '$directory_guard'
Dec 05 00:02:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
because the base consensus doesn't match the digest as found in the
consensus diff header.
Dec 05 00:02:40.000 [warn] {CONSDIFF} Expected:
6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
Dec 05 00:02:40.000 [warn] {DIR} Could not apply consensus diff received
from server '$directory_guard'
Dec 05 00:02:58.000 [notice] {APP} Tried for 120 seconds to get a
connection to
5gdvpfoh6kb2iqbizb37lzk2ddzrwa47m6rpdueg2m656fovmbhoptqd:993. Giving up.
(waiting for rendezvous desc)
Dec 05 00:03:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
because the base consensus doesn't match the digest as found in the
consensus diff header.
Dec 05 00:03:40.000 [warn] {CONSDIFF} Expected:
6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
Dec 05 00:03:40.000 [warn] {DIR} Could not apply consensus diff received
from server '$directory_guard'
Dec 05 00:04:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
because the base consensus doesn't match the digest as found in the
consensus diff header.
Dec 05 00:04:40.000 [warn] {CONSDIFF} Expected:
6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
Dec 05 00:04:40.000 [warn] {DIR} Could not apply consensus diff received
from server '$directory_guard'
Dec 05 00:05:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
because the base consensus doesn't match the digest as found in the
consensus diff header.
Dec 05 00:05:40.000 [warn] {CONSDIFF} Expected:
6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
Dec 05 00:05:40.000 [warn] {DIR} Could not apply consensus diff received
from server '$directory_guard'
Dec 05 00:06:40.000 [warn] {CONSDIFF} Refusing to apply consensus diff
because the base consensus doesn't match the digest as found in the
consensus diff header.
Dec 05 00:06:40.000 [warn] {CONSDIFF} Expected:
6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
Dec 05 00:06:40.000 [warn] {DIR} Could not apply consensus diff received
from server '$directory_guard'
Dec 05 00:07:49.000 [warn] {CONSDIFF} Refusing to apply consensus diff
because the base consensus doesn't match the digest as found in the
consensus diff header.
Dec 05 00:07:49.000 [warn] {CONSDIFF} Expected:
6630240AA7F1F643B7DCEFCD0B402F4860D1129C810927F0F6774DA51D7BC75E; found:
308CC8C02AD1A45612737D112962988069ED9A8F78EEDD8CDF5D532CC5747308
Dec 05 00:07:49.000 [warn] {DIR} Could not apply consensus diff
