Bug 666 - [Chameleon]No error message when an incorrect IP is set in the configuration file
: [Chameleon]No error message when an incorrect IP is set in the configuration ...
Status: RESOLVED WONTFIX
: Chameleon
Core
: 1.99
: PC Linux
: P2 normal
: 1.99 beta 4
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2004-09-08 11:29 by
Modified: 2004-12-02 21:31 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2004-09-08 11:29:13
No error message is shown when an incorrect IP address is used in the
configuration file for some parameters.  I try to load one of the sample
applications and it hangs forever.  I came across this problem when I'm using my
laptop in two different location.

The IP is used for these two parameters:  "cwc2_url" and "web_server_path" in
"chameleon.xml".

Steps to reproduce:

1.  Used an incorrect IP address in the configuration file for the above parameters.

2.  Load one of the chameleon sample applications.

Mozilla 1.6
Federa Core 2.
Chameleon CVS
------- Comment #1 From 2004-10-21 14:06:12 -------
Changed target to 1.99 RC 1.
------- Comment #2 From 2004-11-04 10:12:32 -------
I just tried this.  Some stuff works, some stuff doesn't.  For instance, the map
image fails to load.  This is because there is an HTTP 404 error - its looking
for an address that doesn't exist.  I'm not sure, but I think this is another of
those things that are so obvious that I don't really want to deal with it.  I
understand that, in your case (and for me too), you have several different
possible configurations depending on whether you are at home or at the office. 
However, this should be considered an abnormal situation as chameleon would not
normally be set up to run from a laptop.  I think that it is a reasonable
assumption that chameleon be correctly configured, and that this configuration
would be done once on installation and then updated if the system changes.  I
think that the existing installation instructions are sufficient to get a
running chameleon instance.  So in this case, the issue is that you changed your
system configuration and did not update Chameleon to reflect the changes.

It would be very difficult, if not impossible, to determine that the
configuration is incorrect (at least in this case).  We can possibly detect
errors like the map image failing to load, but how do we know *why* it failed to
load?  I am marking this as wontfix because I think it is purely a user error in
this case.  If you don't configure stuff correctly, it will break.