aMule Forum
English => aMule Help => Topic started by: ominobufo on March 12, 2005, 11:46:20 AM
-
I've just compiled this tarball with
./configure --enable-optimize --enable-amulecmd --enable-amule-daemon --disable-gtk --disable-monolithic --enable-webserver
Seem it works (it make connection and well go....) but, but when it start it launch it's webserver (i don't know if it's normal) that change immediately to dead thread: (just 2 make sure we understand...)
29984 ? S 11:12 amuled
...
29992 ? S 0:00 amuled
29993 ? Z 0:00 [amuleweb]
Any other attempts to launch amulecmd or amuleweb it's been denied by wrong password (dont' have set anyone... and even if i put one... the result is always the same)
Someone can help?
Tnx
P.s.
Maybe this is may help
-----------------------------
Initialising aMule
Userhash loaded: 5A612AAC020E9EE3D5BFB1681CDD6F07
Loading temp files from /mnt/hd/Emule-Temp.
- 001.part.met: Success.
- 002.part.met: Success.
ListenSocket: Ok.
*** TCP socket (ECServer) listening on 0.0.0.0:4712
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
Adding file /mnt/hd/Emule-Temp/001.part.met to shares
Adding file /mnt/hd/Emule-Temp/002.part.met to shares
aMuleweb is running on pid 30771
CServerSocket: destroying socket 0x83bf8d8 <---?!?!??
-
Please do a make install after compilation.
Other useful information sources:
amuleweb --help
man amuleweb (after installation, of course)
the aMule wiki: http://wiki.amule.org/
-
ehhh?!??!?!
truly i've done a make install after compilation.....
-
Then you have to set a proper password, probably.
NOtice that the current config files is NOT .eMule but .aMule/amule.conf
-
tried, plain text or null or md5 coded, don't work same way.
Think will wait for next stable version....
-
heh well dont give up so easy ;)
there is a pretty good howto in our wiki pages...
/http://www.amule.org/wiki/index.php/Webserver
in which way you have to setup the passwords and such.
for teh EC passwort you have to set it into your amule.conf which is in your .aMule folder in your homedir
the paswort later for teh webserver you can setup with
amuleweb -p passwort -w
this will write teh config file
then only type
amuleweb
btw: there are now new man pages aswell for taht stuff ;)
stefanero
-
Also if you decide not to solve the problem now, it is actualy very likely that you will have to solve this problem when the next stable version comes out. The next stable version is very close to CVS after all.
From March, 14th on, there is an option to generate an rpm from the cvs tarball, look here:
http://www.amule.org/amule/thread.php?threadid=5452&sid=
Cheers!
-
have already followed wiki guide to webserver step by step, no way to get it working. maybe try to switch to another cvs.... (no rpm support on my system :° but that's not the question...) I HATE THINGS THAT'S NOT WORKING, IT WILL IN A WAY OR ANOTHER MUAHAHHAHAHAHAHAH >:/ SBARAGBAUSSSS
I've already sucessfully installed other amule versions, and has always worked great. :° That's wants to get me mad... SOB :°°°°°°°°°°°°°°°°° ;( ;( ;( ;( ;( ;( evil programmers, evil programs :P
exact problem....
-----------------------
Creating client...
Now, doing connection....
Using host 'localhost' port:4712
Trying to connect (timeout = 10 sec)...
ExternalConn: Access denied because: Authentication failed.
------------------------
Tnx for all patience :*
-
ominobufo,
Please note that the configuration file for remote applications (amuleweb, amulecmd, amule-gui) has changed in the last days. So, the file is no longer ~/.eMule. Now it is ~/.aMule/remote.conf. You have a bad configured password. Type the command that stefanero told you:
$ amuleweb -P myfsckngpassword -w
NOTICE THE CAPITAL P!
and the password will be set in the file. You can also generate the password with an md5 hash and edit the file:
echo -n "myfsckngpassword" | md5sum
bc0ab7219ede9ebd3ba1bcc58f1af5e4 -
This hash can be used to check if the remote config file has the correct value:
$ grep -i password ~/.aMule/remote.conf
Password=bc0ab7219ede9ebd3ba1bcc58f1af5e4
Another option is
$ amuleweb --create-config-from=~/.eMule
This will create a config file based on your old configuration file. I hope this will solve your issue and other users as well.
Cheers!
-
Tnx for patience again. All works fine now.
My mistake, after setting remote.conf accordly to amule.conf all work!
Tnx for all support :baby: :baby: :baby:
-
Thanks to you for testing CVS :)