Opened 10 years ago
Closed 9 years ago
#460 closed defect (fixed)
wrong log level for eep proxy connections
Reported by: | sponge | Owned by: | sponge |
---|---|---|---|
Priority: | minor | Milestone: | 0.8.12 |
Component: | apps/i2ptunnel | Version: | 0.6.31 |
Keywords: | Cc: | ||
Parent Tickets: | Sensitive: | no |
Description
Error level is too high for connections that don't work on the eep proxy. Here is an example, from bidir's proxy. Not sure if the same level is in the eep-proxy as well.
ERROR [7.0.0.1:7658] unnel.I2PTunnelHTTPBidirServer: Error connecting to HTTP server /127.0.0.1:7658 java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at java.net.Socket.connect(Socket.java:478) at java.net.Socket.<init>(Socket.java:375) at java.net.Socket.<init>(Socket.java:218) at net.i2p.i2ptunnel.I2PTunnelHTTPServer.blockingHandle(I2PTunnelHTTPServer.java:126) at net.i2p.i2ptunnel.I2PTunnelServer$Handler.run(I2PTunnelServer.java:374) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)
Perhaps the log level should be INFO, not ERROR, as it's not a major issue, and a transient error
This has been an issue since for as long as I can remember.
Subtickets
Change History (3)
comment:1 Changed 10 years ago by
Milestone: | 0.8.6 → 0.8.9 |
---|---|
Owner: | set to sponge |
Status: | new → assigned |
comment:2 Changed 9 years ago by
Status: | assigned → accepted |
---|
Tunnel is open before jetty got the chance to start, that's why it happens…
And you are correct, that is on the inbound, I'll still fix this on the bidir tunnel.
comment:3 Changed 9 years ago by
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Changed warning level for the first 3 minutes to WARN.
Note: See
TracTickets for help on using
tickets.
This is not an outgoing client eep proxy error, it's an incoming server error. I2PTunnel can't connect the HTTP server at port 7658. Why is it transient? The local web server isn't responding.
So I don't see why it should be less than ERROR.
Assigning to you for further explanation or to close it.