3 Jan 2005 14:48
Naturally
jrandom will be the judge for the 'working' part.
eco
4 Jan 2005 21:54
weekly status notes [jan 4]
Hi y'all, time for our first weekly status notes of 2005 * Index 1) Net status 2) 0.4.2.6 3) 0.5 4) jabber <at> chat.i2p 5) ??? * 1) Net status Over the last week, things have been pretty interesting on the net - on nye, there were some comments posted to a popular website talking about i2p-bt and we've had a small burst of new users. At the moment there are between 120-150 routers on the net, though that peaked at 160 a few days ago. The network held its own though, with high capacity peers picking up the excess load without much disruption to other peers. Some users running without bandwidth limits on really fast links have reported throughput of 2-300KBps, while those with less capacity use the usual low 1-5KBps. I think I remember Connelly mentioning that he was seeing 300+ different routers over the course of a few days after new years, so there has been significant churn. On the other hand, we now have a steady 120-150 users online, unlike the previous 80-90, which is a reasonable increase. We still do *not* want it to grow too much yet though, as there are known implementation issues that still need to be done. Specifically, until the 0.6 release [1], we're going to want to stay below 2-300 peers to keep the number of threads at a(Continue reading)
6 Jan 2005 17:45
0.4.2.6 is available
Hi y'all, time for a new update The 0.4.2.6 release has a whole slew of bug fixes, reliability improvements, and bundles Ragnarok's addressbook as a client application. The release is backwards compatible and should not be too disruptive, so upgrade when you get the chance. As mentioned in the weekly status notes [1], the addressbook essentially just automates the anonymous fetching and merging of hosts.txt files from locations of your choosing (defaults being http://duck.i2p/hosts.txt and http://dev.i2p/i2p/hosts.txt). More details can be found on Ragnarok's site [2], and the source is in cvs [3]. If you don't have the addressbook installed already, you have no additional work to do. However, if you previously installed the addressbook and manually wired it to run in your router (through the lines in clients.config and a reference to the .jar file in wrapper.config), you will need to remove those. Existing addressbook configuration and data files will be honored if they are located in the default addressbook/ directory. [1] http://dev.i2p.net/pipermail/i2p/2005-January/000541.html [2] http://ragnarok.i2p/ [3] http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/apps/addressbook/ Anyway, thats that. The full list of updates in the release can be found in the usual place [4], and upgrading uses the same process as before [5].(Continue reading)
6 Jan 2005 18:07
6 Jan 2005 18:29
Re: 0.4.2.6 is available
> Is there any reason why eepsite/jetty.xml is still being bundled in > i2pupdate.zip? Generally, to keep me from maintaining a big matrix of upgrade scripts. Anyone with anything since 0.4.0.1 could use the same i2pupdate.zip, and users with revs prior to 0.4.1 needed the jetty.xml. Since 0.4.1 was 3 months ago, its probably safe to tell them to do a clean install if they haven't been keeping up. I'll remove jetty.xml from future updates though, good catch. =jr
6 Jan 2005 22:13
i2p 0.4.2.5-0 quit unexpectedly
Hello i2p,
was running i2p on wlan, then did gracefull shutdown, reconnected to
the internet via lan, started i2p, everything seemed normal, after
some time, I fond that it wasn't running anymore.
last lines in log:
20:38:59.013 CRIT [hutdown hook] net.i2p.router.Router : Shutdown(2) complete
java.lang.Exception: Shutdown
at net.i2p.router.Router.shutdown(Router.java:668)
at net.i2p.router.Router$GracefulShutdown.run(Router.java:735)
at java.lang.Thread.run(Unknown Source)
at net.i2p.util.I2PThread.run(I2PThread.java:64)
20:38:59.013 CRIT [hutdown hook] net.i2p.util.LogManager : Shutting down logger
if you think it is not normal, I will be glad to send you a full log
file.
--
--
Best regards,
mailto:ebolarulez@...
6 Jan 2005 23:02
Re: i2p 0.4.2.5-0 quit unexpectedly
> Shutdown(2) complete Hmm, the 2 means (cryptically) that it was shutdown gracefully. Did you wait the 11-ish minutes after hitting graceful shutdown before switching from the WLAN to the LAN? If you didn't shut down the router after it restarted, then it must not have written to the log any further, perhaps the disk was full, or it had other problems starting up? If this does recur, please let me know and we can debug through the logs further. =jr
7 Jan 2005 00:25
Proxy services not starting
I successfully upgraded to version 0.4.2.6, but am having trouble starting the HTTP and IRC proxies. When I go to http://127.0.0.1:7657/i2ptunnel/index.jsp and click the "start" link for either proxy, I see the following error message. Error starting up the tunnel - Invalid manager class [net.i2p.client.streaming.I2PSocketManagerFull] - not found What is causing the problem, and will reinstalling I2P completely help?
7 Jan 2005 00:58
Re: Proxy services not starting
> Error starting up the tunnel - Invalid manager class > [net.i2p.client.streaming.I2PSocketManagerFull] - not found > > What is causing the problem, and will reinstalling I2P completely help? Yes, though the root cause is from an old wrapper.config. Could you add the following to your wrapper.config: wrapper.java.classpath.21=lib/streaming.jar A graceful restart after that should do the trick. hth, lemmie know if it doesn't. =jr
9 Jan 2005 22:21
"Just Installed" and Graceful Shutdown
Two things: 0) What do you call the page/site that exists at localhost:7657? 1) The "Congratulations on getting I2P installed!" message on the router page is increasingly inappropriate as time goes on. What is the current mechanism by which that HTML is updated and maintained? If I wanted to contribute to this, where would I start? 2) I just noticed a message on localhost:7657 that I haven't seen before. At the top it says, "Graceful shutdown in 1h". What does that mean, other than the obvious? Why is my router shutting down in 1 hour, and will it come back up? I have an uptime of 61 hours. I just dropped the latest i2pupdate.zip in and initiated a graceful restart. When I refresh, it still says 0.4.2.5. Is it really taking an hour to politely extract from the conversation so it can go do its business? (I spent last night at a cocktail party of sorts.) I figured a graceful restart would take only several minutes. Ten, maybe. Just trying to learn a few I2P concepts... -todd
RSS Feed