Print

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

[Lewoco]

Two different procedures:

1) run amule; run amulegui on same host; perform search.
2) run amuled; run amulegui on same host; perform search.

Now with (1), the matches return quite quickly. With (2), amulegui never displays any matches. These results can be reliably duplicated.

amuled also crashes sometimes. I have no idea if it's related to the problem described above, and I since I'm not sure what causes it, I can't generate a backtrace using gdb. It's happened twice so far, both times after only a few minutes of operation. When it happens amulegui prints the following error to the console approximately once per second:

ECSocket::WriteBufferToSocket error The socket is non-blocking and the operation would block

Here is the output from amuled. I'm also trying to generate a backtrace using gdb, but like I said, I'm having trouble getting amuled to crash:

p2p@chac ~ $ amuled
Initialising aMule
Checking if there is an instance already running...
Loading temp files from /home/p2p/.aMule/Temp.
Loading PartFile 1 of 1
All PartFiles Loaded.
ListenSocket: Ok.

*** TCP socket (ECServer) listening on 0.0.0.0:4712
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
Empty dir /home/p2p/.aMule/Incoming/ shared
CServerSocket: destroying socket 0x8417740

--------------------------------------------------------------------------------
A fatal error has occurred and aMule has crashed.
Please assist us in fixing this problem by posting the backtrace below in our
'aMule Crashes' forum and include as much information as possible regarding the
circumstances of this crash. The forum is located here:
    http://forum.amule.org/board.php?boardid=67
If possible, please try to generate a real backtrace of this crash:
    http://www.amule.org/wiki/index.php/Backtraces

----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMuled 2.0.0 using wxGTK2 v2.6.0 (Unicoded)
Running on: Linux 2.6.9-gentoo-r9 i686

[2] wxFatalSignalHandler in /usr/lib/libwx_gtk2u-2.6.so.0[0xb7b9803a]
[3] ?? in /lib/libpthread.so.0 [0xb7f862c6]
[4] ?? in [0xffffe420]
[5] GSocket::Select(int) in /usr/lib/libwx_gtk2u-2.6.so.0[0xb7ba96d5]
[6] wxSocketBase::_Wait(long, long, int) in /usr/lib/libwx_gtk2u-2.6.so.0[0xb7ba53ce]
[7] wxSocketBase::WaitForRead(long, long) in /usr/lib/libwx_gtk2u-2.6.so.0[0xb7ba54bf]
[8] ?? in amuled [0x8114c1d]
[9] wxThreadInternal::PthreadStart(wxThread*) in /usr/lib/libwx_gtk2u-2.6.so.0[0xb7b832ba]
[10] wxPthreadStart in /usr/lib/libwx_gtk2u-2.6.so.0[0xb7b831b0]
[11] ?? in /lib/libpthread.so.0 [0xb7f80c17]
[12] __clone in /lib/libc.so.6[0xb77b16aa]

--------------------------------------------------------------------------------
Killed

[lfroen]

You have too many connections. Reduce max connection below 1000.

[darklegion]

Not sure if this is the same issue,but I have found that with amulegui the search window will show no results until you have clicked on the search window,after which they will appear.