aMule Forum
English => Backtraces => Topic started by: RRM on April 08, 2010, 06:47:06 AM
-
Im currently only uploading files 24/7.
All aMule activity was halted due to this:
Akademlia/kademlia/Entry.cpp(469): assert "!m_publishingIPs->empty()" failed in ReCalculateTrustValue().
ASSERT INFO:
kademlia/kademlia/Entry.cpp(584): assert "wxAssertFailure" failed in WriteTagListWithPublishInfo().
BACKTRACE:
[1] Kademlia::CKeyEntry::WriteTagListWithPublishInfo(CFileDataIO*) /home/rrm/tmp/amule/src/kademlia/kademlia/Entry.cpp:585
[2] Kademlia::CIndexed::SendValidKeywordResult(Kademlia::CUInt128 const&, SSearchTerm const*, unsigned int, unsigned short, bool, bool, unsigned short, Kademlia::CKadUDPKey const&) /home/rrm/tmp/amule/src/kademlia/kademlia/Indexed.cpp:770
[3] Kademlia::CKademliaUDPListener::Process2SearchKeyRequest(unsigned char const*, unsigned int, unsigned int, unsigned short, Kademlia::CKadUDPKey const&) /home/rrm/tmp/amule/src/kademlia/net/KademliaUDPListener.cpp:1300
[4] Kademlia::CKademliaUDPListener::ProcessPacket(unsigned char const*, unsigned int, unsigned int, unsigned short, bool, Kademlia::CKadUDPKey const&) /home/rrm/tmp/amule/src/kademlia/net/KademliaUDPListener.cpp:321
[5] Kademlia::CKademlia::ProcessPacket(unsigned char const*, unsigned int, unsigned int, unsigned short, bool, Kademlia::CKadUDPKey const&) /home/rrm/tmp/amule/src/kademlia/kademlia/Kademlia.cpp:302
[6] CClientUDPSocket::OnPacketReceived(unsigned int, unsigned short, unsigned char*, unsigned int) /home/rrm/tmp/amule/src/ClientUDPSocket.cpp:137
[7] CMuleUDPSocket::OnReceive(int) /home/rrm/tmp/amule/src/MuleUDPSocket.cpp:183
[8] CClientUDPSocket::OnReceive(int) /home/rrm/tmp/amule/src/ClientUDPSocket.cpp:72
[9] wxAppConsole::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) cons)
[10] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[11] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[12] wxEvtHandler::ProcessEvent(wxEvent&)
[13] wxEvtHandler::ProcessPendingEvents()
[14] wxAppConsole::ProcessPendingEvents()
[15] wxAppBase::ProcessIdle()
[16] g_main_context_dispatch()
[17] g_main_loop_run()
[18] gtk_main()
[19] wxEventLoop::Run()
[20] wxAppBase::MainLoop()
-
Dear RRM,
I don't have the sightlest idea about Kad, it seems some people are attacking it so that could be the cause.
Anyways, run amule under gdb and try to reproduce this an get a more detailed backtrace, I guess that will help developers.
Cheers,
BTK
-
Thank you Bill.
aMule doesnt crash, it just halts all activity,
until i press "continue" (but when im not home, that can take all day)
When i got home, there were a whole bunch of these warnings; 14 i think.
GDB just says:
2010-04-08 06:55:03: SafeFile.cpp(475): Invalid Kad tag; type=0xd8 name=
2010-04-08 07:05:20: SafeFile.cpp(475): Invalid Kad tag; type=0x25 name=
2010-04-08 07:23:05: SafeFile.cpp(475): Invalid Kad tag; type=0xaa name=
2010-04-08 07:27:05: SafeFile.cpp(475): Invalid Kad tag; type=0xed name=
2010-04-08 08:31:01: SafeFile.cpp(475): Invalid Kad tag; type=0x26 name=
2010-04-08 08:33:23: SafeFile.cpp(475): Invalid Kad tag; type=0x0b name=
2010-04-08 08:43:07: SafeFile.cpp(475): Invalid Kad tag; type=0xad name=
2010-04-08 09:17:04: SafeFile.cpp(475): Invalid Kad tag; type=0x95 name=
2010-04-08 09:45:11: SafeFile.cpp(475): Invalid Kad tag; type=0xa4 name=
2010-04-08 10:38:45: SafeFile.cpp(475): Invalid Kad tag; type=0x9e name=
2010-04-08 12:38:42: SafeFile.cpp(475): Invalid Kad tag; type=0xa3 name=
2010-04-08 13:20:28: SafeFile.cpp(475): Invalid Kad tag; type=0x12 name=
2010-04-08 13:53:40: SafeFile.cpp(475): Invalid Kad tag; type=0x30 name=
2010-04-08 14:40:47: SafeFile.cpp(475): Invalid Kad tag; type=0x29 name=
Could it be that 'they' are targeting mega-uploaders?
-
This usually means a corrupted index. The assertion means that aMule has found a file with no publishers in the index, which should normally be an impossible situation.
-
RRM, are you still using a debug build ?
I think in a release build it would just skate over the problem.
And if it happened just once, lets file it in the "shit happens" category. ;)
-
Thank you Gonosz.
RRM, are you still using a debug build ?
Yes.
Should i build a new version disabling debug enabling optimize?
And if it happened just once, lets file it in the "shit happens" category. ;)
It was the third time. First time i ignored it.
Second time it was just one warning.
The third time there were 14.
Nothing happened this past night.
-
Should i build a new version disabling debug enabling optimize?
You should always enable optimize at the load you are running.
And yes, I suggest you disable debug for now.
-
hmmm, i must have done something wrong.
Maybe here?
./configure --prefix=/usr/local/stow/amule-opt/ --enable-geoip --enable-optimize --disable-debug --mandir=/share/bin
aMule starts running (aMule SVN using wxGTK2 v2.8.10 (Snapshot: rev. 10084)).
Normally connects automatically, but not now.
After i press "connect" (eD2k and KAD not connected), aMule says "connecting"
but after 20 minutes still nothing happens.
-
Application based firewall blocking app with different checksum?
-
Thank you Stu.
Why wasnt this an issue with previous aMule versions?
I didnt even know that there was such a firewall in Ubuntu.
How can i check this firewall?
Through ufw?
-
It was just a wild speculation.
Wait a moment...
Normally connects automatically, but not now.
Since 10074 aMule loads the IP filter in the the background and then connects. Could it be that you hit the connect button while the filter still loaded and actually disconnected it?
Just restart it. Switch to the log view. It should say "IP filter is ready" after a while and then "Connecting".
-
Arrg, there was a bug in the IP filter. If "IP filter update on startup" was selected and URL was empty or bad, aMule never connected to the network. :o
Fixed in 10086. Update or check your ip filter settings.
-
Hmm, when i call "git pull", it says "already up-to-date".
So, maybe i should wait a few hours, right?
-
Git is updated only when GonoszTopi finds time to do it.
Meanwhile just disable automatic filter update, or enter a valid URL.
-
I get it.
Aaaah, that works perfectly.
Thank you Stu.
-
I think in a release build it would just skate over the problem.
Similar as it skates over the following issue, i guess.
Curious if its the same as what previously halted debug enabled aMule;
I received over 100 identical of the following warnings:
(amule:8584): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
-
I continuously keep getting these warnings (in the GDB terminal);
about 35 of these warnings per minute now!!
(amule:2128): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
Just not right away after restarting; it takes a few hours before they come back.
Once they come again, they keep coming.
-
I'm always getting a flood of (amule:1544): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
. I believe it's a problem between wx and GTK. Yours might be similar.
You have any strings with strange characters on screen that don't get rendered properly?
-
You have any strings with strange characters on screen that don't get rendered properly?
I dont know, because i dont understand.
What screen?
In the GDB terminal window?
Or in aMule, in the "transfers" section?
-
I checked everything, but i couldnt find something like that anywhere.
-
In aMule. Anywhere. The message indicates aMule is passing bad strings to wx to be displayed in GTK.
-
AFAICT those warnings are GTK-related and can be safely ignored. Anyways, for the Pango warning the text doens't need to be displayed, could be a strange username of other network user, etc...
-
Thank you!