aMule Forum
English => aMule Help => Topic started by: PsychoChris on June 07, 2005, 05:47:00 PM
-
Hello,
since upgrading from 2.0.1 to 2.0.2 the webinterface doesn't behave like expected. Whatever i click on the pages reload but don't show refreshed content. And the preferences and statistic screens dont even show anything. In 2.0.1 those things worked fine and i compiled with the same flags. Should mention that i use only the daemon on a linux 9.0 computer and handle the rest through the webinterface on a windows computer.
Would appreciate any idea.
[EDIT:]
The problem is not the webinterface. After connecting through amulecmd it seems that amuled itself doesn't refresh its data. If i enter Stats i always get the same values back, as if the program is somehow frozen.
[EDIT:]
After restarting aMule again the daemon seems to work ok but the refreshing problems in the webinterface are still there. And when i exit amulecmd i get the following message:
ECSocket::ReadBufferFromSocket error No error happened
Sometimes i see this message in the logfiles. After they appeared im not able to connect to aMule through the webinterface anymore. In the process list i see [defunct] besides one of the amuleweb processes.
Any clues?
Greetings,
Chris
-
No one having similar problems with aMule 2.0.2?
-
well not here...but I run cvs-daemon
what wx-version are you one?
self compiler or rpms?
-
Never happen to me in amy version. Any chance that browser doesn't refresh it's cache ? May be template not contains "nocache" ?
-
@ stefanero:
wx-version is 2.6.0. I use a compiled version of aMule 2.0.2. The strange thing is that i didn't have any problems with 2.0.1 and i used exactly the same config-flags for configure.
Another strange thing is that clicking Serverlist, Transfer or Shared Files in the webinterface works fine, only the other options Statistics, Graphs and Preferences dont work. The page begins to load but nothing appears in the content area. Clicking on Search works also, but when i start a search i never get results. That also worked fine with 2.0.1.
@ Ifroen:
Didn't change browser-settings and tried it also on other browsers. Template also contains no-cache (using default template).
Does someone know what causes the following message?:
ECSocket::ReadBufferFromSocket error No error happened
Greetings,
Chris
-
ECSocket::ReadBufferFromSocket error No error happened
This is actuall not an error: it's indication that connection (EC) has been closed.