Opened 9 years ago

Closed 8 years ago

#307 closed defect (worksforme)

Unable to create socket manager

Reported by: manijay2001@… Owned by: zzz
Priority: major Milestone: 0.8.3
Component: api/data Version: 0.8.1
Keywords: Cc:
Parent Tickets:

Description

Hello,

I posted to the Technical Problems forum. The recommendation was to raise a ticket.

Below is a summary of the problem as I understand it;

when I attempt to go to any .i2p site I get the error message 'Proxy Server Refused Connection'

The browser I am using is Firxfox 3.0.1.0

I've configured the HTTP and SSL as instructed on http://www.i2p2.de/htproxyports.html.

I2P version: 0.8.1-0
Java version: Sun Microsystems Inc. 1.6.0_21 (Java(TM) SE Runtime
Platform: Windows XP x86 5.1

The Router Console does show http://127.0.0.1:7657/index.jsp.

Looking at the Router Console left hand side, I can see 'Network: Firewalled'.

Having said that, I can see

Peers
Active: 33 / 134
Fast: 16
High capacity: 35
Integrated: 30
Known: 603

Bandwidth in/out
1s: 1.10 / 0.70KBps
5m: 0.81 / 1.40KBps
Total: 0.77 / 0.87KBps
Used: 26.97MB / 30.79MB

Tunnels
Exploratory: 4
Client: 11
Participating: 2
Share ratio: 0.06

Congestion
Job lag: 2ms
Message delay: 630ms
Tunnel lag: 2091ms
Backlog: 0

I've attached:
Router Logs
Service (Wrapper) Logs
Critical Logs

Please let me know if I need to send any more information.

Many thanks
M

Subtickets

Attachments (3)

Critical Logs.txt (4.7 KB) - added by manijay2001 9 years ago.
Critical Logs
log-router-1.txt (4.7 KB) - added by anonymous 9 years ago.
log router
wrapper.txt (23.2 KB) - added by manijay2001 9 years ago.
wrapper log

Download all attachments as: .zip

Change History (6)

Changed 9 years ago by manijay2001

Critical Logs

Changed 9 years ago by anonymous

log router

Changed 9 years ago by manijay2001

wrapper log

comment:1 Changed 9 years ago by zzz

  • Milestone set to 0.8.2
  • Owner set to zzz
  • Status changed from new to assigned
  • Version changed from 0.8 to 0.8.1

thanks for the extra info.

java.lang.OutOfMemoryError? is real bad. But that error is after the Socket Manager errors so I'm not sure if it is a cause or a symptom.

Still not really enough to go on, unfortunately. I've tried to enhance the logging of errors in dev build 0.8.1-3. That may help diagnosis.

Were you running a lot of torrents in i2psnark, or are there other reasons for running out of memory?

Has it happened again since you restarted?

comment:2 Changed 8 years ago by zzz

  • Milestone changed from 0.8.2 to 0.8.3

If you can run a development build from echelon.i2p (0.8.1-3 or higher), the logging is improved there so I may be able to diagnose the problem. Unfortunately if the i2ptunnel tunnels won't start at all you probably can't do that.

Sorry I am out of ideas at the moment.

comment:3 Changed 8 years ago by zzz

  • Resolution set to worksforme
  • Status changed from assigned to closed

no response, closing ticket. Please reopen if you have get more log info with a 0.8.2 or 0.8.3 router.

Note: See TracTickets for help on using tickets.