[103] in installers

home help back first fref pref prev next nref lref last post

Re: MINK is Broken...

daemon@ATHENA.MIT.EDU (Paul B. Hill)
Thu Aug 7 13:58:25 1997

Date: Thu, 07 Aug 1997 13:54:48 -0400
To: Computing Help Desk <computing-help@MIT.EDU>, installers@MIT.EDU
From: "Paul B. Hill" <pbh@MIT.EDU>
Cc: help-super@MIT.EDU
In-Reply-To: <v03020900b00f8edaa0ff@[18.81.0.117]>

> ...
>    Ftp connection failed.  Error code 2002
> ...

Hi,

This information is for support personnel and installer developers. It may
also be appropriate for local experts. It is not appropriate for the
average end user on campus to follow these suggestions.

When you see a repeatable problem with an ftp based installer your first
step should be to manually open an ftp connection to net-dist.mit.edu and
then cd into the mit directory. Do not use a web browser to perform this
operation. Use a command line based ftp client since that will tend to
provide you with more detailed information. 

If you are not able to make the connection this may imply that there is a
problem with the ftp service on net-dist. If the error message seems to
indicate this then report the problem to network@mit.edu. You should
consider a subject line along the lines of, "net-dist ftp problem at
11:00am 7 August". You probably already know the proper steps to take if
this does not resolve the problem. If you don't know how to escalate the
problem report please talk to your supervisor.

If you are able to connect to net-dist using an ftp client then you should
report the problem to the installers@mit.edu.

In addition to providing a description of the problem and the error message
or number displayed to the end user you should attempt to provide more
information. In the case of Windows based ftp installers some log
information is available and the log files should be included as text into
the problem report. Each Windows based installer puts a log file into the
\net\mit directory (assuming some defaults here). In the case of the MINK
installer this log file will be \net\mit\mink.log. There is also a seperate
ftp log file created by these applications. This provides us with more
details about the ftp process itself.

In the case of MINK the ftp log will be put into a MINK subdirectory under
the machine's temp directory. Note that the location of the temp directory
is set by an environment variable. In may case the TEMP environment
variable is c:\temp. This means that the ftp log file for the mink
installer can be found in c:\temp\mink\minkftp.log

Following this procedure should help us to resolve problems more
efficiently. Thnaks for your help and cooperation.

Paul



home help back first fref pref prev next nref lref last post