aMule Forum

English => en_Bugs => Topic started by: Galizah on February 16, 2004, 11:23:32 AM

Title: aMule Webserver bug
Post by: Galizah on February 16, 2004, 11:23:32 AM

Hi,

I have noticed a bug when trying to run "amuleweb" with aMule 1.2.5.

When aMule is running for more than 4 hours "amuleweb" starts and aMule is crashing. Only killing it with "kill -9 amule" can stop the program then.

When restarting aMule and run "amuleweb" again, it works fine.
After 4 hours it still runs, but when accessing aMule through the web it chrashes.

This bug was also in 1.2.4, but not in 1.2.1!

So I dunno why this happens? Perhaps someone has the same problem and has fixed it already?

Greetings

Galizah

Title: Re: aMule Webserver bug
Post by: shakraw on February 18, 2004, 09:42:26 AM

Hi,
since new 1.2.6 version there is a modified web server and communication protocol code that makes amuleweb run nicely and much more faster than in 1.2.5.

Try using the new code for better performances and, in case, to track bugs. In this case, please, post a gdb's 'bt' and a 'bt full' output to help us in bug finding/fixing.

Greets,
shakraw

Title: I can't authenticate on the web server [1.2.6]
Post by: ryu on February 19, 2004, 01:59:01 AM

With amule 1.2.6 I can't authenticate on the web server. Most of times the server simply ignores my passwords without replying anything like "Unauthorized", but when the stars and the planets line up and the 'p' parameter of the URL is parsed the latest, then I get a web result that only says 'Access denied!'.

I readed the HOWTO and followed all the steps (I think). Here are the important parts of my .eMule config:

[WebServer]
Password=251e176204391644f8c402101ed111e7
PasswordLow=
Port=8080
Enabled=1
UseGzip=1
PageRefreshTime=120
UseLowRightsUser=0

[ExternalConnect]
AcceptExternalConnections=1
ECUseTCPPort=1
ECPort=4712
ECPassword=251e176204391644f8c402101ed111e7

The password is 'pakito' only to test, but I tryed others, of course with the same results.
I tested also with different passwords fot the amule external connection and the webserver login.

I run amule without arguments, and amuleweb also without arguments (which automatically connects through TCP with amule on the right port). I restarted amule several times to be sure that the config file was not written before stopping amule.
If I use amulecmd, I can connect and check the status of amule without problems (also connects through TCP).

Thanks for your help and this masterpiece of software.