aMule Forum

English => aMule Help => Topic started by: gooddude on September 13, 2005, 10:26:13 PM

Title: amuled & amuleweb forked problems
Post by: gooddude on September 13, 2005, 10:26:13 PM

Hello good people!

Here is the problem:

I set up everything to work. So at the end, after testing amuled and amuleweb separately and configured conf file (as described in wiki) to start amuled with amuleweb i tried amuled -f, and it worked, at least it said it did. I tried then to connect to the localhost:4711, as I would normaly do with amuleweb, but then it couldn't connect (i also tried ip:4711). What could it be?

tnx

Title: Re: amuled & amuleweb forked problems
Post by: stefanero on September 14, 2005, 06:27:31 AM

amuleweb is a seperate application
did you start it?

if you enable automatic start in amule.conf file for amuleweb, make sure it is in path
with ps ax | grep amule

you can check what is actually running...

Title: Re: amuled & amuleweb forked problems
Post by: gooddude on September 14, 2005, 04:05:05 PM

Solo amuleweb works better than great.

I enabled automatic start for amuleweb. On processes list there is amuled -f, the only amule process, I asumed that's ok. Should it show amuleweb when integrated?

When I try to run amuledcmd to shutdown amuled it holds on so I have to kill amuled instead, I guess.

Title: Re: amuled & amuleweb forked problems
Post by: stefanero on September 14, 2005, 05:18:40 PM

yeah amulecmd was buggy in 2.0.3, but should work in cvs again...

and about teh amuleweb process not sure ;)
what does "netstat -ntlp" say? is there something listening on the webport? if no its not running...
sure amuleweb is in path?

Title: Re: amuled & amuleweb forked problems
Post by: gooddude on September 14, 2005, 06:51:42 PM

i must say that i'm not sure if it's in the path, cause i don't know what path are you talking about  :)

ok, there is only 4712 port opened so i guess web port is not open. what next ?

i will install CVS for cmd to work then.

Title: Re: amuled & amuleweb forked problems
Post by: stefanero on September 14, 2005, 07:02:56 PM

how do you start amuled?
go into the directory and type ./amuled? or what?

Title: Re: amuled & amuleweb forked problems
Post by: gooddude on September 14, 2005, 07:15:55 PM

just amuled (and -f when i want it).

i also tried going to the /usr/local/bin and did ./amuled -f, but as expected the same thing.

Title: Re: amuled & amuleweb forked problems
Post by: GonoszTopi on September 14, 2005, 07:32:10 PM

do a "which amuleweb"

If it shows something like below, then it's in the path.

Code: [Select]

$ which amuleweb
/usr/local/bin/amuleweb
$

Title: Re: amuled & amuleweb forked problems
Post by: gooddude on September 14, 2005, 08:07:49 PM

Yes, I forgot to mention that all amules are there (amuled, amuleweb, amulecmd, ...). So now I can say it is and was in the path.

Title: Re: amuled & amuleweb forked problems
Post by: gooddude on September 15, 2005, 04:42:11 PM

I have installed the new CVS. After some strange situations everything works fine, I think there were some bugs in the older version.
Thank you all for your help  :)

Title: Re: amuled & amuleweb forked problems
Post by: stefanero on September 15, 2005, 05:39:46 PM

:))