aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: webserver not running since 2.0.3 update  (Read 4108 times)

dazzathedude

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 10
webserver not running since 2.0.3 update
« on: July 01, 2005, 04:52:49 PM »

HI AGAIN,

after great help/support from ken i have been happily running amule 2.0.1 with webserver support (running manually).
i have since updated to v2.0.3 which i know has the webserver compiled in the binary.
when i run the program after enabling webserver on startup I get the error message.

you requested to run webserver from startup, but the
amuleweb binary cannot be run. please install the package
containing amule webserver, or compile amule using --enable-
webserver and run make install???
1. I have tried deleting and reinstalling amule (including the hidden folders).

2. I have created a new user in osx v10.4.1 run amule and again still the same error.

please can anyboby HELP!!! or do i need to go back to 2.0.1 and run the webserver manually again.

kindest regards

darren
Logged

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: webserver not running since 2.0.3 update
« Reply #1 on: July 01, 2005, 05:57:17 PM »

Hi dazza,

I'd like you to try running amuleweb manually, just for a test.  Hopefully there will be some output that will help me figure out the problem.

  • In aMule, disable auto-launch of amuleweb.
  • Control-click on the aMule application icon in the Finder and select Show Package Contents
  • Navigate to Contents/MacOS where you should see amuleweb
  • Open /Applications/Utilities/Terminal.app
  • Drag amuleweb and drop it in the Terminal window
  • Press return to run amuleweb

Let me know if it works.  If it doesn't, please copy the output from amuleweb and post it here.
Logged

dazzathedude

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 10
as requested
« Reply #2 on: July 03, 2005, 12:31:48 PM »

hi again ken, glad u r back to help?

it sais, (i have typed it in as its running on a remote mac)

welcome to darwin!
darrens-power-mac-g4:~ darren$ /applications/utilities/amule.app/contents/macos/amuleweb
Enter password for mule connection (i type the pw i have put into amule full rights pw and ext tcp port)

creating client....
Now, doing connection....
Using host 'localhost' port: 4712
Trying to connect (timeout = 10 sec)....
Connection Failed, Unable to connect to the specified host


im sure it is something to do with my mac as i got a friend to download the client and i set it up for him without a problem?
possibly as i have run a prev. version manually although i have deleted all incl. hidden files and tried creating a new user in osx without luck?

many thanks

darren
Logged

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: webserver not running since 2.0.3 update
« Reply #3 on: July 03, 2005, 10:52:48 PM »

The error you're getting ("Connection Failed, Unable to connect to the specified host") indicates either that aMule isn't actually running, that it is not listening on the External Connection port, or that it is not using port 4712 as the External Connection port.

You can check aMule's log, at the bottom of the Servers screen, to see if aMule is listening on that port.  Scroll to the beginning of the log and you should see something like:

2005-07-03 01:01:55: *** TCP socket (ECServer) listening on 0.0.0.0:4712

Or, you might see something explaining why it isn't listening on that socket.

In aMule's preferences, in Remote Controls, in the External Connection Parameters section on the bottom: make sure "Accept external connections" and "Use TCP ports instead of unix local sockets" are both checked.  Use 4712 as your External TCP Port.  Make sure you have entered a password in here.  (This is separate from the Webserver full and low rights passwords.)

And, of course, make sure aMule is running when you try this test.

Hmm.  Do you have a Mac OS X's firewall running?  It's in System Preferences -> Sharing -> Firewall.  If you do, that could be preventing amuleweb from contacting aMule, maybe even though they're both running on the same computer.
Logged

dazzathedude

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 10
Nearly There
« Reply #4 on: July 04, 2005, 12:52:22 PM »

Hi again ken, this seems odd to me but i seem to be getting there?

I have now found if i move amule into my utilities folder (in applications) then run it normally everything works fine and runs ok (i have tried fixing permission incase you ask?).

But if i put amule into my p2p folder in applications (where the old version was?) it fails and webserver does not run?

this is my amule log below?

2005-07-04 11:52:34: Creditfile loaded, 0 clients are known
2005-07-04 11:52:34: Loaded ipfilter with 0 new IP addresses.

2005-07-04 11:52:35:  - This is aMule 2.0.3 using wxMac v2.6.1 (Unicoded) based on eMule.
2005-07-04 11:52:35:    Running on MacOS (Darwin 7.9.0 Power Macintosh)
2005-07-04 11:52:35:  - Visit http://www.amule.org to check if a new version is available.

2005-07-04 11:52:35: Loading server.met file: /Users/darren/.aMule/server.met
2005-07-04 11:52:37: 125 servers in server.met found
2005-07-04 11:52:37: No part files found
2005-07-04 11:52:37: *** TCP socket (ECServer) listening on 0.0.0.0:4712
2005-07-04 11:52:37: Found 0 known shared files
2005-07-04 11:52:37: Connecting
2005-07-04 11:52:37: Connecting to ## Çѱ¹Çü ´ç³ª±Í (http://shakespeer.net) ## (218.38.14.250 - 218.38.14.250:4661)
2005-07-04 11:52:38: AICH Thread: Syncronization thread started.
2005-07-04 11:52:38: AICH Thread: Masterhashes of known files have been loaded.
2005-07-04 11:52:38: AICH Thread: No new files found.
2005-07-04 11:52:38: AICH Thread: Terminated.
2005-07-04 11:52:38: Connected to ## Çѱ¹Çü ´ç³ª±Í (http://shakespeer.net) ## (218.38.14.250:4661)
2005-07-04 11:52:39: Connection established on: ## Çѱ¹Çü ´ç³ª±Í (http://shakespeer.net) ##
2005-07-04 11:52:39: New clientid is 2200595138
2005-07-04 11:52:40: Saving of server-list completed.


AND THIS IS THE POPUP ERROR I GET.

you requested to run webserver from startup, but the
amuleweb binary cannot be run. please install the package
containing amule webserver, or compile amule using --enable-
webserver and run make install???


this is strange as it was not running in utilities either last week,
so i tried running webserver manually like you suggested earlier in this forum incase this did anything and i still get the same error, and no luck?

for now i have put amule in the utilities folder and an alias where i want it and all seems to be running fine.

any suggestions would be great, but i am glad just to have it running at the mo. :)

best regards

darren

btw: i have enabled run websvr on startup, enable gzip comp., accept ext. connections and use tcp ports with a password in full rights password and the same password in ext. tcp port.
« Last Edit: July 04, 2005, 12:57:09 PM by dazzathedude »
Logged

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
RE: Nearly There
« Reply #5 on: July 05, 2005, 05:55:56 PM »

Hmm.  That is weird.

Can you check console.log to see what messages were written at the time when you ran aMule and it popped up the error about being unable to run amuleweb?

Quote
Originally posted by dazzathedude
so i tried running webserver manually like you suggested earlier in this forum incase this did anything and i still get the same error, and no luck?

This is a bit unclear.  Do you mean that amuleweb still gives the same error ("Connection Failed, Unable to connect to the specified host")?  Or, do you mean that aMule still gives the same popup error?

Just to be painfully clear, here's the procedure I'm interested in knowing the results of:

  • Move aMule to your p2p folder (where auto-launching of amuleweb doesn't work)
  • Run aMule.
  • Dismiss the popup error about amuleweb (I'm expecting this), and let aMule get all the way started up.
  • With aMule running, run amuleweb manually in Terminal.

I'm interested to know the error message if any from amuleweb and the messages written to console.log.  Thanks.  :)
Logged