aMule Forum

English => en_Bugs => Topic started by: woutermense on March 12, 2010, 05:17:38 PM

Title: aMuleGUI SVN10045 connection problem.
Post by: woutermense on March 12, 2010, 05:17:38 PM

After a long time of not compiling any SVN version I wanted to be bleeding edge again ;) aMuleD is running on my server, GUI on my desktop. It seems to load initially, but it doesn't finish.

• On the Transfers tab, all downloads (135) are displayed, but none of the uploads (25). Also the statusbar is 'frozen'
• On the Networks tab, all servers are displayed, but the aMule log is truncated and Server Info isn't displayed at all.
• Shared Files, Messages  tab are ok
• On the Statistics tab, none of the stats are displayed (I don't mean the graphs)

There seems to be no communication possible with the server whatsoever after loading.

Title: Re: aMuleGUI SVN10045 connection problem.
Post by: Stu Redman on March 12, 2010, 06:45:23 PM

You did run amuled and amulegui of the same version?

Title: Re: aMuleGUI SVN10045 connection problem.
Post by: woutermense on March 12, 2010, 07:00:25 PM

The new errormessage when an incompatible version is used works great ;)

So yes, the same version runs on the server as well as the desktop

Title: Re: aMuleGUI SVN10045 connection problem.
Post by: Stu Redman on March 12, 2010, 07:17:32 PM

What version did you run before? Can you retry the older version?
I've been stirring up EC pretty hard recently (but it is running fine here). However there is a connection problem (http://forum.amule.org/index.php?topic=17648.0) that is present in older versions too. What's your server/desktop OS ?

If you feel like investigating, build both in debug mode, activate EC debug logging and take a look at the logfiles. Careful about posting, they reveal all your activities.

Title: Re: aMuleGUI SVN10045 connection problem.
Post by: woutermense on March 12, 2010, 08:17:56 PM

I ran 2.2.6 before.

The connection problem from the other thread did not occur in 2.2.6, nor did (does) this problem.

My server runs opensuse 11.2, desktop is running windows 7. (Both 64bit)

I'll post a pruned log later.

Title: Re: aMuleGUI SVN10045 connection problem.
Post by: Stu Redman on March 12, 2010, 08:34:28 PM

Mingw or MSVC?

Title: Re: aMuleGUI SVN10045 connection problem.
Post by: woutermense on March 12, 2010, 09:00:00 PM

Visual Studio. (for the GUI)

Got the daemon already compiled.  (Serverside, standard linux tools)

Option: Cat_External\ Connect=1 or is more required?

Title: Re: aMuleGUI SVN10045 connection problem.
Post by: Stu Redman on March 12, 2010, 09:24:19 PM

eMule\VerboseDebug=1 is also required
Daemon uses amule.conf, remote guiuses remote.conf  .

Title: Re: aMuleGUI SVN10045 connection problem.
Post by: woutermense on March 12, 2010, 09:53:50 PM

Quote from: Stu Redman on March 12, 2010, 09:24:19 PM

eMule\VerboseDebug=1 is also required

This is called eMule for histrical/compatibility reasons I guess? It's not an auto-generated line if there is no config file tot start with. I assumed it goes in the [Debug] section. I edited both remote.conf on my desktop and amule.conf on the server to have debugging turned on.

Anyway, the debug builds are worse. Right now after I click connect, nothing happens and the process stays running in the background.

What appears on the amuled log:

Code: [Select]

2010-03-12 21:41:34: ExternalConn.cpp(260): New external connection accepted
aMuleGUI log:

Code: [Select]

2010-03-12 21:46:27 (remote-GUI): amuleAppCommon.cpp(329): Initialising aMuleGUI SVN using wxMSW VC v2.8.10 (Debugging) (Snapshot: rev. 10045)
 2010-03-12 21:46:27 (remote-GUI): amuleAppCommon.cpp(375): Checking if there is an instance already running...
 2010-03-12 21:46:27 (remote-GUI): amuleAppCommon.cpp(406): No other instances are running.
 2010-03-12 21:46:38 (remote-GUI): amule-remote-gui.cpp(292): Connecting...
 2010-03-12 21:46:38 (remote-GUI): amule-remote-gui.cpp(266): Going to event loop...
Then after I kill the daemon on the server:

Code: [Select]

2010-03-12 21:59:22 (remote-GUI): amule-remote-gui.cpp(307): Remote GUI EC event handler
!2010-03-12 21:59:22 (remote-GUI): amule-remote-gui.cpp(309): Connection failure
 2010-03-12 21:59:22 (remote-GUI): amule-remote-gui.cpp(314): Going down


Title: Re: aMuleGUI SVN10045 connection problem.
Post by: Stu Redman on March 12, 2010, 10:08:29 PM

Duh me. I meant

Code: [Select]

[eMule]
VerboseDebug=1Yeah, very historical. The only thing it's good for (apart from causing confusion) is to turn on/off a set of debug options without deselecting/reselecting them all. I think.
Maybe you can also try release amuled + debug remotegui or the other way round. How about CPU load?
If CPU load is an issue you can build the daemon both with optimize and debug.

Title: Re: aMuleGUI SVN10045 connection problem.
Post by: woutermense on March 12, 2010, 10:24:18 PM

This is what I get

aMuleGUI

Code: [Select]

2010-03-12 22:16:33 (remote-GUI): amuleAppCommon.cpp(329): Initialising aMuleGUI SVN using wxMSW VC v2.8.10 (Debugging) (Snapshot: rev. 10045)
 2010-03-12 22:16:33 (remote-GUI): amuleAppCommon.cpp(375): Checking if there is an instance already running...
 2010-03-12 22:16:33 (remote-GUI): amuleAppCommon.cpp(406): No other instances are running.
 2010-03-12 22:16:47 (remote-GUI): amule-remote-gui.cpp(292): Connecting...
 2010-03-12 22:16:47 (remote-GUI): amule-remote-gui.cpp(266): Going to event loop...
.2010-03-12 22:16:47 (remote-GUI): > EC_OP_AUTH_REQ 43
.2010-03-12 22:16:47 (remote-GUI):     EC_TAG_CLIENT_NAME 13 = amule-remote
.2010-03-12 22:16:47 (remote-GUI):     EC_TAG_CLIENT_VERSION 7 = 0x0001
.2010-03-12 22:16:47 (remote-GUI):     EC_TAG_PROTOCOL_VERSION 2 = 515
After killing the daemon

Code: [Select]

2010-03-12 22:19:36 (remote-GUI): amule-remote-gui.cpp(307): Remote GUI EC event handler
!2010-03-12 22:19:36 (remote-GUI): amule-remote-gui.cpp(309): Connection failure
 2010-03-12 22:19:36 (remote-GUI): amule-remote-gui.cpp(314): Going downamuled:

Code: [Select]

2010-03-12 22:22:49: BaseClient.cpp(1790): Compatible client found with ET_COMPATIBLECLIENT of cb
 2010-03-12 22:22:51: ExternalConn.cpp(260): New external connection accepted

I'll try recompiling tomorrow.

CPU load is low on server and desktop. Also both gui and daemon aren't eating the cpu.

Title: Re: aMuleGUI SVN10045 connection problem.
Post by: Stu Redman on March 12, 2010, 10:58:57 PM

Sometimes Windows just needs a kick in the ass (aka reboot) and EC magically starts working again. I've seen this after certain crashes caused by buggy versions.

Title: Re: aMuleGUI SVN10045 connection problem.
Post by: woutermense on March 14, 2010, 07:28:29 PM

Rebooting ís like magic... :( Ah well, another problem solved.