Tor Error: couldn't read ~cached-descriptors / no current certificate

[jakdominance]

I just got an updated version of Tor (see below for specs), but it always stops partway into connecting. Here's the message log. What's wrong?

6 月 23 22:36:09.331 [Notice] Tor v0.2.0.34 (r18423). This is experimental software. Do not rely on it for strong anonymity. (Running on Darwin i386)
6 月 23 22:36:09.367 [Notice] Initialized libevent version 1.4.9-stable using method kqueue. Good.
6 月 23 22:36:09.368 [Notice] Opening Socks listener on 127.0.0.1:9050
6 月 23 22:36:09.368 [Notice] Opening Control listener on 127.0.0.1:9051
6 月 23 22:37:10.306 [Notice] Couldn't read /Users/Dakota/.tor/cached-descriptors; trying to load routers from old location /Users/Dakota/.tor/cached-routers.
6 月 23 22:37:10.308 [Notice] No current certificate known for authority moria1; launching request.
6 月 23 22:37:10.309 [Notice] No current certificate known for authority tor26; launching request.
6 月 23 22:37:10.309 [Notice] No current certificate known for authority dizum; launching request.
6 月 23 22:37:10.309 [Notice] No current certificate known for authority ides; launching request.
6 月 23 22:37:10.309 [Notice] No current certificate known for authority gabelmoo; launching request.
6 月 23 22:37:10.310 [Notice] No current certificate known for authority dannenberg; launching request.
6 月 23 22:37:10.310 [Notice] Couldn't read /Users/Dakota/.tor/cached-descriptors; trying to load routers from old location /Users/Dakota/.tor/cached-routers.

EDIT: Computer Specs:
Macbook using Mac OS X 10.5.7
Airport Extreme

 

[jakdominance]

So i turned everything off, reinstalled it and it worked fine.

however, i get this now.

6 月 24 20:32:59.869 [Notice] Tor v0.2.0.34 (r18423). This is experimental software. Do not rely on it for strong anonymity. (Running on Darwin i386)
6 月 24 20:32:59.870 [Notice] Initialized libevent version 1.4.9-stable using method kqueue. Good.
6 月 24 20:32:59.871 [Notice] Opening OR listener on 0.0.0.0:9001
6 月 24 20:32:59.871 [Notice] Opening Directory listener on 0.0.0.0:9030
6 月 24 20:32:59.871 [Notice] Opening Socks listener on 127.0.0.1:9050
6 月 24 20:32:59.871 [Notice] Opening Control listener on 127.0.0.1:9051
6 月 24 20:35:13.921 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:1443. Giving up. (waiting for circuit)

i've seen the same thing a few times on the internet but no answers, it seems. anybody know? should I submit a bug?