aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Amuleweb won't start in FC4  (Read 3884 times)

georgios

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 6
Amuleweb won't start in FC4
« on: October 03, 2006, 06:35:56 PM »

hi,
I did this:
yum remove wxGTK-2.6.3-2.6.3.2.2.fc4
rpm -ivh wx*rpm
rpm -ivh aMule*rpm

with these files present:
wx-base-unicode-2.6.3-1.i586.rpm
wx-gtk2-unicode-2.6.3-1.i586.rpm

aMule-2.1.3-1_FC4.i586.rpm
aMule-amulecmd-2.1.3-1_FC4.i586.rpm
aMule-amulegui-2.1.3-1_FC4.i586.rpm
aMule-daemon-2.1.3-1_FC4.i586.rpm
aMule-webserver-2.1.3-1_FC4.i586.rpm
aMule-wxcas-2.1.3-1_FC4.i586.rpm

and I had amule working.

Then, I set a password from the remote connections menu and set start web server during runtime and I got amuleweb running.
(checked with ps -u user|grep amule)

BUT using a browser (local and lan computer) I could not connect to amuleweb.
So, I disable the password (amuleweb doesn't start) and I run it separately afterwards.

with:
amuleweb -h localhost -p 4711 -v

I got:
looking for template: php-default
checking for directory '/home/internet/.aMule/webserver'... no
checking for directory '/usr/share/amule/webserver'... yes
checking for directory '/usr/share/amule/webserver/php-default'... yes
checking for file '/usr/share/amule/webserver/php-default/login.php'... yes
*** Using template: /usr/share/amule/webserver/php-default/aMule.tmpl
This is amuleweb 2.1.3
Enter password for mule connection:

Creating client...

And there is hangs. No connection, no webserver.
After a while, the process dies as well.

Saying:
connection failed, unable to connect to specified host

Did I do something wrong, or should I say: `good luck with debugging?'
Logged

wardevil

  • Sr. Member
  • ****
  • Karma: -1
  • Offline Offline
  • Posts: 402
Re: Amuleweb won't start in FC4
« Reply #1 on: October 03, 2006, 07:10:46 PM »

Can u post the contents of amule.conf located in ~/.aMule ?
U can also try to run amule from a console to see if any messages helping to solve the problem.
Another shot is to backup your ~/.aMule folder and remove it,then start amule again and set the remote password and restart amule.
Check the results and post them in here,plz.  :baby:

Cheers.
Logged
Linux user nº289016 at Linux counter

georgios

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 6
Re: Amuleweb won't start in FC4
« Reply #2 on: October 03, 2006, 10:31:51 PM »

Hi,
I found a way around it making it work, but I am not sure it is the way it was meant. The layout of your menus suggests that `amuleweb' and `external connections' are two different things and that's why they are independently set, with their own passwords et.c. However, as soon as I activated the external connections, the amuleweb started working on my lan.

Initially, I only set the amuleweb at startup, the Gzip compression, the full rights and low rights user, but not the external connections, because I thought it was an extra setting for separating lan and wan access using a different login port and a different login password. (Since I only meant this pc as a monitorless mule-machine on my home lan, I thought I need not set the remote connections.)

I realised that this was not a good idea, after you told me to run it from bash, in which case it prompted me with a password to use! (apparently the amuleweb process did that when it forket in) so, given I had a password set for amuleweb, I suspected something's missing. So, since only the external connections password was not set, I activated it as well along with the service on port 4712, in which case the amule-web worked on port 4711!  (question: did you come up with this port number after the ... aftershave or something?   :D)

BUT, the whole thing does not make particularly sense, so I suspect a bug of some sort.

You see, if `webserver' and `external connections' should both be activated, what is the point of having them independently selectable? I think it creates some misunderstandings. Also if this is the case, why  different passwords in external and webserver connections? If this is not the case, then how come I have to activate both of them for amuleweb to function?

I also checked this:
I disabled external connections and it stopped working. I disabled the amuleweb password and it stopped allowing me in, although I connect to the amuleweb-page. I tried to have external connections without setting THEIR password and it does not permit me to save the settings, so they won't start, and neither will amule-web.  

So, may I propose that all settings get a yellow note with information about them, when there is a mouse pointer over them? Also that the menu is disambiguated somehow and documented with a howto? (the wiki howto did not particularly help me mentioning: `you should know the difference between the two', i.e. amuleweb and external connections).

offtopic: how about protocol obfuscation? some providers of 4Mbit/s connections in Greece use QoS that make them behave as 0.5Mbit/s connections with aMule, which means `it's about time' to introduce protocol obfuscation to tackle with their traffic shaping, because some friends are "falling back" to windows for mule!  8o

Anyway, have a look at it, and if it doesn't work this way at your end, I'll post my amule.conf too.
Logged

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
Re: Amuleweb won't start in FC4
« Reply #3 on: October 04, 2006, 12:06:25 AM »

There's not just amuleweb which uses external connections. Imagine that you're running amuleweb in order to control your things via the internet. At the same time you have e.g. amulegui in your lan for your room mate. If you use the same password he could access the settings via the web as well, but you don't want him to that. Now, that you can use two different passwords this won't happen.
(Not the best example, but that's more or less the point.)

Protocol obfuscation is going to be implemented, but due to real life-reason this will take a while.
Logged

Seagull

  • Full Member
  • ***
  • Karma: 0
  • Offline Offline
  • Posts: 154
Re: Amuleweb won't start in FC4
« Reply #4 on: October 04, 2006, 12:14:27 AM »

Quote
BUT, the whole thing does not make particularly sense, so I suspect a bug of some sort.

You see, if `webserver' and `external connections' should both be activated, what is the point of having them independently selectable? I think it creates some misunderstandings. Also if this is the case, why  different passwords in external and webserver connections? If this is not the case, then how come I have to activate both of them for amuleweb to function?
Because "external connections" work for more than the webserver, are a general way for applications to connect with amule; one is the amule-cmd, the cli client for amule.

Also, you can have the webserver in a different machine, conneting thh the amule client mahine through the lan, using the "external connections" mechanism.

However i do agree that an activation through the amule gui means that both clients are on the same machine, and checking that both work would save such troubles.
Logged

georgios

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 6
Re: Amuleweb won't start in FC4
« Reply #5 on: October 04, 2006, 11:34:20 AM »

Quote
However i do agree that an activation through the amule gui means that both clients are on the same machine, and checking that both work would save such troubles.

A very simple sanity check could be to warn the user  that amuleweb will not start unless you have `external connections' set and also make sure that amuleweb process won't start either during the startup-sequence of amule, especially if it stays there waiting for a password, which you don't see when starting it from gnome, and which does not affect the proper running of amuleweb, even if you give it there through console.)

The way it is, you expect it to run, you see it running (ps -u user|grep amule), and you start checking firewall rules to see what's wrong and it doesn't connect. It's kind of a trap for the unsuspecting user, which if it comes after a less-than-smooth-installation (*), becomes upsetting.

(*) Regarding installation:
before I removed that:
wxGTK-2.6.3-2.6.3.2.2.fc4

and put these:
wx-base-unicode-2.6.3-1.i586.rpm
wx-gtk2-unicode-2.6.3-1.i586.rpm

the rpm's of amule et friends were properly installed, but when it was about to start, I was given a message that `the library' (question `which one?') was not compatible, although the program required 2.6 compatible with 2.4 and I had 2.6 compatible with 2.4 and 2.2 by its own admission (and installer's infuriation.)

Then, the instructions in the forum were mentioning a download and yum install of working wx files, which was not possible at first, because the rpms were not signed. Eventually (after some ranting) it worked with rpm -ivh (posted the `solution' there too).  

Ok, I got there, because I really like your program and I had the time and I'm not entirely useless with Linux, but were that to be the first application a windows-to-linux-converted would install, he'd jump back into Gates arms shouting: "OHMG" half the way there. (Especially if there is no wiki entry for fedora that points to wx files and no rpm install howto, leaving it hanging in the air that you might have to compile the whole thing, in which case you might get all sort of errors, which although they have to do with wx, for the end-user they are attributed to amule, rendering it a `bad program').  

How about contacting the packager of wxGTK-2.6.3-2.6.3.2.2.fc4 and make sure that what he bottles works with amule? I mean, how many more applications on a desktop linux using wxGTK they get installed on their FC, that they put amule aside as a second priority? If amule is not one of the top 5 check items on the list of a converted to linux, what is?

Of course, they do offer the previous version (I got it yum installed from the freshrpms repository I think), but they do not offer the amuleweb and friends (I installed the whole amule 2.1.3 et friends, because I could not find 2.1.2 amuleweb to add to my existing amule. BTW, did you realise that the previous versions of amule point to the rpm of the latest one?)

The way things are in Fedora (and here), they really spoil the fun with your program and this unfair, because it is a good program. If I were you, I'd go there kick the r's  (well, that's considered suggesting violence, isn't it? :] ) and tidy up my installation instructions and the installation packages.

Still, very good program, keep up the good work.
Logged

wardevil

  • Sr. Member
  • ****
  • Karma: -1
  • Offline Offline
  • Posts: 402
Re: Amuleweb won't start in FC4
« Reply #6 on: October 05, 2006, 12:58:02 AM »

For rpms privided by the amule forum are made by me:
1 - When i was thinking of building amule rpms for fedora core 4,there was only a wxGTK-2.6.2 in the repositories,as version 2.6.2.was a bit buggy i built some wx rpms of my own...terrible to compile i might add....so some errors were made like those signature stuff.
2 - The reason i made those rpms in such a way,wx shared libraries(wx-gtk,wx-base,etc),insteed of monolithic version(wxGTK) like fedora packagers made them is because in many old systems where there is no need for X and all related dependencies,the installation of the wxGTK provided by fedora requires X libs to be installed so in order to have amuled and webserver,for example,you still need to install X libs,so i made a shared version of wx,thats why they are separate rpms,in order to have amuled and webserver, you only need to install wx-base wich is comparatevely small to the monolithic version of wxGTK.
3 - The packaging error like signatures and other errors are mine,not aMule team.
I am not a part of aMule team,I made this for users who are searching an easy alternative to the windows emule client in linux.Thats all.

Cheers.....
Logged
Linux user nº289016 at Linux counter