Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[OldFrog]

Recomppiled against wxGtk-CVS as of 2005-01-03, and still the same.

Code: [Select]

tail -f .aMule/logfile
2006-01-29 13:08:58: Fichier de Crédits chargé, il y a 30142 clients connus
2006-01-29 13:08:59:
2006-01-29 13:08:59:  - Ceci est aMule CVS using wxGTK2 v2.7.0 (Snapshot: Sun Jan 29 07:02:07 CET 2006) basé sur eMule.
2006-01-29 13:08:59:    Tourne sur Linux 2.6.12-14mdk i686
2006-01-29 13:08:59:  - Visitez [URL]http://www.amule.org[/URL] pour vérifier si une nouvelle version estdisponible.
2006-01-29 13:08:59:
2006-01-29 13:08:59: Chargement des fichiers ipfilter.dat.
2006-01-29 13:09:01: 127025 rang d'IP chargés depuis 'ipfilter.dat'. 0 lignes malformées ont été mises de coté.
2006-01-29 13:09:01: 0 rang d'IP chargés depuis 'ipfilter_static.dat'. 0 lignes malformées ont été mises de coté.
2006-01-29 13:09:01: Chargement du fichier server.met: /home/louis/.aMule/server.met
2006-01-29 13:10:29: 6739 serveurs trouvés dans server.met
2006-01-29 13:10:29: 2 fichiers .part trouvés
2006-01-29 13:10:29: *** TCP socket (ECServer) listening on 0.0.0.0:8008
2006-01-29 13:10:29: MuleUDPSocket: Created Server UDP-Socket at port 8005
2006-01-29 13:10:29: MuleUDPSocket: Created Client UDP-Socket at port 8006
2006-01-29 13:10:30: 127 Fichier(s) partagé(s) connu(s) trouvé(s)
2006-01-29 13:10:30: Connexion en cours
2006-01-29 13:10:30: Servers: Trying to connect
2006-01-29 13:10:30: Connexion à  Razorback (195.245.244.243 - 195.245.244.243:4661)
2006-01-29 13:10:30: 184 contacts Kad lus
2006-01-29 13:10:31: Deleted stale lock file '/home/louis/.aMule/muleLock'.
2006-01-29 13:10:31: ThreadScheduler: Completed task 'AICH Syncronizing', 125 tasks remaining.
2006-01-29 13:10:31: Hasher: Starting to create AICH hash for file: XXXXXXXXXXXXX
2006-01-29 13:10:31: Votre copie d'aMule est à  jour.
2006-01-29 13:10:31: Délai d'attente de la connexion à  Razorback (195.245.244.243:4661) dépassé.
2006-01-29 13:10:31: Servers: Trying to connect
2006-01-29 13:10:31: Connexion à  .S.E.D.G. 400k (38.119.96.15 - 38.119.96.15:4661)
2006-01-29 13:10:32: Connecté à  Kad (pare-feu)

And it stays there forever.

Looks like in today's snapshot there's something going wrong for my rig when rehashing, as in another try, connection lines went first, then rehashing ilne, and always only one line with rehash.
When connecting back with aMule-2.1.0, rehashing is ok and much faster (and uses much less CPU).

[Xaignar]

I'm afraid that I can't make head and tail of your description. What exactly is going wrong?

[wuischke]

2006-01-29 13:10:32: Connecté à  Kad (pare-feu)
This means: Connected to Kad (firewalled)

I guess this is what he means.

[Xaignar]

In any case, I'll have to advice against running the current snapshot, since I noticed a couple of mistakes made yesterday (by myself no less) that causes aMule to enter an inf. loop. As for the message, Kad always starts out firewalled.

[OldFrog]

Originally posted by Xaignar
I'm afraid that I can't make head and tail of your description. What exactly is going wrong?

Sorry, I had some real life :-D


What I mean is the snapshot runs flawlessly until it says it starts re-hashing, eventually it tells it's connected, and nothing is displayed any more, and it stays like that for at least 20 mlinutes, with 92% cpu and still hashing (I guess) the same single file.

I reran 2.1.0. It displays the same messages, but every 2 minutes it tells me it hashes a new file giving the name and telling how many are remaining. And it eats only 40% CPU doing that.

As you said, I'm afraid I entered an infinite loop anyway.

It didn't happen with yesterday's snapshot.

Sorry for the french-unicoded lines, I was in a hurry and didn't take time to put them back in english.

No trouble at all with kad (It always tells it's firewalled for a few seconds after connecting, as I use a router, then it's ok), my only concern is there seems to be a loop when hashing, or during the time it's hashing the very first file.

Thanks for your job, devs, it's now a huge work you did on this software. :baby:

[OldFrog]

As for now, looks like it's solved in Jan 30th's snapshot. the mule has already hashed 5 files and kry is an awful liar : it eats 70% CPU only. Thanks a lot   :baby: