aMule Forum
English => Multiplatform => Mac OSX => Topic started by: m2kio on March 05, 2005, 04:18:39 PM
-
still bothers me.
(1) i still get low id from most servers and is definitely depends on the server, whether i get low or high id:
((list sorted by users))
razorback .. low
donkeysever no.1 .. low
donkeysever no.3 .. low
81.23.250.167 .. 50/50
byte devils .. low
ChezToff .. high
Breizh Digitalus .. high
Donkeyserver No.2 .. low
193.151.74.81 .. high
up to rc8 AFAIR i had no problems getting a high id.
... m2kio !
-
Strange. I tried all of your server which should have got me low id and I always get high Id. Useing new binary from lionel). With rc8, it was OK too.
-
Do you have an ipfilter.dat (or similar filter)?
According to this post (http://forum.amule.org/thread.php?postid=25201#post25201), Razorback requires more than one IP address (195.245.244.240 - 195.245.244.243) to be allowed through your filters. Could this be the problem?
If so, maybe the other servers have a similar requirement.
It may also be that your ISP is filtering connections from those servers in an attempt to discourage P2P use.
You might try a packet sniffer and see what happens on the wire.
-
hi,
i'm using an ip-filter.dat, but haven't changed it since months.
no ports blocked (outgoing), the 3 required ingoing ports forwarded.
today i restarted amule and got suddenly dl rates of approx. 4x as high as up to then. for 1/2 h. then amule crashed. restarting failed (assert(0)) 2nd restart took xxlong for indexing. now up ok, but i get many unusual errors on the console:
*** malloc: vm_allocate(size=1073745920) failed (error code=3)
*** malloc[1638]: error: Can't allocate region
*** malloc: vm_allocate(size=2147487744) failed (error code=3)
*** malloc[1638]: error: Can't allocate region
((note: amule is at 1.9 GB VM right now...))
Couldn't send hello packet (client deleted?)
((note: much more than usual))
Brrrrrr wrong UDP packet from server! (Unknown server on a OP_GLOBSERVSTATRES packet (194.242.113.240:4642))
Brrrrrr wrong UDP packet from server! (Invalid challenge on OP_GLOBSERVSTATRES packet (0x55aa7073 != 0x55aa145c))
... m2kio !
-
That sounds like something got corrupted in your .met files or something.
You can track down the source of those malloc messages by putting a breakpoint on malloc_printf and printing backtraces when it is hit. Then you can continue. When you feel you have a representative sampling of the source(s) of these messages, you can delete or disable the breakpoint. Here's a set of gdb commands which will automate the process of grabbing a few backtraces on malloc_printf for you:break malloc_printf
set $count = 0
commands
silent
if $count < 8
bt
set $count = $count + 1
end
cont
end[EDITED to include the all-important increment step.]
Note that even after the 8 backtraces, the breakpoint is still in effect, it's just continuing immediately. This means there's a small performance hit for each subsequent malloc message printed. If you like, just Ctrl-C to interrupt the program, disable the breakpoint, and continue. I would have had the breakpoint disable itself after the 8 backtraces, but gdb seems a bit buggy. When I've tried that in the past, it's crapped out on me.
After that, you might consider renaming your ~/.aMule directory and starting fresh. Start aMule once so it will create the necessary files in that directory and then you can move your Temp files back in to test.
-
hi,
sorry for the long delay in answering, but i actually had already replied but the msg seems lost. (maybe i closed the browser tab before submitting :] )
malloc: after some aMule crashes i removed all newly added dl's and the malloc problem was gone and no longer showed up.
i still get some "Brrrrrr wrong UDP packet from server! (Invalid challenge on OP_GLOBSERVSTATRES packet (0x55aa112f != 0x55aab97f))" messages and quite often "Couldn't send hello packet (client deleted?)"
low id: i tried to traceroute to the servers giving me low id and found out, i cannot traceroute through my router. i don't know too much about ip routing and so i absolutely cannot tell why.
for that reason i updated my router's software, but this didn't change nothing.
after that i had to reconfigure the router (saveing settings to file and reloading after firmware update does not work. off course not!) i found that after (trying to) connecting to a server i get some ip packets to different ports which were dropped by the router. i thought this may be the problem and set my mac as exposed host, firewall disabled, but that didn't remedy the problem. still getting low id from most servers, only some (i currently use 213.186.60.106 (ChezToff) and 81.23.250.167) give me high id most times.
btw: a new build from lionell would be fine. :rolleyes:
... m2kio !
-
Originally posted by m2kio
btw: a new build from lionell would be fine. :rolleyes:
at your service (http://forum.amule.org/thread.php?sid=&postid=28889) ;)
-
Originally posted by lionel77at your service[/URL] ;)
Thanks. :)
i occassionally succeeded in compiling it on my own, cvs-2005-03-16 + wxMac cvs-2005-03-16 happened to compile and link. But the prominent wx bug, where printing to the scrollview is messed up every time is still present. so i happily dl'ed yours.
.. m2kio !
-
hi ken,
i noticed again 2GB mallocs and tried the gdb stuff. as already stated i'm not used to this.
after starting with
bash: gdb amule
i entered the gdb commands. but amule was not started by gdb as i would have expected, so i started it thereafter from the finder, gdb still open and waiting in a terminal window. will this do it? or should amule have been started before?
and where are the backtraces stored?
... m2kio !
-
You must type "run" on gdb
-
Originally posted by m2kio
and where are the backtraces stored?
They are just printed in the terminal window, not saved somewhere in a file.
-
Originally posted by Kry
You must type "run" on gdb
ah, so there was another all-important step ;)
ok, i attach a log.
-
Statistics... let me take a look over it.
-
Originally posted by m2kio
Originally posted by Kry
You must type "run" on gdb
ah, so there was another all-important step ;)
Sorry about that. :)
I keep forgetting with whom I have and haven't done gdb stuff before.
[Edited: removed speculation (that I now believe was incorrect) about memory corruption bugs introduced by Xaignar's listctrl changes. Sorry, Xaignar. :)]
-
BTW, this is already fixed.
-
back to the low id issue...
after deleting (actually, moving) ".aMule/" i got high ids on razorback etc. So this is too an issue with (broken?) data/files.
Q: has anybody a hint which file to delete w/o again losing credits or even .part files?
... m2kio !
-
What about ~/.aMule/amule.conf
-
Originally posted by Kry
What about ~/.aMule/amule.conf
nope.
ok, i backuped .aMule/ and started with a virgin setup. (at least, i thought)
after copying in slowly files from the backuped .aMule/ it appeared to be ipfilter.dat.
Q: if i download a new ipfilter.dat (in Preferences>Security) is this expected to be merged with or to replace the old file?
i would have expected that it replaces the old file, but the old ipfilter.dat was ~6MB and after deleting and downloading it was only 3.2MB. so either it is merged, which would be idiotic, or replacing does not work, which should be fixed. (maybe the file is not truncated?)
also, after moving .aMule/ back (and deleting ipfilter.dat) i got a lot of warnings after starting amule again:
2005-04-01 16:58:18: Warning: /Users/kio/.aMule/Temp/022.part.met might be corrupted (-598)
i hope these are warnings only. i really thought to be on the safe side after duplicating the whole folder.
... m2kio !
-
Merged. And I don't like you calling me idiotic. I was the one making it merge.
-
Originally posted by Kry
Merged. And I don't like you calling me idiotic. I was the one making it merge.
hey, i didn't call you idiotic, only the idea to merge. ;)
how do you get rid of bogus entries if you merge them? (e.g. entries which include major servers 8))
aren't fresh ipfilter.dat's expected to be 'complete' ?
that's why i think merging is ... suboptimal.
maybe some kind of sanity check before replacing a working list with a maliciously broken one, but not merging. imho.
... m2kio !
-
Merging is there or you wouldn't be able to have personal ipfilter.dat entries. They would be removed on update.
If you want to remove entiries, do it by hand or remove ipfilter.dat before update.
-
huh,
where can i add personal ipfilter entries?
-
opening ipfilter.dat with a text editor?
-
Originally posted by Kry
opening ipfilter.dat with a text editor?
ok, somehow i expected this...
so, to summarize, you merge at a point where the uninformed user (100% minus the devs) can be expected to expect 'replace', because a user could have added some lines to this file manually. and as a result users now must (!) identify and remove bogus entries manually from a multi-MB file. each time after downloading a fresh one. this is not very user friendly. but no complaining. :rolleyes:
i suggest to add a radio button set "O merge" - "O replace" in IP-Filtering. Preset to "replace". This could have saved me the low id trouble and improved my "download experience". (peers were rejected too, of course.)
agreed?
... m2kio !
-
I already decided to do that, but I can't until 2.0.0 is out.
-
no problem for me to wait, i have fixed my ipfilter.dat, at least for now.
it's good there is a design freeze so short before the 2.0.0 release. :D
... m2kio !
-
there is no design freeze, just CVS freeze. I bet people is keeping code with themselves and not commiting, like me... I have some cool features already done ;)