aboutsummaryrefslogtreecommitdiff
path: root/src/or/connection_or.c
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2008-06-09 18:32:43 +0000
committerRoger Dingledine <arma@torproject.org>2008-06-09 18:32:43 +0000
commitbaa3cea213dae87197991e6d50ff53ef53e8e829 (patch)
treebab367b4318313b6814782fb7131fe86876fff62 /src/or/connection_or.c
parentdba6d8c55aa7af6e3aabe28b54fb3fc499c1d139 (diff)
downloadtor-baa3cea213dae87197991e6d50ff53ef53e8e829.tar.gz
tor-baa3cea213dae87197991e6d50ff53ef53e8e829.zip
Start noticing and reporting bootstrapping failures too. It looks like
we never bothered learning why OR conns fail, so next step is to add some infrastructure for that. svn:r15091
Diffstat (limited to 'src/or/connection_or.c')
-rw-r--r--src/or/connection_or.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/src/or/connection_or.c b/src/or/connection_or.c
index f9dd28de31..02921e1981 100644
--- a/src/or/connection_or.c
+++ b/src/or/connection_or.c
@@ -546,6 +546,8 @@ connection_or_connect(uint32_t addr, uint16_t port, const char *id_digest)
}
control_event_or_conn_status(conn, OR_CONN_EVENT_FAILED,
END_OR_CONN_REASON_TCP_REFUSED);
+ /* XXX connection_connect() can fail for all sorts of other reasons */
+ control_event_bootstrap_problem("foo", END_OR_CONN_REASON_TCP_REFUSED);
connection_free(TO_CONN(conn));
return NULL;
case 0:
@@ -795,6 +797,7 @@ connection_or_check_valid_tls_handshake(or_connection_t *conn,
router_set_status(conn->identity_digest, 0);
control_event_or_conn_status(conn, OR_CONN_EVENT_FAILED,
END_OR_CONN_REASON_OR_IDENTITY);
+ control_event_bootstrap_problem("foo", END_OR_CONN_REASON_OR_IDENTITY);
as_advertised = 0;
}
if (authdir_mode_tests_reachability(options)) {