[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #24977 [Core Tor/Tor]: Non-fatal assertion !(tor_mem_is_zero((const char*)node->hsdir_index->fetch, DIGEST256_LEN))

To: undisclosed-recipients: ;
Subject: Re: [tor-bugs] #24977 [Core Tor/Tor]: Non-fatal assertion !(tor_mem_is_zero((const char*)node->hsdir_index->fetch, DIGEST256_LEN))
From: "Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>
Date: Tue, 15 May 2018 10:30:33 -0000
Auto-submitted: auto-generated
Delivered-to: archiver@xxxxxxxx
Delivery-date: Tue, 15 May 2018 06:30:46 -0400
In-reply-to: <043.1edc65209d7c4cb609ee022909f2c6bd@torproject.org>
List-archive: <http://lists.torproject.org/pipermail/tor-bugs/>
List-help: <mailto:tor-bugs-request@lists.torproject.org?subject=help>
List-id: "auto: Tor bug tracker status mails" <tor-bugs.lists.torproject.org>
List-post: <mailto:tor-bugs@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=unsubscribe>
References: <043.1edc65209d7c4cb609ee022909f2c6bd@torproject.org>
Reply-to: no-reply@xxxxxxxxxxxxxx, tor-assistants@xxxxxxxxxxxxxx
Sender: "tor-bugs" <tor-bugs-bounces@xxxxxxxxxxxxxxxxxxxx>

#24977: Non-fatal assertion !(tor_mem_is_zero((const
char*)node->hsdir_index->fetch, DIGEST256_LEN))
-------------------------------------------------+-------------------------
 Reporter:  asn                                  |          Owner:  dgoulet
     Type:  defect                               |         Status:
                                                 |  needs_information
 Priority:  Medium                               |      Milestone:  Tor:
                                                 |  unspecified
Component:  Core Tor/Tor                         |        Version:  Tor:
                                                 |  0.3.2.1-alpha
 Severity:  Normal                               |     Resolution:
 Keywords:  tor-hs, prop224,                     |  Actual Points:
  034-triage-20180328, 034-removed-20180502      |
