[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[McIDAS #JTG-722928]: installation error

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [McIDAS #JTG-722928]: installation error
  • Date: Wed, 29 Jul 2015 12:00:14 -0600
Hi Justin,

re:
> This time, I explicitly set the group in permissions by entering *chown -R
> mcidas:mcidas /home/mcidas* and the install finished.

Excellent!  This implies that the ~mcidas/bin directory was owned by
'mcidas' but the group part of the ownership was different.  I am not
sure how this would have happened if your rebuild efforts were done
entirely as 'mcidas'.

re:
> I did not receive any
> errors, but it did not mention anything about completing the install at the
> end of the process either.

The ~mcidas/mcidas2015/src/makelog file should include a time stamp for
when the build started and when it finished.

re:
> I am including the logs for both make and install.
> 
> After the install, I sourced and then logged out. The source info is
> included in the log.

I see that log file pieces that you included do contain the start and
end times for the build:

##########################################
Wed Jul 29 08:10:01 EDT 2015: BUILD INIT
##########################################

 ...


##########################################
Wed Jul 29 08:18:28 EDT 2015: BUILD END           <- end of McIDAS-X build
##########################################

 ...

##########################################
Wed Jul 29 08:18:58 EDT 2015: BUILD END           <- end of McIDAS-XCD build
##########################################

The installation portion of the build/install does not include a BUILD END
time clause, and this is normal.

re:
> Then I proceeded to login as <awips> and sourced and then logged out and
> back in again. The source info is included in the log.

?? I do not understand why you are logging in as 'awips'.  Are you somehow
trying to double duty the 'awips' and 'mcidas' accounts?  If yes, I can
assure you that this is a bad idea.

re:
> However, when I try to start mcidas using the command *mcidas* , I get
> command not found.

Try to run 'mcidas' as who?  'mcidas' or 'awips'?

re:
> For the log, you can search* make all* and *make install.all* to see where
> each log begins.

I reviewed the file you attached and see nothing to be concerned with.

Question:

- when you login as 'mcidas', what is the output from:

echo $PATH

which mcidas

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: JTG-722928
Department: Support McIDAS
Priority: Normal
Status: Closed