aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Socket blocking errors  (Read 2088 times)

JLP

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 22
    • http://jlp.holodeck1.com/blog/
Socket blocking errors
« on: January 08, 2005, 08:25:46 PM »
I just compiled aMule 2.0.0rc8 on 64-bit Gentoo Linux machine and when I enable verbose mode I get a lot of errors like

08. 01. 2005 20:31:08: An unnamed client (IP:24.23.213.54) caused a socket blocking error. Retries: 0. Trying to reconnect... (retries left: 2)
08. 01. 2005 20:31:08: An unnamed client (IP:172.181.71.22) caused a socket blocking error. Retries: 0. Trying to reconnect... (retries left: 2)

in the log window.
Logged

deltaHF

  • Evil Admin
  • Former Developer
  • Hero Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 3920
  • .. Legends may sleep, but they never die ..
    • http://www.amule.org
Re: Socket blocking errors
« Reply #1 on: January 08, 2005, 08:30:16 PM »
don't worry about.. disable verbose and everything will be ok again.
verbose is only for devs (no idea why we still have it there), the msgs are normal and verbose will eat all your CPU and MEM after some time

cheers
« Last Edit: January 08, 2005, 08:58:42 PM by deltaHF »
Logged

Xaignar

  • Admin and Code Junky
  • Hero Member
  • *****
  • Karma: 19
  • Offline Offline
  • Posts: 1103
Re: Socket blocking errors
« Reply #2 on: January 08, 2005, 08:30:32 PM »
It's not an error, it's just extra debugging output. Hence the name "verbose". ;)
Logged

JLP

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 22
    • http://jlp.holodeck1.com/blog/
Re: Socket blocking errors
« Reply #3 on: January 08, 2005, 08:31:38 PM »
OK then. I just posted this just in case if there could be something wrong. It these are normal then OK.
Logged