Parent ID:  #25955                               |         Points:  1
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by cypherpunks):

 My computer started with a wrong time. The bug was triggered while I ran
 "openntpd -d -s" to set the correct time.

 System: debian stretch amd64 with openRC as init system
 torrc: socksPort + onion service v2 + onion service v3

 {{{
 May 14 19:01:07 txt Tor[3576]: Bootstrapped 0%: Starting
 May 14 19:01:07 txt Tor[3576]: Received local state file with skewed time
 (/var/lib/tor/state): It seems that our clock is behind by 16 hours, 57
 minutes, or that theirs is ahead. Tor requires an accurate clock to work:
 please check your time, timezone, and date settings.
 May 14 19:01:07 txt Tor[3576]: Problem bootstrapping. Stuck at 0%:
 Starting. (Clock skew -61037 in local state file from /var/lib/tor/state;
 CLOCK_SKEW; count 1; recommendation warn; host ? at ?)
 May 14 19:01:07 txt Tor[3576]: Parsing GEOIP IPv4 file
 /usr/share/tor/geoip.
 May 14 19:01:08 txt Tor[3576]: Parsing GEOIP IPv6 file
 /usr/share/tor/geoip6.
 May 14 19:01:13 txt Tor[3576]: Our clock is 14 hours, 58 minutes behind
 the time published in the consensus network status document (2018-05-15
 08:00:00 UTC).  Tor needs an accurate clock to work correctly. Please
 check your time and date settings!
 May 14 19:01:13 txt Tor[3576]: Received microdesc flavor consensus with
 skewed time (CONSENSUS): It seems that our clock is behind by 14 hours, 58
 minutes, or that theirs is ahead. Tor requires an accurate clock to work:
 please check your time, timezone, and date settings
 .
 May 14 19:01:13 txt Tor[3576]: Problem bootstrapping. Stuck at 0%:
 Starting. (Clock skew -53934 in microdesc flavor consensus from CONSENSUS;
 CLOCK_SKEW; count 2; recommendation warn; host ? at ?)
 May 14 19:01:13 txt Tor[3576]: Starting with guard context "default"
 May 14 19:01:13 txt Tor[3576]: Opening Socks listener on
 /var/run/tor/socks
 May 14 19:01:13 txt Tor[3576]: Opening Control listener on
 /var/run/tor/control
 May 14 19:01:13 txt Tor[3576]: Bootstrapped 5%: Connecting to directory
 server
 May 14 19:01:13 txt Tor[3576]: Bootstrapped 10%: Finishing handshake with
 directory server
 May 14 19:01:14 txt Tor[3576]: Bootstrapped 15%: Establishing an encrypted
 directory connection
 May 14 19:01:14 txt Tor[3576]: Bootstrapped 20%: Asking for networkstatus
 consensus
 May 14 19:01:14 txt Tor[3576]: Bootstrapped 25%: Loading networkstatus
 consensus
 May 14 19:01:15 txt Tor[3576]: Our clock is 15 hours, 58 minutes behind
 the time published in the consensus network status document (2018-05-15
 09:00:00 UTC).  Tor needs an accurate clock to work correctly. Please
 check your time and date settings!
 May 14 19:01:15 txt Tor[3576]: Received microdesc flavor consensus with
 skewed time (CONSENSUS): It seems that our clock is behind by 15 hours, 58
 minutes, or that theirs is ahead. Tor requires an accurate clock to work:
 please check your time, timezone, and date settings
 .
 May 14 19:01:15 txt Tor[3576]: Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -57526 in microdesc flavor
 consensus from CONSENSUS; CLOCK_SKEW; count 3; recommendation warn; host ?
 at ?)
 May 14 19:01:15 txt Tor[3576]: I learned some more directory information,
 but not enough to build a circuit: We have no recent usable consensus.
 May 14 19:01:18 txt Tor[3576]: Application request when we haven't used
 client functionality lately. Optimistically trying directory fetches
 again.
 May 14 19:01:18 txt Tor[3576]: Application request when we haven't used
 client f
 unctionality lately. Optimistically trying directory fetches again.
 May 14 19:01:18 txt Tor[3576]: Application request when we haven't used
 client functionality lately. Optimistically trying directory fetches
 again.
 May 14 19:01:25 txt Tor[3576]: Received NETINFO cell with skewed time
 (OR:86.59.21.38:443): It seems that our clock is behind by 16 hours, 58
 minutes, or that theirs is ahead. Tor requires an accurate clock to work:
 please check your time, timezone, and date settings.
 May 14 19:01:25 txt Tor[3576]: Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -61111 in NETINFO cell from
 OR; CLOCK_SKEW; count 4; recommendation warn; host
 847B1F850344D7876491A54892F904934E4EB85D at 86.59.21.38:443)
 May 14 19:01:26 txt Tor[3576]: Received directory with skewed time
 (DIRSERV:86.59.21.38:443): It seems that our clock is behind by 16 hours,
 58 minutes, or that theirs is ahead. Tor requires an accurate clock to
 work: please check your time, timezone, and date settings.
 May 14 19:01:26 txt Tor[3576]: Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -61114 in directory from
 DIRSERV; CLOCK_SKEW; count 5; recommendation warn; host ? at
 86.59.21.38:443)
 May 14 19:01:32 txt Tor[3576]: Received NETINFO cell with skewed time
 (OR:193.23.244.244:443): It seems that our clock is behind by 16 hours, 58
 minutes, or that theirs is ahead. Tor requires an accurate clock to work:
 please check your time, timezone, and date settings.
 May 14 19:01:32 txt Tor[3576]: Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -61112 in NETINFO cell from
 OR; CLOCK_SKEW; count 6; recommendation warn; host
 7BE683E65D48141321C5ED92F075C55364AC7123 at 193.23.244.244:443)
 May 14 19:01:32 txt Tor[3576]: Received directory with skewed time
 (DIRSERV:193.23.244.244:443): It seems that our clock is behind by 16
 hours, 58 minutes, or that theirs is ahead. Tor requires an accurate clock
 to work: please check your time, timezone, and date settings.
 May 14 19:01:32 txt Tor[3576]: Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -61114 in directory from
 DIRSERV; CLOCK_SKEW; count 7; recommendation warn; host ? at
 193.23.244.244:443)
 May 14 19:01:33 txt Tor[3576]: Our clock is 16 hours, 58 minutes behind
 the time published in the consensus network status document (2018-05-15
 10:00:00 UTC).  Tor needs an accurate clock to work correctly. Please
 check your time and date settings!
 May 14 19:01:33 txt Tor[3576]: Received microdesc flavor consensus with
 skewed time (CONSENSUS): It seems that our clock is behind by 16 hours, 58
 minutes, or that theirs is ahead. Tor requires an accurate clock to work:
 please check your time, timezone, and date settings.
 May 14 19:01:33 txt Tor[3576]: Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -61108 in microdesc flavor
 consensus from CONSENSUS; CLOCK_SKEW; count 8; recommendation warn; host ?
 at ?)
 May 14 19:01:33 txt Tor[3576]: I learned some more directory information,
 but not enough to build a circuit: We have no recent usable consensus.
 May 14 19:01:39 txt Tor[3576]: Received NETINFO cell with skewed time
 (OR:194.109.206.212:443): It seems that our clock is behind by 16 hours,
 58 minutes, or that theirs is ahead. Tor requires an accurate clock to
 work: please check your time, timezone, and date settings.
 May 14 19:01:39 txt Tor[3576]: Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -61113 in NETINFO cell from
 OR; CLOCK_SKEW; count 9; recommendation warn; host
 7EA6EAD6FD83083C538F44038BBFA077587DD755 at 194.109.206.212:443)
 May 14 19:01:39 txt Tor[3576]: Received directory with skewed time
 (DIRSERV:194.109.206.212:443): It seems that our clock is behind by 16
 hours, 58 minutes, or that theirs is ahead. Tor requires an accurate clock
 to work: please check your time, timezone, and date settings.
 May 14 19:01:39 txt Tor[3576]: Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -61113 in directory from
 DIRSERV; CLOCK_SKEW; count 10; recommendation warn; host ? at
 194.109.206.212:443)
 May 14 19:01:49 txt Tor[3576]: Application request when we haven't used
 client functionality lately. Optimistically trying directory fetches
 again.
 May 14 19:01:49 txt Tor[3576]: Application request when we haven't used
 client functionality lately. Optimistically trying directory fetches
 again.
 May 14 19:01:49 txt Tor[3576]: Application request when we haven't used
 client functionality lately. Optimistically trying directory fetches
 again.
 May 14 19:01:55 txt Tor[3576]: Received directory with skewed time
 (DIRSERV:194.109.206.212:443): It seems that our clock is behind by 16
 hours, 58 minutes, or that theirs is ahead. Tor requires an accurate clock
 to work: please check your time, timezone, and date settings.
 May 14 19:01:55 txt Tor[3576]: Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -61113 in directory from
 DIRSERV; CLOCK_SKEW; count 11; recommendation warn; host ? at
 194.109.206.212:443)
 May 14 19:02:01 txt Tor[3576]: Received NETINFO cell with skewed time
 (OR:131.188.40.189:443): It seems that our clock is behind by 16 hours, 58
 minutes, or that theirs is ahead. Tor requires an accurate clock to work:
 please check your time, timezone, and date settings.
 May 14 19:02:01 txt Tor[3576]: Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -61113 in NETINFO cell from
 OR; CLOCK_SKEW; count 12; recommendation warn; host
 F2044413DAC2E02E3D6BCF4735A19BCA1DE97281 at 131.188.40.189:443)
 May 14 19:02:01 txt Tor[3576]: Received directory with skewed time
 (DIRSERV:131.188.40.189:443): It seems that our clock is behind by 16
 hours, 58 minutes, or that theirs is ahead. Tor requires an accurate clock
 to work: please check your time, timezone, and date settings.
 May 14 19:02:01 txt Tor[3576]: Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -61113 in directory from
 DIRSERV; CLOCK_SKEW; count 13; recommendation warn; host ? at
 131.188.40.189:443)
 May 14 19:02:08 txt Tor[3576]: Received NETINFO cell with skewed time
 (OR:154.35.175.225:443): It seems that our clock is behind by 16 hours, 58
 minutes, or that theirs is ahead. Tor requires an accurate clock to work:
 please check your time, timezone, and date settings.
 May 14 19:02:08 txt Tor[3576]: Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -61112 in NETINFO cell from
 OR; CLOCK_SKEW; count 14; recommendation warn; host
 CF6D0AAFB385BE71B8E111FC5CFF4B47923733BC at 154.35.175.225:443)
 May 14 19:02:08 txt Tor[3576]: Received directory with skewed time
 (DIRSERV:154.35.175.225:443): It seems that our clock is behind by 16
 hours, 58 minutes, or that theirs is ahead. Tor requires an accurate clock
 to work: please check your time, timezone, and date settings.
 May 14 19:02:08 txt Tor[3576]: Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -61113 in directory from
 DIRSERV; CLOCK_SKEW; count 15; recommendation warn; host ? at
 154.35.175.225:443)
 May 14 19:02:13 txt Tor[3576]: Received NETINFO cell with skewed time
 (OR:171.25.193.9:80): It seems that our clock is behind by 16 hours, 58
 minutes, or that theirs is ahead. Tor requires an accurate clock to work:
 please check your time, timezone, and date settings.
 May 14 19:02:13 txt Tor[3576]: Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -61113 in NETINFO cell from
 OR; CLOCK_SKEW; count 16; recommendation warn; host
 BD6A829255CB08E66FBE7D3748363586E46B3810 at 171.25.193.9:80)
 May 14 19:02:14 txt Tor[3576]: Received directory with skewed time
 (DIRSERV:171.25.193.9:80): It seems that our clock is behind by 16 hours,
 58 minutes, or that theirs is ahead. Tor requires an accurate clock to
 work: please check your time, timezone, and date settings.
 May 14 19:02:14 txt Tor[3576]: Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -61113 in directory from
 DIRSERV; CLOCK_SKEW; count 17; recommendation warn; host ? at
 171.25.193.9:80)
 May 14 19:02:21 txt Tor[3576]: Application request when we haven't used
 client functionality lately. Optimistically trying directory fetches
 again.
 May 14 19:02:21 txt Tor[3576]: Application request when we haven't used
 client functionality lately. Optimistically trying directory fetches
 again.
 May 14 19:02:21 txt Tor[3576]: Application request when we haven't used
 client functionality lately. Optimistically trying directory fetches
 again.
 May 14 19:02:28 txt Tor[3576]: Received NETINFO cell with skewed time
 (OR:128.31.0.34:9101): It seems that our clock is behind by 16 hours, 58
 minutes, or that theirs is ahead. Tor requires an accurate clock to work:
 please check your time, timezone, and date settings.
 May 14 19:02:28 txt Tor[3576]: Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -61112 in NETINFO cell from
 OR; CLOCK_SKEW; count 18; recommendation warn; host
 9695DFC35FFEB861329B9F1AB04C46397020CE31 at 128.31.0.34:9101)
 May 15 12:01:08 txt Tor[3576]: Tried for 61127 seconds to get a connection
 to [scrubbed]:443. Giving up.
 May 15 12:01:08 txt Tor[3576]: Tried for 61127 seconds to get a connection
 to [scrubbed]:443. Giving up.
 May 15 12:01:08 txt Tor[3576]: Your system clock just jumped 61114 seconds
 forward; assuming established circuits no longer work.
 May 15 12:01:08 txt Tor[3576]: Bootstrapped 80%: Connecting to the Tor
 network
 May 15 12:01:08 txt Tor[3576]: Bootstrapped 90%: Establishing a Tor
 circuit
 May 15 12:01:08 txt Tor[3576]: Tor has successfully opened a circuit.
 Looks like client functionality is working.
 May 15 12:01:08 txt Tor[3576]: Bootstrapped 100%: Done
 May 15 12:01:08 txt Tor[3576]: tor_bug_occurred_(): Bug:
 ../src/or/hs_service.c:1952: should_rotate_descriptors: Non-fatal
 assertion !(service->desc_current == NULL || service->desc_next == NULL)
 failed. (on Tor 0.3.3.5-rc )
 May 15 12:01:08 txt Tor[3576]: Bug: Non-fatal assertion
 !(service->desc_current == NULL || service->desc_next == NULL) failed in
 should_rotate_descriptors at ../src/or/hs_service.c:1952. Stack trace: (on
 Tor 0.3.3.5-rc )
 May 15 12:01:08 txt Tor[3576]: Bug:     /usr/bin/tor(log_backtrace+0x44)
 [0x55da645ac3f4] (on Tor 0.3.3.5-rc )
 May 15 12:01:08 txt Tor[3576]: Bug:
 /usr/bin/tor(tor_bug_occurred_+0xb9) [0x55da645c7c29] (on Tor 0.3.3.5-rc )
 May 15 12:01:08 txt Tor[3576]: Bug:
 /usr/bin/tor(hs_service_run_scheduled_events+0x887) [0x55da6459aa77] (on
 Tor 0.3.3.5-rc )
 May 15 12:01:08 txt Tor[3576]: Bug:     /usr/bin/tor(+0x505e1)
 [0x55da644735e1] (on Tor 0.3.3.5-rc )
 May 15 12:01:08 txt Tor[3576]: Bug:     /usr/bin/tor(+0x70df0)
 [0x55da64493df0] (on Tor 0.3.3.5-rc )
 May 15 12:01:08 txt Tor[3576]: Bug:     /usr/lib/x86_64-linux-
 gnu/libevent-2.0.so.5(event_base_loop+0x6a0) [0x7f5ba944c5a0] (on Tor
 0.3.3.5-rc )
 May 15 12:01:08 txt Tor[3576]: Bug:     /usr/bin/tor(do_main_loop+0x2bc)
 [0x55da644777ec] (on Tor 0.3.3.5-rc )
 May 15 12:01:08 txt Tor[3576]: Bug:     /usr/bin/tor(tor_run_main+0x275)
 [0x55da64478ef5] (on Tor 0.3.3.5-rc )
 May 15 12:01:08 txt Tor[3576]: Bug:     /usr/bin/tor(tor_main+0x3a)
 [0x55da6447233a] (on Tor 0.3.3.5-rc )
 May 15 12:01:08 txt Tor[3576]: Bug:     /usr/bin/tor(main+0x19)
 [0x55da644720a9] (on Tor 0.3.3.5-rc )
 May 15 12:01:08 txt Tor[3576]: Bug:     /lib/x86_64-linux-
 gnu/libc.so.6(__libc_start_main+0xf1) [0x7f5ba7ca82e1] (on Tor 0.3.3.5-rc
 )
 May 15 12:01:08 txt Tor[3576]: Bug:     /usr/bin/tor(_start+0x2a)
 [0x55da644720fa] (on Tor 0.3.3.5-rc )
 May 15 12:01:08 txt Tor[3576]: should_rotate_descriptors(): Bug: Service
 descriptor is NULL ((nil)/(nil)). Next rotation time is 1526367600 (now:
 1526378468). Valid after time from consensus is 1526378400 (on Tor
 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: tor_bug_occurred_(): Bug:
 ../src/or/hs_common.c:1294: node_has_hsdir_index: Non-fatal assertion
 !(tor_mem_is_zero((const char*)node->hsdir_index->fetch, DIGEST256_LEN))
 failed. (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug: Non-fatal assertion
 !(tor_mem_is_zero((const char*)node->hsdir_index->fetch, DIGEST256_LEN))
 failed in node_has_hsdir_index at ../src/or/hs_common.c:1294. Stack trace:
 (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(log_backtrace+0x44)
 [0x55da645ac3f4] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:
 /usr/bin/tor(tor_bug_occurred_+0xb9) [0x55da645c7c29] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:
 /usr/bin/tor(hs_get_responsible_hsdirs+0x396) [0x55da6458d236] (on Tor
 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:
 /usr/bin/tor(hs_service_run_scheduled_events+0x1a44) [0x55da6459bc34] (on
 Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(+0x505e1)
 [0x55da644735e1] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(+0x70df0)
 [0x55da64493df0] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/lib/x86_64-linux-
 gnu/libevent-2.0.so.5(event_base_loop+0x6a0) [0x7f5ba944c5a0] (on Tor
 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(do_main_loop+0x2bc)
 [0x55da644777ec] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(tor_run_main+0x275)
 [0x55da64478ef5] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(tor_main+0x3a)
 [0x55da6447233a] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(main+0x19)
 [0x55da644720a9] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /lib/x86_64-linux-
 gnu/libc.so.6(__libc_start_main+0xf1) [0x7f5ba7ca82e1] (on Tor 0.3.3.5-rc
 )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(_start+0x2a)
 [0x55da644720fa] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: tor_bug_occurred_(): Bug:
 ../src/or/hs_common.c:1294: node_has_hsdir_index: Non-fatal assertion
 !(tor_mem_is_zero((const char*)node->hsdir_index->fetch, DIGEST256_LEN))
 failed. (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug: Non-fatal assertion
 !(tor_mem_is_zero((const char*)node->hsdir_index->fetch, DIGEST256_LEN))
 failed in node_has_hsdir_index at ../src/or/hs_common.c:1294. Stack trace:
 (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(log_backtrace+0x44)
 [0x55da645ac3f4] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:
 /usr/bin/tor(tor_bug_occurred_+0xb9) [0x55da645c7c29] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:
 /usr/bin/tor(hs_get_responsible_hsdirs+0x396) [0x55da6458d236] (on Tor
 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:
 /usr/bin/tor(hs_service_run_scheduled_events+0x1a44) [0x55da6459bc34] (on
 Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(+0x505e1)
 [0x55da644735e1] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(+0x70df0)
 [0x55da64493df0] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/lib/x86_64-linux-
 gnu/libevent-2.0.so.5(event_base_loop+0x6a0) [0x7f5ba944c5a0] (on Tor
 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(do_main_loop+0x2bc)
 [0x55da644777ec] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(tor_run_main+0x275)
 [0x55da64478ef5] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(tor_main+0x3a)
 [0x55da6447233a] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(main+0x19)
 [0x55da644720a9] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /lib/x86_64-linux-
 gnu/libc.so.6(__libc_start_main+0xf1) [0x7f5ba7ca82e1] (on Tor 0.3.3.5-rc
 )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(_start+0x2a)
 [0x55da644720fa] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: tor_bug_occurred_(): Bug:
 ../src/or/hs_common.c:1294: node_has_hsdir_index: Non-fatal assertion
 !(tor_mem_is_zero((const char*)node->hsdir_index->fetch, DIGEST256_LEN))
 failed. (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug: Non-fatal assertion
 !(tor_mem_is_zero((const char*)node->hsdir_index->fetch, DIGEST256_LEN))
 failed in node_has_hsdir_index at ../src/or/hs_common.c:1294. Stack trace:
 (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(log_backtrace+0x44)
 [0x55da645ac3f4] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:
 /usr/bin/tor(tor_bug_occurred_+0xb9) [0x55da645c7c29] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:
 /usr/bin/tor(hs_get_responsible_hsdirs+0x396) [0x55da6458d236] (on Tor
 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:
 /usr/bin/tor(hs_service_run_scheduled_events+0x1a44) [0x55da6459bc34] (on
 Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(+0x505e1)
 [0x55da644735e1] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(+0x70df0)
 [0x55da64493df0] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/lib/x86_64-linux-
 gnu/libevent-2.0.so.5(event_base_loop+0x6a0) [0x7f5ba944c5a0] (on Tor
 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(do_main_loop+0x2bc)
 [0x55da644777ec] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(tor_run_main+0x275)
 [0x55da64478ef5] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(tor_main+0x3a)
 [0x55da6447233a] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(main+0x19)
 [0x55da644720a9] (on Tor 0.3.3.5-rc )
 May 15 12:01:10 txt Tor[3576]: Bug:     /lib/x86_64-linux-
 gnu/libc.so.6(__libc_start_main+0xf1) [0x7f5ba7ca82e1] (on Tor 0.3.3.5-rc
 )
 May 15 12:01:10 txt Tor[3576]: Bug:     /usr/bin/tor(_start+0x2a)
 [0x55da644720fa] (on Tor 0.3.3.5-rc )
 }}}
 The log shows many more recurrences of tor_bug_occured. I only copied the
 first few. The last recurrence was 5 seconds later.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24977#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Prev by Author: Re: [tor-bugs] #25899 [Core Tor/Tor]: Only run retry_dns() and check_dns_honesty() on exits
Next by Author: Re: [tor-bugs] #26048 [Applications/Tor Browser]: potential confusing "restart to update" message in ESR60
Previous by thread: Re: [tor-bugs] #24977 [Core Tor/Tor]: Non-fatal assertion !(tor_mem_is_zero((const char*)node->hsdir_index->fetch, DIGEST256_LEN))
Next by thread: Re: [tor-bugs] #24977 [Core Tor/Tor]: Non-fatal assertion !(tor_mem_is_zero((const char*)node->hsdir_index->fetch, DIGEST256_LEN))
Index(es):
- Author
- Thread