aMule Forum
English => aMule Help => Topic started by: mithrandir77 on October 24, 2005, 11:25:59 AM
-
Hi to everybody.
I have installed amule-cvs and i'm trying webserver but i have some problems.
With both standard and php webserver i have met some strange behaviours...
In fact after login i can't see download list or server list, and the browser page remains in 'loading state'...
It doens't happen with amule 2.0.3
?(
-
Can you tell what browser you using ? This problem was reported once, but I wasn't able to reproduce it.
-
Originally posted by lfroen
Can you tell what browser you using ? This problem was reported once, but I wasn't able to reproduce it.
I am using firefox (release 1.0.7)
-
Now i have tried also with IE but nothing has changed
The console of webserver reports:
WCThread: Started a new WCThread
Session ok
Checking password
Password ok
Processing request: index.html
WCThread: exited [WebSocket closed]
WCThread: Started a new WCThread
WCThread: Started a new WCThread
Session ok
Logout requested
Processing request: amuleweb-main-dload.php
Why it reports 'logout'? ?(
-
Moreover the webserver starts by default with php version and not with standard version, without using --php option on console. (if i start it from amule client, it starts with standard version)
This is the screenshot of browser connected to amule webserver.
(http://img479.imageshack.us/img479/5386/amule9hs.jpg)
-
Moreover the webserver starts by default
Yes, that is default version now. Previous webserver is being aged out.
Session ok
Logout requested
I suspect there's problem with url you using to access webpage.
It should be something like http://myhostname:1234/
One more thing, are you accessing localhost or another computer ? How they are connected ?
I will debug it. Thank you for report.
-
Originally posted by lfroen
Moreover the webserver starts by default
Yes, that is default version now. Previous webserver is being aged out.
Session ok
Logout requested
I suspect there's problem with url you using to access webpage.
It should be something like http://myhostname:1234/
One more thing, are you accessing localhost or another computer ? How they are connected ?
I will debug it. Thank you for report.
I use this notation to connect http://myhostname.no-ip.info:5711/ .
I connect using another computer, from remote. I use a Dynamic DNS service (no-ip.com) to connect from my computer at work.
However i have tried to use local firefox (by VNC) and http://127.0.0.1:5711 but nothing changes
-
Moreover i have to shutdown and restart the webserver if i want to try another time. The server seems to freeze...
I have tried also using standar port (4711 instead 5711, which is the one i use), but nothing has changed.
?(
-
I made few changes/fixes today. Please see if there's any difference. Post webserver log if it still works wrong.
-
Originally posted by lfroen
I made few changes/fixes today. Please see if there's any difference. Post webserver log if it still works wrong.
Can i found these last changes on the last cvs release now?
Stupid question: where can i found the webserver log? :tongue:
-
No, not now. Wait untill tomorrow snapshot. Or meet me on #amule
Stupid question: where can i found the webserver log?
Log is printed to console where amuleweb was started.
-
Originally posted by lfroen
No, not now. Wait untill tomorrow snapshot. Or meet me on #amule
Stupid question: where can i found the webserver log?
Log is printed to console where amuleweb was started.
ok i will wait for tomorrow snapshot ;)
-
Hi!
I have downloaded the new cvs snapshot but the problem still remains.
The log of webserver is
WSThread: Thread started
WSThread: created socket listening on :5711
WCThread: Started a new WCThread
Processing request [original]: stats.php
No session opened - will request login
Session created - requesting login
Checking password
Password ok
Processing request [redirected]: index.html
WCThread: exited [WebSocket closed]
WCThread: Started a new WCThread
WCThread: Started a new WCThread
Processing request [original]: top.html
Session ok, logged in
Processing request [redirected]: top.html
WCThread: exited [WebSocket closed]
Processing request [original]: amuleweb-main-dload.php
Session ok, logged in
Processing request [redirected]: amuleweb-main-dload.php
WCThread: Started a new WCThread
It seems to be processing the request but it is infinitly slow. In fact if i try to connect with another browser session, the new browser session waits for an answer without receiving a timeout. So the webserver seems to be freezed.
?(
-
WSThread: Thread started
WSThread: created socket listening on :5711
WCThread: Started a new WCThread
Processing request [original]: stats.php
No session opened - will request login
Session created - requesting login
stats.php ? What url do you access ? Or you have ommited parts of log ? Anyway, I don't see any particular problem here: in it is processing request:
Processing request [original]: amuleweb-main-dload.php
Session ok, logged in
Processing request [redirected]: amuleweb-main-dload.php
There might be a problem in communication between amuleweb and core. Do you run them both on the same computer ? Is it amule or daemon ?
Such problem has never been reported, so I suspect more debugging would be needed.
Next step would be ethereal sniffing to track data being transferred, on both local end remote end, if you know how to do it. You welcomed to meet me on irc #amule for assistance.
-
Originally posted by lfroen
WSThread: Thread started
WSThread: created socket listening on :5711
WCThread: Started a new WCThread
Processing request [original]: stats.php
No session opened - will request login
Session created - requesting login
stats.php ? What url do you access ? Or you have ommited parts of log ? Anyway, I don't see any particular problem here: in it is processing request:
Processing request [original]: amuleweb-main-dload.php
Session ok, logged in
Processing request [redirected]: amuleweb-main-dload.php
There might be a problem in communication between amuleweb and core. Do you run them both on the same computer ? Is it amule or daemon ?
Such problem has never been reported, so I suspect more debugging would be needed.
Next step would be ethereal sniffing to track data being transferred, on both local end remote end, if you know how to do it. You welcomed to meet me on irc #amule for assistance.
I access the url from my work place (using ip:port), and either from the same computer (127.0.0.1:port) using remote desktop (VNC).
I note that it is processing, but it never finishes... ?(
Ethereal? i know it by i don't use it... As i can open irc i contact you ;-)
-
lfroen which server for irc?
-
irc.freenode.net port 6667 ;)
-
I'm still having problem with php webserver.
How can i change the webserver to chicane template? ;(
-
well if you use cvs tehn run it with
--no-php -t chicane
the -t option is for the template name, check in your
/usr/local/share/amule/webserver/
if the chicane template is present, if so the above commadn should work, just start amuleweb like that from teh command lin
-
Please report if webserver works for you with --no-php. It would give me hint in debug.
-
Originally posted by stefanero
well if you use cvs tehn run it with
--no-php -t chicane
the -t option is for the template name, check in your
/usr/local/share/amule/webserver/
if the chicane template is present, if so the above commadn should work, just start amuleweb like that from teh command lin
Thx...
I have done it.... and... I have understood that the previous problem is not caused by the template but by the server or by the comunication between server and amule core.
In fact i can log in, i see the first page with header but if i try to view download page or server page, i have the same problem that i have with php server: the browser loading and the server freeze or loop... ;(
-
That is what I already told several posts before. Before displaying downloads page, webserver queries core. If you have many files (> 100) in download queue, EC may fail.
That is known problem, and being debugged.
-
And being fixed.
-
Originally posted by lfroen
That is what I already told several posts before. Before displaying downloads page, webserver queries core. If you have many files (> 100) in download queue, EC may fail.
That is known problem, and being debugged.
Ok, i understood.
But i haven't so many files in download, i have no more than 30 files (even if some files are more than 1 GB).
I have a lot of file in sharing, quite 2000 files.
Do you think it can cause the same problem?
-
I dont think so...
what about the --no-php and the other template??
-
Originally posted by stefanero
I dont think so...
what about the --no-php and the other template??
The same... It seems to be loading... But never finish...
I have tried also the old template but without success
-
Hi, all!
I have this same behaviour, when trying to access server list or log file. The page won't be displayed completely, with the little hour glass turning endlessly. I once went away to lunch, leaving it alone for two hours - nothing. I have to kill and restart amuleweb, to get any response out of it again.
Tried every variant, with and w/out php.
Shared files (only 150 or so) and transfer (even fewer. 8 files) are OK.
I observe this behaviour for some months now. Up to and including CVS 20051026.
-
To add to this line, I observe the same issue with CVS 20051029 here too (and several others before that). But it is not quite consistent, the server does serve the pages for preferences, graphs, statistics, search and servers. Only the transfer page seems to not load. And once you touched that button, nothing more can be done other then killing and restarting the daemon.
PS1: The webserver is started by the detached daemon, does it leave a log anywhere else but on the console?
PS2: The amulegui also won't start, it doesn't show any error, but it doesn't do anything. Again, this has worked once tonight, but that's all.
-
To be perfectly clear: the trigger for this bug is transmission of EC packet above size of outgoing buffer which is hardcoded in ECSocket.h. Since there's no theorethical limit for size of this packet (it depends on number of items requested and length of item names), this limit sometimes reached. Unfortunally, the code that should deal with this situation is broken.
I will fix it when I'm done with current webserver issues, means really soon.
Kry: this bug must be fixed before release.
-
Originally posted by lfroen
To be perfectly clear: the trigger for this bug is transmission of EC packet above size of outgoing buffer which is hardcoded in ECSocket.h. Since there's no theorethical limit for size of this packet (it depends on number of items requested and length of item names), this limit sometimes reached. Unfortunally, the code that should deal with this situation is broken.
I will fix it when I'm done with current webserver issues, means really soon.
Kry: this bug must be fixed before release.
Thanks :baby:
I will wait for it... because it is very difficult to submit searches without it from a remote computer :P
-
A news about this problem: i have installed on my notebook Suse 10 for trying it and then i have tried to install amule cvs on it (reinstalling wxGTK ;-) )
Then i have tried to start the amule webserver and after login it seems to work. ?(
But i don't have file in download list and no file in sharing so the test is not very useful.
In this weekend i want to install Suse 10 and amule on my home pc and last amule cvs and i will test ;)
-
Again an update on this from my side:
It seems that the webserver is having problems when:
- It is started by the daemon. It won't serve certain pages after the login succeeds.
- The daemon is hashing files. It almost seems like the daemon blocks certain functionality if the hasher is working.
Yesterday I installed the CVS 20051105 version, and this version still shows odd behaviour of the webserver. To be continued I guess.
PS. It's good to see the PHP version now as standard "daemon started" version too ;)
-
New update by my side.
I have finished to install Suse 10 on my pc (where i use amule) and nothing has changed on amule webserver behaviour. Login successful, but nothingelse... The browser remains 'loading', and i have to shutdown the webserver to try another access.
So on two Suse 10:
- no files in sharing and in downloading list all is ok, i can access the amule webserver
- with files in sharing and in downloading list, the webserver continues to have problems after login
-
One more update from here:
If I start a webserver from the command prompt, where I have to edit the remote.conf first to set the listening port to 4713, all is well. Then I get all the pages that I want, and quickly too.
Also I found out now that if I restart the daemon and leave it alone for say 15 minutes the automatically started webserver does indeed function correctly.
It seems that every test I have done sofar I have simply requested pages too soon after a restart of the daemon. Perhaps the daemon/webserver combination have some housekeeping to do before the first pages can be served correctly?
-
Hi ........i have a similar problem in amulewebserver in amule2.03 and latest cvs....
the webserver seem's to start properly but when i connect to him after login i have a blank screen on my browser. please help me. sorry for my very bad english