I'm trying to use TorStatus and it took me almost 2 hours to set everything up and able to run tns_update.pl smoothly with no error. However, I am facing a problem that Google cannot help me.
[0] starting... [0] mirror? [0] connecting to Tor [0] authenticating with Tor [0] starting descriptions *The TorStatus database was not updated properly. An error has occured. I will continue to try to update, however.*
It says an error has occured but I am unable to find any error logs. Anyone? ___
Best Regards,
Felix Ker
Mobile +65-91456635 Email felix@ker.sg
*IMPORTANT* Find out the best ways to get my attention: http://protocol.by/felixker/
Hi Felix,
On 6/4/12 6:51 AM, Felix Ker wrote:
I'm trying to use TorStatus and it took me almost 2 hours to set everything up and able to run tns_update.pl smoothly with no error. However, I am facing a problem that Google cannot help me.
[0] starting... [0] mirror? [0] connecting to Tor [0] authenticating with Tor [0] starting descriptions *The TorStatus database was not updated properly. An error has occured. I will continue to try to update, however.*
It says an error has occured but I am unable to find any error logs. Anyone?
TorStatus is, AFAIK, not maintained anymore. But we developed Onionoo [0] and Atlas [1] as a TorStatus replacement. Onionoo provides Tor status information in a JSON format and Atlas presents these data in a nice human-readable format. You could set up an Atlas mirror (which only serves static content, because the heavy lifting is done via JavaScript on the client) using the current Onionoo host as data source or you could mirror both Onionoo and Atlas. Happy to give you advice how to set up Onionoo. Bug reports, feature suggestions, and of course patches would be highly appreciated.
Best, Karsten
Hello Karsten
Thank you for sharing! Looks like there's too little information about how Atlas can be used to list the servers. Would you be able to share any documentation?
___
Best Regards,
Felix Ker
Mobile +65-91456635 Email felix@ker.sg
*IMPORTANT* Find out the best ways to get my attention: http://protocol.by/felixker/
On Mon, Jun 4, 2012 at 2:04 PM, Karsten Loesing karsten@torproject.orgwrote:
Hi Felix,
On 6/4/12 6:51 AM, Felix Ker wrote:
I'm trying to use TorStatus and it took me almost 2 hours to set
everything
up and able to run tns_update.pl smoothly with no error. However, I am facing a problem that Google cannot help me.
[0] starting... [0] mirror? [0] connecting to Tor [0] authenticating with Tor [0] starting descriptions *The TorStatus database was not updated properly. An error has occured.
I
will continue to try to update, however.*
It says an error has occured but I am unable to find any error logs.
Anyone?
TorStatus is, AFAIK, not maintained anymore. But we developed Onionoo [0] and Atlas [1] as a TorStatus replacement. Onionoo provides Tor status information in a JSON format and Atlas presents these data in a nice human-readable format. You could set up an Atlas mirror (which only serves static content, because the heavy lifting is done via JavaScript on the client) using the current Onionoo host as data source or you could mirror both Onionoo and Atlas. Happy to give you advice how to set up Onionoo. Bug reports, feature suggestions, and of course patches would be highly appreciated.
Best, Karsten
On 6/4/12 8:40 AM, Felix Ker wrote:
Thank you for sharing! Looks like there's too little information about how Atlas can be used to list the servers. Would you be able to share any documentation?
Do you mean how Atlas can be used to display a list of the current relays and/or bridges rather than providing a search function?
A full list of relays was practical when there were 300 relays in the Tor network. It isn't practical with the current 3000 relays and 1000 bridges, nor will it become any more practical when the Tor network grows to 30000 relays and 10000 bridges. The main reason why having a full list is useful is that browsers has better search functionality than the website. We should rather go fix that and have the website provide good search and sorting functions.
There's a new function in Onionoo that allows clients to use "order," "offset," and "limit" parameters [0] that can be used to display ordered, paged results. Atlas doesn't use these parameters yet, but it could do so in the future. If someone wants to add that feature, be sure to talk to Arturo about the design; he may already have ideas for supporting paged results.
Or did you mean something else?
Best, Karsten
[0] https://onionoo.torproject.org/, scroll down to "Methods" section
On 6/4/12 8:04 AM, Karsten Loesing wrote:
TorStatus is, AFAIK, not maintained anymore. But we developed Onionoo [0] and Atlas [1] as a TorStatus replacement. Onionoo provides Tor status information in a JSON format and Atlas presents these data in a nice human-readable format. You could set up an Atlas mirror (which only serves static content, because the heavy lifting is done via JavaScript on the client) using the current Onionoo host as data source or you could mirror both Onionoo and Atlas. Happy to give you advice how to set up Onionoo. Bug reports, feature suggestions, and of course patches would be highly appreciated.
Best, Karsten
I would suggest to rewrite onionoo in Python on the basis of STEM (or extension of txtorcon):
https://gitweb.torproject.org/stem.git by atagar
It now have extensive parsers for Tor's cached-consensus i think it may quickly provide the REST interface that Atlas need: https://gitweb.torproject.org/stem.git/blob/HEAD:/stem/descriptor/server_des... https://gitweb.torproject.org/stem.git/blob/HEAD:/stem/descriptor/extrainfo_...
That way you can have a "single package" with Python App + Atlas, without the overhead of Java given by onionoo.
Felix, consider also if you have time and it match your goals, to try to write a self-contained windows/osx application using APAF (Anonymous Python Application Framework http://github.com/mmaker/APAF ) merging Atlas+Server-Python-Code for a Desktop application bundling Tor .
-naif
On 6/4/12 8:47 AM, Fabio Pietrosanti (naif) wrote:
I would suggest to rewrite onionoo in Python on the basis of STEM (or extension of txtorcon):
https://gitweb.torproject.org/stem.git by atagar
It now have extensive parsers for Tor's cached-consensus i think it may quickly provide the REST interface that Atlas need: https://gitweb.torproject.org/stem.git/blob/HEAD:/stem/descriptor/server_des... https://gitweb.torproject.org/stem.git/blob/HEAD:/stem/descriptor/extrainfo_...
I agree that somebody should rewrite Onionoo in Python. I expect that to take a few months though. I'm going to keep maintaining the Java Onionoo until we have a stable and maintained Python replacement. I'm happy to guide people through the tricky parts of writing an Onionoo kind of thing.
For example, being able to parse Tor descriptors is a great start for writing a Python Onionoo. But you'll also have to aggregate bandwidth data in an efficient way. The Java Onionoo uses flat files to store bandwidth data and aggregate them more the higher they lie in the past. That code [0] wasn't exactly trivial to write, and it's also not the most beautiful piece of code I ever wrote. But it's efficient, which is key. Of course, you could start by porting the Java code 1:1 to Python and think about optimizations later.
That way you can have a "single package" with Python App + Atlas, without the overhead of Java given by onionoo.
I'd prefer keeping the (Python) Onionoo and Atlas in two distinct packages. Or rather, the REST interface should stay as open and independent from Atlas as it is now. The Atlas website isn't the only client that could use Onionoo's data. Think of non-JavaScript-based websites that cache Onionoo data rather than letting the client do all the work, mobile clients, Vidalia/arm extensions, tray icons, social network site plugins, command-line tools, etc.
Best, Karsten
[0] https://gitweb.torproject.org/onionoo.git/blob/HEAD:/src/org/torproject/onio...
-
Fabio Pietrosanti (naif) -
Felix Ker -
Karsten Loesing