aMule Forum
English => en_Linux => Topic started by: quini on March 11, 2006, 02:57:24 PM
-
Hallo!
I'm trying to set amuled up working, mainly because I'd like amuled to be run by an unprivileged user in the background, and I should be able to get to it from either the same computer or others.
I'm using Ubuntu & latest binary 2.1.0; I've created user amule, switched to it and run amule once to set everything up; also remote connections are allowed (=1). I've then run amuled from a console, and the log seems fine to me, but it shows client/server UDP errors:
-----
amule@quiniserver:/Dades/HomeQuini$ amuled
amuled: OnInit - starting timer
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
Loading temp files from /home/amule//.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 /Dades/Per grabar/mp3/Café del Mar/ shared
WARNING! Client UDP-Socket discarded packet due to errors (2) while sending.
WARNING! Client UDP-Socket discarded packet due to errors (2) while sending.
WARNING! Client UDP-Socket discarded packet due to errors (2) while sending.
WARNING! Server UDP-Socket discarded packet due to errors (2) while sending.
WARNING! Server UDP-Socket discarded packet due to errors (2) while sending.
...
-----
The problem is really that I cannot get to it either using amulegui nor amuleweb. Ports 4660-4672 are redirected to the server's PC (I was using mldonkey with no problem), and port 4712 is opened in firewall.
If I try to run amulegui it applies for the password (it's set up in amule's config file), and nothing happens, but the program doesn't shut down. The following info appears in the console:
-----
quini@quiniserver:~$ amulegui --verbose
Connecting...
Going to event loop...
-----
If I try to run amuleweb it also applies for the passwd and does nothing, but uses 100% cpu until ctrl+c:
-----
quini@quiniserver:~$ amuleweb
This is amuleweb 2.1.0
Enter password for mule connection:
Creating the client... (translated from catalan)
-----
Any idea on what to do/where to look for??? :baby:
TIA :) :))
-
have you read the wiki pages?
http://wiki.amule.org -- read the webserver howto...
if it does not help, post your amule.conf here
-
Yes, I had... with no luck :rolleyes:
Anyway I've been reading and trying, and I've found something. Amuled (or amule) run by the user I've created doesn't work, but... surprise! It does work if run from my normal user :] ...maybe a rights problem?? It doesn't belong to any group but it's own group, maybe I should add it to a specific group? ?(
Ah, my success is only partial... I can only get to the web interface through the standard 4711 port, but I still get nothing from the amulegui command:
-----
quini@quiniserver:~$ amulegui
Connecting...
Going to event loop...
-----
and it remains like that for long with no error messages 8o
Any other idea?? :))
Thanks for your answer ;)
-
It's solved! :P
The problem has been solved filling the "IP of the listening interface" (remote controls -> external connections) with the lan's local IP... I wrote nothing there because it also says "(empty for any)", so maybe it is a bug. ?(
Ok, thanks anyway :))
-
works here with "nothing" in it..
so it works on all of my 3 lan interfaces, not just one...
-
Confirmed, it only works for me if I set my eth0's IP in "remote controls -> external connections" (I've also tryed 0.0.0.0 successfullyt). If it's left blank amulegui never connects to amuled, either from the pc running amuled or for other in the lan.
Make me know if you'd like me to make some tests on it.
Thanks 8)