aMule Forum
English => en_Bugs => Topic started by: Stu Redman on April 15, 2008, 10:36:29 AM
-
SVN 8365 is featuring Kad 2.0 from eMule 0.48.
Connect and find sources works fine, however search (in the monolith, not over remote) does not work for me. It doesn't find a single file.
-
Yep. Is there no SVN version number in the tarball ?
-
There's no SVN information inside the tarballs. Just call it "today's tarball" if the commit has been before 7am utc+2, elsewise "tomorrow's tarball".
GonoszTopi mentioned something of broken searches in the commit message, so I guess he's aware of that problem and will fix it soon.
-
7am utc+2
Actually 7am Central European Local Time, which is UTC+1 or UTC+2 depending whether daylight saving is in effect.
-
GonoszTopi mentioned something of broken searches in the commit message
He mentioned only searches initiated from the remote gui, but all Kad searches are broken at the moment. :(
And now it has terminated with "exit code 3" - again without any useful info (http://forum.amule.org/index.php?topic=14694.0) though I ran it through GDB. The Windows exception handler is useless as it is. >:(
Reverting to yesterdays tarball.
-
Being investigated and eventually fixed.
-
I fixed both Kad1.0 and Kad2.0 searchs (and source gathering with them), feel free to test with tomorrow's tarball!
Use the attached patch file if you can't wait.
-
You got it. It works! :D
Good work, you two!
The Windows debugging problem still nags me however...
-
Still crashing. :(
"This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information." - Done. ;)
Gdb: "Program exited with code 03." Clean exit, no stacktrace.
!2008-04-15 22:59:46: OtherFunctions.cpp(1108): Using configDir: D:\aMule\config
2008-04-15 22:59:46: amule.cpp(518): Initialising aMule
2008-04-15 22:59:46: amule.cpp(537): Checking if there is an instance already running...
2008-04-15 22:59:46: amule.cpp(562): No other instances are running.
2008-04-15 22:59:46: ClientCreditsList.cpp(168): Creditfile loaded, 936 clients are known
2008-04-15 22:59:46: IPFilter.cpp(109): Loading IP-filters 'ipfilter.dat' and 'ipfilter_static.dat'.
2008-04-15 23:00:18: IPFilter.cpp(333): Loaded 236519 IP-ranges from 'D:\aMule\config\ipfilter.dat'. 0 malformed lines were discarded.
2008-04-15 23:00:18: IPFilter.cpp(333): Loaded 0 IP-ranges from 'D:\aMule\config\ipfilter_static.dat'. 0 malformed lines were discarded.
2008-04-15 23:00:22: ExternalConn.cpp(167): *** TCP socket (ECServer) listening on 0.0.0.0:4712
2008-04-15 23:00:22: MuleUDPSocket.cpp(78): Created Server UDP-Socket at port 7894
2008-04-15 23:00:23: MuleUDPSocket.cpp(78): Created Client UDP-Socket at port 7892
2008-04-15 23:00:25: amuleDlg.cpp(216):
2008-04-15 23:00:25: amuleDlg.cpp(218): - This is aMule SVN using wxMSW v2.8.7 (Snapshot: rev. 8377) based on eMule.
2008-04-15 23:00:25: amuleDlg.cpp(220): Running on Windows XP (build 2600, Service Pack 2)
2008-04-15 23:00:25: amuleDlg.cpp(222): - Visit http://www.amule.org to check if a new version is available.
2008-04-15 23:00:25: amuleDlg.cpp(223):
2008-04-15 23:00:27: ServerList.cpp(83): Loading server.met file: D:\aMule\config\server.met
!2008-04-15 23:00:28: ServerList.cpp(168): 0 servers in server.met found
!2008-04-15 23:01:20: amule.cpp(783): Connecting
2008-04-15 23:01:22: RoutingZone.cpp(172): Read 197 Kad contacts
2008-04-15 23:01:22: ThreadScheduler.cpp(308): ThreadScheduler: Completed task 'AICH Syncronizing', 0 tasks remaining.
2008-04-15 23:01:24: Connected to Kad (firewalled)
2008-04-15 23:01:27: Connected to Kad (ok)
2008-04-16 04:16:21: RoutingZone.cpp(211): Wrote 1 Kad contact
2008-04-16 04:16:21: RoutingZone.cpp(211): Wrote 3 Kad contacts
2008-04-16 04:16:21: RoutingZone.cpp(211): Wrote 0 Kad contacts
2008-04-16 04:16:21: RoutingZone.cpp(211): Wrote 1 Kad contact
2008-04-16 05:01:33: Connected to Kad (firewalled)
2008-04-16 05:01:34: Connected to Kad (ok)
2008-04-16 09:01:31: Connected to Kad (firewalled)
2008-04-16 09:01:31: Connected to Kad (ok)
2008-04-16 13:01:27: Connected to Kad (firewalled)
2008-04-16 13:01:28: Connected to Kad (ok)
2008-04-16 16:01:20: Connected to Kad (firewalled)
After some multiple of an hour, Kad goes to firewalled and immedeately reconnects. On one of these ocassions, it went down however.
The runtimeerror could be a crash in one of the standard template lib functions (list stuff or so).
Oh, and it left a single contact in the nodes.dat. :P
-
"Please contact the application's support team for more information."
Sounds like dumb windoof. Could You write Your OS in Your signature or profile?
-
After some multiple of an hour, Kad goes to firewalled and immedeately reconnects.
That's perfectly normal.
-
Could You write Your OS in Your signature or profile?
I've mentioned Windows several times in this thread. And the log I posted shows the exact version. ;)
Windows (or rather the exception handler for Windows) is responsible for the bad handling, but probably not for the problem itself.
-
SVN 16Apr: Still can't do Kad searches from amulegui, or through amuleweb.
(but amule monolithic does work)
This means that EC command enumeration is broken.
-
You got it. It works!
No - not really. After an hour or so search stops working. Neither does it find any search results, nor any sources for new downloads. ???
... and some time later, search is working again. Maybe after nightly disconnect of my router ???
-
Kad searches are actually broken in todays tarball- I tested through the amuleweb interface and amuled as core.
SVN 16Apr: Still can't do Kad searches from amulegui, or through amuleweb.
Fixed.
-
After an hour or so search stops working. Neither does it find any search results, nor any sources for new downloads. ???
Just had the same problem with the pre-Kad2.0 version. Worked again after rebooting my router. Seems aMule is killing my router. >:(
Maybe it's the UDP queue lockup I read some time ago here ?
-
Maybe.
-
Still crashing. :(
"This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information." - Done. ;)
Gdb: "Program exited with code 03." Clean exit, no stacktrace.
After some multiple of an hour, Kad goes to firewalled and immedeately reconnects. On one of these ocassions, it went down however.
The runtimeerror could be a crash in one of the standard template lib functions (list stuff or so).
Since I applied this fix (http://forum.amule.org/index.php?topic=14843.msg78635#msg78635) it's been running straight for 3 days. Seems like you nailed that one, GonoszTopi. Looking good now. :D