tor needs to perform a dir request whenever starting as a server?
[11:54] tor can no longer guess my ip address, so it never builds a desc_routerinfo - which causes all kinds of havoc [11:56] i'm using trunk [12:01] it's failing to guess mine completely: tries to figure it out from hostname, then finds the internal address, then says neither of those will do and gives up [12:02] because it gets nothing from router_pick_published_address it doesn't get past go in router_rebuild_descriptor [12:02] this results in it failing to assign desc_routerinfo [12:02] so if i then do a getinfo dir/server/fp/ on my own server fingerprint - I get a segfault [12:03] because desc_routerinfo doesn't exist and tor's assuming one exists [12:03] this solves the segfault: http://pastebin.ca/914977 [12:04] but the real problem is failing to guess the ip [12:05] it can only have been introduced recently because i generally use trunk [12:10] the real problem is probably in router_guess_address_from_dir_headers somewhere [12:16] mwenge: sry, looking at the commit statements did not reveal (to me) which one changed that behavior. [12:17] karsten: same here. i think i see the problem. if tor starts and has relatively fresh server info cached it doesn't get an ip from the dir servers until the next time it requests something [12:17] so last_guessed_ip remains 0. and if you run a server your address remains undetermined [12:20] so it looks as if tor needs to perform a dir request when starting at all times [12:20] or else cache x-your-address on file - which seems a bad idea [12:22] yup. rm -rf cache- and restarting tor gets last_guessed_ip populated again [12:22] just restarting tor with clearing the cache results it in remaining 0
sorry for the straight paste - i'm lazy
[Automatically added by flyspray2trac: Operating System: All]