aMule Forum

English => aMule Help => Topic started by: lumi on February 19, 2012, 01:16:02 PM

Title: How to diagnose problem with UDP?
Post by: lumi on February 19, 2012, 01:16:02 PM

Hi,

  I run aMule for a long time without problems, I didn't change configuration - not amule, not firewall, not nothing. The only possibility is, I upgraded some system library (like glibc).

  And from some time (2-3 weeks) out of the blue I get this error when starting aMule:

Code: [Select]

MuleUDPSocket.cpp(77): MuleUDPSocket: Failed to create valid Server UDP-Socket
and later (I don't know if related or not):

Code: [Select]

2012-02-19 13:07:08: UPnPBase.cpp(945): Universal Plug and Play: UPnP Error: CUPnPControlPoint::AddPortMapping: WAN Service not detected.
There is no more info, or error reason given. I get connected, highID, transfer is OK, etc. but without UDP this is only TCP in action.

It is the latest version of aMule (2.3.1), how can I diagnose what is the reason of this error?

Thank you!

Title: Re: How to diagnose problem with UDP?
Post by: Stu Redman on February 19, 2012, 05:25:12 PM

Try a few different UDP ports, that's my best guess. There is no error message available here.

Title: Re: How to diagnose problem with UDP?
Post by: lumi on February 19, 2012, 05:55:32 PM

Thank you, this is completely crazy, but it worked.

Is there any possibility, that dying (crashing) aMule can somehow "lock" given port, and when I later run it again (I have uptimes of the system ~ a month) the "lock" is preserved and aMule cannot use this port again?

I am asking, but now it hit me -- when trying to solve this issue I've googled and I read the about the problems when running several instances on the same computer. Maybe remains of aMule + aMule somehow are in clash when it comes to the UDP ports?

If not this, for me it seems like pure magic :)

Title: Re: How to diagnose problem with UDP?
Post by: Stu Redman on February 19, 2012, 07:47:06 PM

Well, a reboot sometimes does magic.  :D
Not so much in Linux as in Windows, but it's sure possible that some effect somehow locks a port in your OS. If you never rebooted since the problem occurred that's the most probable solution.

Title: Re: How to diagnose problem with UDP?
Post by: lumi on February 19, 2012, 10:36:48 PM

My OS is Linux, don't know how about Windows, but in Linux you don't have to restart computer every day, and it would be great to keep it that way.

Anyone, one such "accident" per several years is rather miniscule problem but if you by any chance spot a way to handle better those port locks, it would be great - thank you in advance.

Title: Re: How to diagnose problem with UDP?
Post by: lumi on February 19, 2012, 10:37:44 PM

PS. I is not that I am too lazy to reboot machine, it is when you run server it is not very applicable.

Title: Re: How to diagnose problem with UDP?
Post by: Stu Redman on February 20, 2012, 10:45:59 PM

It's rather a problem of your OS if it keeps resources locked after their process terminates.
Anyway, just one of the glitches you get when working with computers.  :)

Title: Re: How to diagnose problem with UDP?
Post by: stoatwblr on March 03, 2012, 06:13:20 PM

I've seen this kind of behaviour in the past.

Such reservations should expire after 10 minutes at most.