aMule Forum
English => Multiplatform => Mac OSX => Topic started by: Gomaaz on June 17, 2005, 10:16:23 PM
-
Good evening everybody,
I think I found some strange behavoiur in the new 2.0.3 Version of Amule..
First of all I'm a Mac user (tiger 10.4.1) and installed the mac binary of the new Version. After startup I got a low ID...worried me, because I got needed Ports forwarded. So I changed some server to see if it has any affect...some server were ok with High ID.
So I didn't think more about it and had let him run overnight. But as I was looking for the speed...it were on "0 KB/sec" upload "20 KB/sec". The same speed as the night before and all day long.
Now I started 2.0.2 and see....it works perfect ...on all servers I got a high ID and acceptable rates
Something did wrong by building a new version? ?(
I dunno but first, I will stay with 2.0.2
thanks
-
hmm the same effect is on 2.0.2 so it can't be the versiondifference ?(
-
I have the same error!!!
exactly as you describe it.
I even thought my isp was blocking my ports because of the high trafic I've been changing the ports amule uses I whent from 4662 to 26500 to 60000, whenever I changed ports and restarted amule I got my high ID back, but after 1 or 2 hours bang very low dls (very very low like 3 and 4 KB) again, and with a simple reconect to a server I could see that I now had lowID AGAIN.
What I've now learned is that it isnt a port thing cuz whenever I have the problem I just restart amule with the same port that was giving me lowID and I have HighId back.
Can someone plz point uz where to put this thread to have more visibility, cuz this is a MAJOR bug.
tnx
g.
ps I have an ImacG5 20" MacOSX 10.4.1
EDIT: I an sure I have my router (nat and firewall) configured, Its not a server thing cuz I've tryed to conect to a lot of diferent servers, and its not my isp who is blocking my ports cuz I've tryed a lot of ports.
-
I don't think this is a router/firewall issue at all. It appears to be more Tiger (10.4) related.
I have noticed on other forums that people, using similar programs like mlnet and xDonkey, are getting the same High/Low id problem. The one thing they all have in common is that they are running OSX 10.4.1.
I am now getting the same problem as you with the strange id behaviour and it only started after I upgraded from 10.3.9 to 10.4.1 on the weekend.
-
I am sure it's not aMule bug and I agree this must be a Tiger problem.
-
Jesus if its a Tiger problem then we are all depending on Apple? what if it isnt fixed with 10.4.2?
aaa man I'm soo depressed.... I only have one week of unlimited bandwidth left :(
Gomazz please post here if you find any solution on any other Forum, I will search too.
-
strange....because 2.0.0 and above until 2.0.2 it worked perfect
I'lett you know here when I find something useful to solve that prob
PS: It really can't be a prob of firewall etc. I've tested the ports on some ways and were always open
amule 2.0.2 even don't work ?( and I don't want to go back to mldonkey (shit behaviour with tempfiles) I just hate it.
Amule is/will be good :baby:
Cu then :))
-
humm would it take any solving-effect when I compile amule by myself? ?(
-
Try.
-
hmhm ok I'll try *readsthemanual* :P I will report
-
I'll but a Tiger build to see if it helps :)
Hello grgasca! I am friendly!
-
Compiling on tiger doesn't solve the prob -_- or I compiled wrong what I don't believe :(
let's hope for a magic wonder ;(
-
I'll but a Tiger build to see if it helps :)
please I beg you :baby:
Hello grgasca! I am friendly!
Well now I know. :rolleyes:
I've confirmed that peoplle using mldonkey have the same problem with diferent versions of their client giving diferent times of loosing the highId. Thats why I think that maybe a Tiger compiled version of aMule could do the trick.
Their workaround as lame as it might be is too run a script to close and relaunch their client in a certain interval of time to keep the highId. Its the only thing we can do for now.
-
not for me... X( let's hope Kry or other developer get luck in this :baby:
-
no news?
-
Don't think so grgasca...my Amule has alived on the same server as the night before...where I am happy about
But it's still soo slow :/ think I will set the hardlimit and max connections to lower values....we'll see
So Selfcompiled CVS doesn't solve the prob....so what to do ? :(
-
edit: nothing has changed...the prob just happened again 8o
-
I just realized I can't compile in Tiger. Will anyone please PM a ssh connection to a Tiger box? ;)
-
hum? I can compile on Tiger
U just have to edit 2 strings in the ExternalConnector.cpp if u got errors(thanks to Ken in this case) :
u have to change row 54 and 66 into this:
row 54: extern "C" char *readline (const char*);
row 66: extern "C" void add_history (const char*);
-
Finally I got a solution for this Prob....not really cool but amule works now
U have to downgrade to 10.4.0 to get amule to run.. 8o
it's not really the best way but try to insert your tiger cds and keep your old username...then install the system
Some new stuff in the update of 10.4.1 is built in which amule can't argue with...hope your getting more happier this way :/
sry (let's hope 10.4.2 will bring more success) :(
-
U have to downgrade to 10.4.0 to get amule to run..
That suxs. :(
I hope 10.4.2 fixes things, otherwise aMule (and mldonkey) will die out on the mac platform.
-
If so I will stay on 10.4.0 forever :D
-
Hi there everyone,
Was wondering if there was any news on this issue.
I have recently discovered aMule (and am an extremely happy bunny as a result), having been an edonkey2000 user since they released their mac client.
I am so so so happy that there is finally an eMule-derived product for OS X, one that gives us the options and the interface that we need.
I have only been running it for a week but seemed to have noticed the same problem you were talking about. When I start off and have a HighID, I get very good speeds (50k min and up to 160k...)
But after a while (haven't quite figured out how long yet) my ID changes to Low and my speed go down...
Can anyone still confirm that this is a Tiger 10.4.1 issue (which i am running), has anyone found any solutions to this problem as it stands ??? Or do we just have to keep quitting an restarting every now and then ??
Thanks in advance.
-
Can anyone still confirm that this is a Tiger 10.4.1 issue (which i am running)
Yes, Ken does ! :)
has anyone found any solutions to this problem as it stands ???
no..or downgrade to 10.4.0
Or do we just have to keep quitting an restarting every now and then ??
That's what you can but I wouldn't recommend it (downloads will never be done -_-)
-
mac os x 10.4.2 is just released!!
anyone who wanna try :] ?
I think I'll do it
-
with 10.4.2 the prob seems to be solved 8o I'll wait another few hours to see if it is really so. Otherwise apple reported improved performance in the tiger update for third-party-applications
so it has to be solved :rolleyes:
-
Well, I have been running under 10.4.2 for about 12 hours now and no strange ID problems. (It used to occur after 3-4 hours under 10.4.1).
So it looks like the problem has been fixed!!!!
-
not here.
Updtated this morning and had to restart the amule 3 times.
I Noticed no dl after 2-3 hours. still full sources but averytime i reach the last position in the remote queue i'm booted.
No significant msg form the log until i try to connect to other servers.
On launch it connects at light speed to Razor, as soon as itry to connect to another server when i advice the dtop of the downloads i'm unable to join the server.
Dual G5, 10.4.2
(yesterday i made an archive instal of Tiger and this morning the upgrade)
-
gomaaz & gnaf: do you still don't experience the problem under 10.4.2?
-
still problems here after many days of testing
-
hmm no probs here ?( pretty strange your problem
-
Mars_Artis, could you do a couple of things that may help us figure out what's going on?
When aMule stops downloading and gets low-id, don't quit it. Instead, please do the following:
Important: for all the following steps, replace "4662" with your aMule TCP port number.
- Run the Terminal program in /Applications/Utilities
- In Terminal, type this command: netstat -aLp tcp | grep -w 4662
- Then type this: netstat -ap tcp | grep "\*\.4662"
- Then type this: telnet localhost 4662
The telnet program will either report an error or it will tell you it has connected. If it connects, it will tell you what the "escape character" is. It will probably be "^]". That means Ctrl-]. Type that character and then type "quit" at the "telnet> " prompt.
- Copy the output from those commands and post it to this thread.
- Now, you can quit and restart aMule if you like. You can also quit Terminal.
Thanks for your help.
-
I have the same problem...
When i start Amule i get high id for about 2 to 3 hours then i get disconnected and when i reconnect i always get low id...
This is the results i get in the terminal:
Last login: ************** on console
Welcome to Darwin!
bl6-67-152:~ ******$ netstat -aLp tcp | grep -w 4662
8/8/5 *.4662
bl6-67-152:~ ******$ netstat -ap tcp | grep "\*\.4662"
tcp4 0 0 *.4662 *.* LISTEN
bl6-67-152:~ ******$ telnet localhost 4662
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Operation timed out
telnet: Unable to connect to remote host
bl6-67-152:~ ******$
-
guys, i have a feeling that the problem is not restricted to 10.4.1. :(
i've installed tiger a couple days ago and now i am experiencing the same problem under 10.4.0.
right now, amule (2.0.3) has been running for 20h and is still uploading and connected to razorback. but when i try to connect to its tcp port through the connection tester (http://www.preinheimer.com/cgi-bin/connectiontest/connectiontest2.cgi) i get a firewalled warning. in a couple of hours, upload will break down as well.
netstat & telnet give me exactly the same output that matreco has posted.
i'll do some more testing...
-
Ok mates here it's what i get from terminal:
Mars-G5:~ mars$ netstat -aLp tcp | grep -w 17672
8/8/5 *.17672
Mars-G5:~ mars$ netstat -ap tcp | grep "\*\.17672"
tcp4 0 0 *.17672 *.* LISTEN
Mars-G5:~ mars$ telnet localhost 17672
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Operation timed out
telnet: Unable to connect to remote host
Mars-G5:~ mars$
For me too making the port test as above gives firewalled error
I'll stay tuned for infos.
P.S.
I wanan add this: i did try to downgrade to Tiger 10.4.0 before the up to 10.4.2 And i did notice the some issue. No benefit at all
-
OK, thanks for the reports, guys. Unfortunately, there's no smoking gun.
The next step, I think, is for me to put diagnostic print-out statements throughout the wxMac and aMule code which deals with listening for and accepting connections. I'll supply patches to lionel77, and he and I will run some tests.
I'm also open to suggestions from the gallery. ;)
-
Can't believe it ! The prob just happened again with 10.4.2
God help us all ;(
-
i'm "glad" to hear that -- everybody else i know is experiencing the issue and it was really puzzling to me why the two of you apparently did not.
btw, you can track the accumulation of stuck connections with the "netstat -aLp tcp | grep -w 4662" command. right after you started amule the output should be "0/0/5 *.4662". then, as connections get stuck the first two numbers will increase successively. eventually you will get "8/8/5 *.4662", which is when the problem becomes visible in terms of low ids from servers and in terms of reduced download performance and eventually upload performance.
ken and i, did some extensive testing and we are pretty confident that the problem is located below amule and wx. out of curiosity, i installed mldonkey again to test whether it is suffering from the same limitations and it is. mldonkey is compiled with a maximum of 20 stuck connnections instead of 8, so it takes a bit longer until you can actually see the problem without using netstat, but it is definitely there.
so what's next? ken is trying to devise a small program/script that demonstrates the issue of stuck connections, so we are able to file a precise bug report with apple. there is also a chance that apple is already aware of the issue since it is not unlikely that other types of programs beside p2p apps are affected by this issue as well. so if we are lucky, 10.4.3 might solve our problems...
if everything else fails i am thinking about providing people with a modified amule setup: i've compiled wx to provide amule with a queue of 20 connections instead of 8, which delays the onset of the problem. to avoid getting stuck, i have written a small script that shuts down amule regularly via amulecmd and then restarts it. it's not a very clean solution but it might be better than nothing until apple fixes their sockets.
-
hi first of all,
thank you for spending time in our problem ;)
but I think the shutdown and restart script isnt a good solution because emule network needs time to connect, to stay in queues and so on .
so we'll have to be depend on apple for a real fix? :(
-
i fully agree. restarting amule every couple hours is not a good solution. this is really just an emergency plan.
however, i am relatively confident that you don't lose your queue position if you restart amule and connect to a source again in time. the only problem is that you might be downloading a number of popular files with many sources, then you won't be able to reconnect to all sources in time to maintain your queue positions.
i hope we get this thing fixed soon so we don't need plan b. i still remember running mldonkey using a similar script before the devs fixed a bug that caused problems with os x 10.2. with the constant restarts mldonkey worked somehow, but it wasn't that great.
-
heres a better way:
Put in the tiger installation disk
- boot from cd
- reinstall tiger (in the options you can click on "save users and network settings"
- reupdate to the newest version of tiger
after restarting amule seems to work fine now. All in all it spends a time about 40 mins.
but amule works....for a while :]
-
amule is quitting after 30mins automatically
I'll shutdown amule now for a while :(
-
Gomaaz:
I don't think reinstalling tiger does anything. And most importantly, if you want to test whether the stuck connections problem is present or not you really need to use "netstat -aLp tcp | grep -w 4662" as described above. Just observing amule is not enough.
I'm very sure that the problem was always present on your machine since you first updated to tiger, even at those times when you thought it wasn't. For some reason the rate of connections getting stuck might have been lower at times so that the problem was there latently but you didn't experience it b/c the socket was not completely stuffed.
-
So, did anyone came up with a solution other than reverting to a previous version of the OS? I too have the same problem with Mac OS X 10.4.2 and aMule 2.0.3: It connects in an instant with High ID, performs nicely for several hours, the it looses connection and upone reconnecting all I got is a Low ID. And running "netstat -aLp tcp | grep -w 4662" also returns "8/8/5 *.4662" (both when connected with a High ID and Low ID, though), whatever that means.
Is someone NOT suffering from this with the same software set up?
-
A quick update:
It looks like there are a few people who accumulate stuck connections at a very low rate (1 per 2 days or so). My guess is that this is because of their particular setup (e.g. router, ISP or something along those lines).
I have patched wx now to allow for 193 stuck connections instead of the default 8. This delays the onset of the stuck connection effect tremendously. I've had different test versions running here without any apparent problems because of this modification.
I am in the process of preparing a binary to be posted here. However, I want to make sure that this version works well (both on 10.3 and on 10.4), so I need a few days more of testing.
-
lionel77, could you please post or tell about the patches you did to wxWidgets? I certainly would like to try these on my CVS version of aMule. It seems the stuck connections are gone on my Tiger system as of CVS_2005-09-08.
-
badjob, did you check the number of stuck connections using netstat as described above? maybe you are just not reaching the limit for the problem to surface.
amule cvs has not been working with 10.3 for a while now (a number of weeks?) -- it crashes on average every 3-10 hours. i've posted a couple of backtraces but the problem has not been fixed yet.
originally, i was planing to release a binary that would work on both 10.3 and 10.4 but i'm starting to think i should just go ahead and post a patched 10.4-only binary.
if everything goes well you can expect that binary within 24h.
-
lionel77,
some time ago aMule always stopped working after some hours as some other people wrote in this forum. I got a lowid after some time and had stuck connections (Mac OS X 10.4.2).
Right now I'm running wx2.6.1 and aMule CVS head with major custom GUI patches (mine). No networking code was touched. I built the binaries with gcc4 with --disable-optimize --enable-debug and omitted the stripping.
No problems at all while having 50 up to 300 concurrent connections on average, depending on how much stuff I shared. This was for the standard monolithic GUI client.
Didn't use 10.3 on my main system since release of 10.4.
So a binary wouldn't help me that much, because of my custom GUI patches (some refinements), which I would gladly share in a couple of days when they are finished if someone is interested.
-
Hi,
Is there some news about the $@# problem concerning amule stopping using High ID after a given period of time ?
I'm using daily sources of amule cvs, build against wxMac-2.6.1 on Tiger 10.4.2 and i have to stop then restart amule each and every hour or so (when i have a High ID, ie on each start, the download rates are rather good).
I remember old versions of mlnet suffering of such a problem, but with a different effect: mlnet freezed and we had to kill the process to restart it again. I remember a script which periodically checked connexions and restart automatically mlnet if necessary. Could it be the same problem here ?
-
@badjob:
Again, just because you haven't reached the point where no more new connections are accepted does not mean you are not affected. Run amule for 2 days and then use netstat as described above. I would be surprised if you had no stuck connections by then.
The patch is rather simple. Open wxWidgets/src/unix/gsocket.gpp and go to line 533. It should look something like:
(listen(m_fd, 5) != 0))change it to (listen(m_fd, 128) != 0))128 is the maximum allowed and it will result in amule tolerating up to 193 stuck connections.
Looking forward to your GUI patches... :)
@davenull:
The problem is that it is the underlying low-level os code that is causing the trouble. There is not much we can do about it, except for coming up with work-arounds like increasing the limit for stuck connections.
EVERY single p2p app I've tried so far is affected by this. They only differ in the time it takes until the problem surfaces. Mldonkey for instance tolerates 31 stuck connections per default while an unpatched amule tolerates only 8. Azureus (a BitTorrent client) tolerates 193, which is the maximum, and therefore needs pretty long until no more new connections are accepted.
Rumor is that 10.4.3 will contain a number of fixes on network code, so if we are lucky the problem will be history soon. If not, we have to flood Apple with bug reports... ;)
So in the meantime I suggest you try the most recent cvs binary I posted a couple days ago. It allows for 193 stuck connections instead of the default 8, so you don't have to restart amule that often.
-
Originally posted by lionel77
So in the meantime I suggest you try the most recent cvs binary I posted a couple days ago. It allows for 193 stuck connections instead of the default 8, so you don't have to restart amule that often.
Thanks for your answer.
Did you mean the last "SVN" binary ? (i didn't use it as you say in another post that this version is not that stable...).
-
SVN and CVS are both version control systems that help to keep track of the changes that are made to the code (from the user perspective it is completely irrelevant which one is used). Recently we switched from CVS to SVN so I started calling my binaries SVN binaries instead of CVS binaries. Then I realized that the rest of the team thought it was less confusing to stick with the CVS terminology, because many people don't know about SVN and already associate CVS with up-to-date code. So now I'm calling my builds CVS builds again, even though, technically, I retrieve the code through SVN.
More importantly, the aMule-Mac.cvs2005-09-12.zip binary I posted a few days ago should run ok under Tiger. The stability issues seem to be mostly limited to Panther.
-
Thanks for the explanations.
I've downloaded your cvs2005-09-12 binary and i'm testing now. Crossing fingers...
-
Ok ,one day of ful running of the lates CVS from you lionel, everything is working fine.
This is the result of netstat:
Mars-G5:~ mars$ netstat -aLp tcp | grep -w 17672
94/94/128 *.17672
Mars-G5:~ mars$ netstat -ap tcp | grep "\*\.17672"
tcp4 0 0 *.17672 *.* LISTEN
Mars-G5:~ mars$ telnet localhost 17672
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
-
I've separated the postings on crashes and backtraces to keep this thread more legible. You can find the moved posts in this thread (http://forum.amule.org/thread.php?threadid=7547&sid=). :)
-
i need to comiple aMuledaemon (i've asked my question at this thread (http://forum.amule.org/thread.php?threadid=7526)) for Mac OS X Server 10.4.2
so, do i need only to change this string: "(listen(m_fd, 5) != 0))" and than compile sources as usual? or i need to do something else?
sorry for my english. (-:
-
Originally posted by samson
so, do i need only to change this string: "(listen(m_fd, 5) != 0))" and than compile sources as usual? or i need to do something else?
Yes, that's the only thing you have to change in wxWidgets for better Tiger compatibility.
-
have anybody information about this bug in 10.4.3?
-
Is fixed on 10.4.3
-
in other words, i can compile it under 10.4.3 without any tricks with wxWidgets (like "(listen(m_fd, 5) != 0))") and it will correctly works?
great! (-: