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

[McIDAS #NHQ-322642]: MDX files

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 #NHQ-322642]: MDX files
  • Date: Fri, 18 Jan 2013 15:59:07 -0700
Hi Paul,

re: help out on McIDAS decoding issues on climate

I logged into climate and found that the McIDAS XCD decoding
processes were not running even though the LDM was running.
After doing a quick check of McIDAS-related things in the
'ldm' account (e.g., does xcd_run exist in the PATH and is
properly configured, etc.) and finding nothing obviously
amiss, I decided to simply restart the LDM:

<as 'ldm'>
ldmadmin restart

After doing this, the McIDAS-XCD decoders are running, and MD
files are once again being created and filled:

mcidas@climate:~/workdata$ ps -u ldm | grep \.k
 1552 ?        00:00:00 readyradarkicko
11533 ?        00:00:00 ingetext.k
11585 ?        00:00:00 startxcd.k
11593 ?        00:00:01 ingetext.k
11594 ?        00:00:42 dmsfc.k
11595 ?        00:00:01 dmraob.k
11596 ?        00:09:19 dmsyn.k

mcidas@climate:~/workdata$ dmap.k MDXX
PERM      SIZE LAST CHANGED FILENAME DIRECTORY
---- --------- ------------ -------- ---------
-rw-  49913736 Jan 18 22:46 MDXX0007 /home/data/mcidas
-rw-  50214936 Jan 18 22:56 MDXX0008 /home/data/mcidas
-rw-   6671952 Jan 18 22:41 MDXX0017 /home/data/mcidas
-rw-   5783600 Jan 18 22:42 MDXX0018 /home/data/mcidas
-rw-   1458496 Jan 18 22:41 MDXX0027 /home/data/mcidas
-rw-   1270480 Jan 18 22:42 MDXX0028 /home/data/mcidas
-rw-   5030032 Jan 18 22:57 MDXX0037 /home/data/mcidas
-rw-   4984996 Jan 18 22:57 MDXX0038 /home/data/mcidas
-rw-    672408 Jan 18 22:41 MDXX0056 /home/data/mcidas
-rw-   8849304 Jan 18 22:45 MDXX0057 /home/data/mcidas
-rw-   8860224 Jan 18 22:45 MDXX0058 /home/data/mcidas
-rw-   5229912 Jan 18 22:43 MDXX0059 /home/data/mcidas
-rw-   5956520 Jan 18 22:41 MDXX0067 /home/data/mcidas
-rw-   5956004 Jan 18 22:56 MDXX0068 /home/data/mcidas
-rw-  15298560 Jan 18 22:54 MDXX0098 /home/data/mcidas
-rw-   7070468 Jan 18 22:41 MDXX0108 /home/data/mcidas
-rw-  14134616 Jan 18 22:41 MDXX0118 /home/data/mcidas
197356244 bytes in 17 files

I don't know why the McIDAS-XCD decoders exited, but I
did see some segmentation violations in the XCD log
file, /home/mcidas/logs/XCD_START.LOG, before restarting
the LDM.  My best guess is that a slug of bad data was
received and this caused the decoders to exit.

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