aMule Forum
English => aMule Help => Topic started by: KoZaki on March 29, 2005, 11:06:07 PM
-
Hi every aMule user and :baby: my 'Salutations respectueuses' to all aMule team members
Since a bit more than a week, my aMule client 2.0.0rc8 his all of a sudden having trouble to upload (yes: UPload ;) ) I wonder wether it's a bug (but why would this bug happends suddently), a firewall issue (but i haven't changed any rules for weeks) or... well, WTH is happening ?
As an exemple i started it half an hour ago, & it downloaded 310 MB while uploaded 9 MB !?
Below's a screenshot illustrating what's presently happening :
stats screenshot (http://c.laloy.free.fr/images/softs/p2p/amule2.0.0rc8_up_prob.jpg)
This happends whatever server i connect to.
I'm not used to such a behavior. It's actually the 1st time i see this, despite beeing aMule (& eMule a long time be4) user for quite a long time !
ed2k network's philosphy and mine are close to each other : SHARE WHAT YOU CAN ON THE WEB --> therewhile my question
[EDIT]for clarity[/EDIT]
-
right now, started since 10' & upload @ 2,7ko (60ko available) :(
is there anybody else seeing such a thing ?
when I don't UP, this is no good for you dudes !
-
funny thing
have you tryed disabling your firewall just for the sake of trying if thats teh error?
do you use standart ed2k port? 4662 or have you changed those ports in prefs?
I would suggest you if you still use standart to change them, maybe your ISP is blockig at least upload...
-
hi !
i've changed ports long time ago (as i advise others to do on this web site (http://c.laloy.free.fr/howtos/index_p2p.html) i try to maintain)
so i'll try to stop the FW for moment (i've got 2 servers runnning on it... waiting an old dedicated PC for that..) & come back here say what happened
-
I've stopped the FW then launched aMule and have the same problem
After 20' without FW, UP are very low/unstable,
clients waiting never more than 2 (more often °) !
from time to time one client DL @ full capacity for a few minutes, then slow down to 0-1 ko/sec, then is replaced by another ?(
Here is a wxGTK lib version that may have cause my aMule's problem to upload :
wxGTK2.5-2.5.3-2.mdk10.1.thac
amule-2.0.0-0.rc8.5pl
I just replaced Thac's wxGTK with aMule team's libwxgtk-gtk2u_2.5_3-2.5.3-5mdk-10.1.i586.rpm. But aMule messages still say02.04.2005 18:45:33: Ceci est aMule 2.0.0rc8 using wxGTK2 v2.5.1 (basée sur eMule)
and Upload are still @ 0 kb (connected at Razorback2 then DonkeyServer 1) ;(
-
2day I compiled wxwidgets-cvs along with amule-cv, with --enable -amule-daemon configure option (as i long wanted to launch amule as a daemon) and to see if it solves this %£$@ UP problem.
Changed the firewall rules to be able to log into amule-webserver, & re-checked amule tcp/upd ports are correctly configured --> they are.
amule-cvs runs fine to download but no better than 2.0.0rc8 when it comes to UP !!!
Now, aMule-CVS is running for about 3 hours with >50ko/sec Upload available, but it uploaded 3Mo (sic) and shows only 0 to 1 client
Please help me to find this problem out :baby:
I runned mandrake-10.1 until yesterday night and have shifted to mandrake-10.2 beta2 since then (pliz remember this UPload problem started 10-12 days ago, long be4 i shifted to 10.2beta2).
Logs :
aMule vCVS Statistics [aMule-Linux[EN-FR-CN][http://www.howtos.fr.st]]
Statistiques
Temps de fonctionnement: 3:38 h
Transfert
Ratio UL:DL de la session (Total): 2,90 : 1
Envois
Données émises (Session (Total)): 4,25 Mo (146,61 Go)
Dépassement total (Paquets): 63 Ko (3K)
Dépassement des demandes de fichiers (Paquets): 10 Ko (210)
Dépassement des échanges de sources (Paquets): 32 Octets (2)
Dépassement serveur (Paquets): 32 Ko (3K)
Envois actifs: 0
Envois en attente: 0
Total des sessions d'émission réussies: 78
Total des sessions d'émission échouées: 4
Temps d'émission moyen: 46 s
Téléchargements
...
Connexion
Vitesse moyenne de réception (Session): 0,12 Ko/s
Vitesse moyenne d'émission (Session): 0,34 Ko/s
Vitesse moyenne maximum de réception (Session): 0,13 Ko/s
Vitesse maximum de réception (Session): 21,58 Ko/s
Nombre de reconnexions:0
Temps depuis le premier transfert: 3:35 h
Connecté au serveur depuis: 3:38 h
Connexion actives (estimation): 0
Nombre maximum de connexions atteint: Never
Moyenne des connexions actives (estimation): 0,147226
Pic de connexions (estimation): 12
Clients
Total: 3 Connus: 3
eMule: 3 (100,0%)
v0.45b: 1 (33,3%)
v0.44b: 1 (33,3%)
aMule: 0 (0,0%)
Version
v2.0.0: 1 (100,0%)
Système d'exploitation
Linux: 1 (100,0%)
lMule/xMule: 0 (0,0%)
eDonkeyHybrid: 0 (0,0%)
v0.53.0: 1 (100,0%)
...
LowID: 1 (33,33% Total 33,33% Connus)
SecIdent Marche/Arrêt: 3 (100,00%) : 0 (0,00%)
HasSocket: 0 (0,0%)
Filtrés: 9
Serveurs
Serveurs actifs: 56
Serveurs injoignables: 65
Total: 121
Serveurs supprimés: 0
Utilisateurs sur les serveurs actifs: 3256963
Fichiers sur les serveurs actifs: 415605494
Nombre total d'utilisateurs: 3592908
Nombre total de fichiers: 441297270
Occupation du serveur: 15,42%
Fichiers partagés
Nombre de fichiers partagés: 158
Taille totale des fichiers partagés: 7,57 Go
Taille moyenne de fichier: 49,03 Mo
-
Originally posted by KoZaki
LowID: 1 (33,33% Total 33,33% Connus)
I don't understand the language you posted, but if the LowID refers to your client, this should be the problem.
-
Vollstrecker > the statistics log refers to the clients connected to amule. You can check it in your stats log.
Just to add amule allways get High ID over here. Plus, i have *no prob* to DL, as said up in this post.
ps : what that language u don't understand ?
[EDIT] + screenshot (please clic to enlarge!) :
(http://c.laloy.free.fr/images/softs/p2p/aMule_UP_prob_small.png) (http://c.laloy.free.fr/images/softs/p2p/aMule_UP_prob_stats2.png)
[/EDIT]
-
well could you maybe try a cvs-snapshot and see if it works better? many many things have been solved so maybe even that ;)
other then that I have nfc whats going on here, you havent changed your firewall settings and not changed amule version, only other thing I can suspect here is ISP....
stefanero
EDIT: forget the 1st sentence ;)
-
I vote for ISP :P
-
huh?
looking atr your stats..whats funnny is you only have 3 clients connected to your mule...
from with are 2emule, 1 amule and 1 mldonkey, i guess the 1amule is you....
-
another thing might be IPfilter...it was bugged some time back, maybe you still have a buggy ipfilter.dat
could you disable it in prefs and see if more clients connect to you?
since those few clients might upload more then you see at your stats
-
Originally posted by KoZaki
ps : what that language u don't understand ?
This one:
Données émises (Session (Total)): 4,25 Mo (146,61 Go)
Dépassement total (Paquets): 63 Ko (3K)
Dépassement des demandes de fichiers (Paquets): 10 Ko (210)
Dépassement des échanges de sources (Paquets): 32 Octets (2)
Dépassement serveur (Paquets): 32 Ko (3K)
Envois actifs: 0
....
-
ce la vie Vollstrecke :P
look at your stats tree and its pretty simple to find out what it means ;)
life is sometimes really hard isnt it?
-
Oh no! stefanero how do you dare show everybody here that i'm a pitifull debugger :]
True, i've been looking the stats tree & can't find it
I also desactivated IPFilter then restarted amuled, & uploaded an amazing ;) 209ko after 10 minutes.
Where to look for ?
Connection: Connected to Razorback 2 [195.245.244.243:4661] with HighID
Speed: Up: 0.0 | Down: 0.0 (Limits: 51.0/0.0) [ 4/4/2005 16:23:23 ]
Stats tree shows Connexion
Vitesse moyenne d'émission (Session): 0,14 Ko/s
...
Nombre de reconnexions:0
Temps depuis le premier transfert: 7:11 min
Connecté au serveur depuis: 7:55 min
Connexion actives (estimation): 0
Nombre maximum de connexions atteint: Never
Moyenne des connexions actives (estimation): 0,188779
Pic de connexions (estimation): 5
Clients
...
LowID: 0 (0,00% Total 0,00% Connus)
SecIdent Marche/Arrêt: 4 (80,00%) : 0 (0,00%)
HasSocket: 0 (0,0%)
Filtrés: 0
Serveurs
Serveurs actifs: 69
Serveurs injoignables: 55
Or could it be a Squid proxy server configuration's problem ?
-
huh? you run amule throuw proxy?
-
You wrote 209 ko, so I think it's french.
I never brought amule throu my squid. Why not nat?
-
Vollstrecker > u got a point :)
stefanero : pliz maybe you can develop just a minute : look at your stats tree and its pretty simple to find out what it means Wink
Squid » it's not running anymore, but i tried it for a few days untill yesterday.
Last time i started it, amuled sayed :
* About to connect to [my_ip] port [squid.conf port]
* Trying [my_ip] .. * connection refused
couldn't connect to host
...
Listensocket OK
...
So I'll check my system's proxy & hosts config.
Say, if i put the mess with proxy config, would it affect 2.0.0rc8 the same way than 20050402-cvs ?
-
well aslong as its in your .eMule file might be...
there was no proxy in rc8, but in cvs tehre is, also the conf file changed from .eMule to .aMule/amule.conf
but I dont think that rc8 cares about settings from things it has no clue of,
as a matter maybe remove the .eMule file and amule.conf, create new once and see if that works...
I am just guessing atm, since I really have no clue :rolleyes:
-
Hi!
stefanero > it seems it is you who wrote amuled & amuleweb wiki pages. Schön :)
is it allright if starting amuled once after having moved away .eMule & .aMule/amule.conf, then .aMule/remote.conf is not created ?
To create the ~/.aMule/remote.conf file, which is the preferences file, run aMuled once.
maybe remove the .eMule file and amule.conf, create new once and see if that works...
--> I did that, as i hoped that starting amuled &/or amuleweb will create some config file, that i can compare to mine (which was 1st created looong time ago, with one of the first amule-2.0.0rc rpm releases, or maybe one copied from some eMule client I had 2 years ago), as I'm not able to create an amule.conf right from scratch.
Pliz how can i take advantage from your advice, that is to remove (made backup 1st) amule.conf ?
-
well
1st
.aMule/removte.conf is the config file for external Programms like amuleweb, amulecmd or amule-remote-gui
2nd.
since a couple weeks teh NEW config file is .aMule/amule.conf,
in rc8 for example it was still .eMule file in your homedir.
about what was written in the wiki-pages, someone messed that up, its fixed now...
-
Allright, thank you for making that clear stefanero.
Still ... :
maybe remove the .eMule file and amule.conf, create new once and see if that works...
--> I did that, as i hoped that starting amuled &/or amuleweb will create some config file, that i can compare to mine (which was 1st created looong time ago, with one of the first amule-2.0.0rc rpm releases, or maybe one copied from some eMule client I had 2 years ago), as I'm not able to create an amule.conf right from scratch.
Pliz how can i take advantage from your advice, that is to remove (made backup 1st) amule.conf ?
-
well to remove them just move your .eMule file to .eMule.bak or something and it will create new once aswell....
maybe stick to the rc8 release since we only have one conf file instead of 2 different once
-
?(
I did that, as i hoped that starting amuled &/or amuleweb will create some config file, that i can compare to mine
, but starting amuled (as well as amuleweb) did not create any new configuration file.
So i moved amule.conf back to it's original name & place.
[EDIT] Note that UPload problem started while i was using amule-2.00rc8, so i'm not sure why i'd better shift back to stable.
-
are you running amule-rc8 or cvs now?
amuleweb does not create the config file automatically, ONLY amule does.
to create teh amuleweb config file you would have to start amuleweb with the parameter -w, but check --help in amuleweb for more options, with simple -w it does not make a lot of sense ;)
-
20050402-cvs.
i launched back squid (& added some files to DL) & it looks as if UP is... up back to normal.
So it seems that i messed with my proxy configuration.
Pliz accept my apologize for bothering you about aMule :(
-
heh no problem :)
main concern is that it works ;) so good to know its back to normal :))