Tor 0.2.0.18-alpha log entries

[Ruediger Klis]

Hello all,

I just upgraded to 0.2.0.18-alpha and I've seen the following in my logs:

[...]
1.)  Jan 28 15:08:42.412 [info] read_file_to_str(): Could not open 
"/var/lib/tor/router-stability": No such file or directory

[...]
2.)  Jan 28 15:08:43.382 [info] read_file_to_str(): Could not open 
"/var/lib/tor/unverified-consensus": No such file or directory

3.)  Jan 28 15:08:43.382 [notice] We're missing a certificate from 
authority dannenberg with signing key 
F0A23AD304A0CFF4C27B3D0AE23468FBDD4E88F0: launching request.
Jan 28 15:08:43.383 [info] routers_update_all_from_networkstatus(): The 
directory authorities say my version is ok.

[...]
4.)  Jan 28 15:08:53.787 [warn] Received http status code 404 ("Not 
found") from server '85.25.151.22:9030' while fetching 
"/tor/keys/fp/585769C78764D58426B8B52B6651A5A71137189A".

5.)  Jan 28 15:08:53.787 [notice] We're missing a certificate from 
authority dannenberg with signing key 
F0A23AD304A0CFF4C27B3D0AE23468FBDD4E88F0: launching request.
Jan 28 15:08:53.787 [info] connection_dir_request_failed(): Giving up on 
directory server at '85.25.151.22'; retrying
Jan 28 15:08:53.787 [notice] We're missing a certificate from authority 
dannenberg with signing key F0A23AD304A0CFF4C27B3D0AE23468FBDD4E88F0: 
launching request.
[...]

6.)  Jan 28 15:08:54.366 [warn] Received http status code 404 ("Not 
found") from server '85.214.58.87:80' while fetching 
/tor/keys/fp/585769C78764D58426B8B52B6651A5A71137189A".
Jan 28 15:08:54.366 [info] connection_dir_request_failed(): Giving up on 
directory server at '85.214.58.87'; retrying
[...]

7.)  Jan 28 15:24:09.384 [info] connection_dir_client_reached_eof(): 
Received extra server info (size 0) from server '128.31.0.34:9032'
Jan 28 15:24:09.384 [info] connection_dir_client_reached_eof(): Received 
http status code 404 ("Not found") from server '128.31.0.34:9032' while 
fetching
"/tor/server/d/22E30802B3AF156AB4A65AF3620FBCD20C030725
+0E51AA8EEE5D6D099332E7BA6FB8AE730771C5CF
+4AC601292064ABD1785D057D8D2198F78F3B728E
+56C6AD0E38918E84A451D1866F48FD5B6342FE60
+8C928F8E9A206A6931012CA10B9977777E1DE78D
+DFF32A169565661124B176564D29AA312066944F
+764EA3AD875C93EE75D562F7FCD5AD35C34487A9
+9241E32C11B39F026BFE3DF73135F450C8966F83
+172D428D55C5C2191431E5DD4AE32653FC17B4C5
+049F0632C7C06F38160E7A0FBFCA574546353006
+2A95C86EADB095F5D1029DE99A011D482313DBEB
+1FC06BDABDD9ECABF8599BFD2F3D1CDBF0FD8938
+3AE1246C8752D87E04F530989E76E6FEFC3A5DE5
+1E0369BD1E2544827226B64B6F472DAE35F9E817
+A1428B9CE742D6AD51ABE30C0C220906C7C92890
+3DF742A4398044DE4A6DD8A8542CDB72A5C88CC6.z". I'll try again soon.
[...]


1.) + 2.) Why occur this message? I'm not running a directory, only a 
relay with dirport and tornetworkstatus.

3.) + 5.) IMHO discussed recently on the list about missed certificates?

4.) + 6.) + 7.) May be a misconfiguration??

Does anybody know a reasonable answer or an explanation?

Thanks in advance,
Ruediger

tor node arachne: 0D49 B1D8 0FD8 ED65 7D25 F137 CFB4 9B86 48C4 F386