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

[McIDAS #RWF-297700]: McIDAS 2015 installation questions

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 #RWF-297700]: McIDAS 2015 installation questions
  • Date: Fri, 28 Aug 2015 16:01:46 -0600
Hi Gilbert,

re: 
> So, I am getting these errors on weather3. I do not know what they mean,
> in /var/log/system.log:
> 
> Aug 27 18:22:35 weather3 abrt[21830]: Saved core dump of pid 6879 
> (/home/mcidas/bin/mcenv) to /var/spool/abrt/ccpp-2015-08-27-18:22:34-6879 
> (806912 bytes)
> Aug 27 18:22:35 weather3 abrtd: Directory 'ccpp-2015-08-27-18:22:34-6879' 
> creation detected
> Aug 27 18:22:36 weather3 abrtd: Executable '/home/ldm/ldm-6.12.14/bin/pqact' 
> doesn't belong to any package and ProcessUnpackaged is set to 'no'
> Aug 27 18:22:36 weather3 abrtd: 'post-create' on 
> '/var/spool/abrt/ccpp-2015-08-27-18:22:33-6844' exited with 1
> Aug 27 18:22:36 weather3 abrtd: Deleting problem directory 
> '/var/spool/abrt/ccpp-2015-08-27-18:22:33-6844'
> 
> What does that mean?

The only McIDAS process running as user 'ldm' is ~ldm/util/mcscour.sh,
and this script calls the McIDAS routine 'mcenv'.  'mcscour.sh's sole
purpose is to scour McIDAS data files, and it may be running for a bit
of time when kicked off.

Given that 'mcscour.sh' is being kicked off by cron, it/mcenv should not
be affected by anything LDM.  It is "interesting", however, that the
latest 'mcenv' core file occurs at the same time as the latest 'pqact'
core file.  I don't understand why this is happening!

By the way, I notice a couple of things that looked a bit off:

1) for some reason you define LIBPATH in the 'ldm's environment

   LIBPATH looks like it came from some other operating system
   as it is not a standard Linux environment variable.  Rather,
   it is a standard AIX environment variable.

2) I see that you define LD_LIBRARY_PATH in the ~mcidas/kickoff
   script, and you put /usr/local/lib first

   A quick look in /usr/local/lib on weather3 shows libraries
   that are from 2004.  They don't look like they should be used
   by anything in McIDAS or the LDM.

Questions:

- have you reviewed your environment variable settings in the 'ldm'
  account to see what old cruft can be removed?

- are the libraries in /usr/local/lib used by anything anymore?

  If yes, are there not newer versions of the libraries?

I will write follow-ups if/when anything else occurs to me...

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: RWF-297700
Department: Support McIDAS
Priority: Normal
Status: Closed