[Datastream #IZJ-689237]: Additional Datafeeds

Hi Jeff,

re:
> OK.  Out of frustration, I tried something.  One of the decoders that was 
> squawking about
> not being able to read/write was dcmetr.  The file that it couldn't 
> read/write - 20081016_sao.gem
> existed, but was 0k.  I changed the permissions to 777, still nothing.  I 
> finally said,
> "screw it" and deleted the file and, low and behold, dcmetr took right off, 
> created a new
> one and hasn't looked back...
> 
> Any ideas?

Yes.  The fact that deleting the file allowed newly decoded data to be written 
indicates that
the file that had been created, while writable, was damaged.  Deleting it was 
exactly the
correct thing to do in this case as a new one would not have been automatically 
created until
the next day.

> I know what I'd like to do, but don't think I can/should - start over with a 
> new, empty data
> directory location...

No, this is not needed.

Here is what I just did on your machine:

<as 'gempak'>
-- made a symbolic link from /home/gempak/GEMPAK5.11.1 to /home/gempak/NAWIPS

-- edit ~gempak/.bash_profile and finished the setup for GEMPAK use:

NAWIPS=/home/gempak/GEMPAK.5.11.1
export NAWIPS

# Get the aliases and functions
if [ -f ~/NAWIPS/Gemenviron.profile ]; then
        . ~/NAWIPS/Gemenviron.profile
fi

- ran $NAWIPS/ldm/etc/gen_pqact.csh to create individual pqact pattern-action 
files in ~gempak

<as 'ldm'>

- stopped the LDM

  ldmadmin stop

-- edited ~ldm/etc/ldmd.conf:

  - replaced the existing GEMPAK-related 'exec' actions with those specified in 
the output
    from $NAWIPS/ldm/etc/gen_pqact.csh 

- moved the existing GEMPAK-related pattern action files to a newly created 
~ldm/etc/backup
  directory (to clean-up)

- copied the pqact pqttern-action files created by $NAWIPS/ldm/etc/gen_pqact.csh
  from /home/gempak to ~ldm/etc

- copied the GEMPAK5.11.1 decoders from /home/gempak/NAWIPS/os/linux64/bin to 
~ldm/decoders

- ran ldd on the newly copied decoders to make sure that all shared libraries 
needed
  were found:

  cd ~ldm/decoders
  ldd dc*

  These look good.

- by=hand "rotated" the existing GEMPAK decoder log files:

  cd ~/data/gempak/logs
  foreach log (`ls -1 *.log`)
     mv $log ${log}.l
  end

- edited ~ldm/.cshrc to set needed GEMPAK environment variables:

  # Set needed GEMPAK environment variables
  source /home/gempak/NAWIPS/Gemenviron

- restarted the LDM

  ldmadmin start

- edited the crontab for 'ldm' to:

  - add comments

  - remove mailing of messages to 'ldm' (MAILTO="")

  - rotate GEMPAK log files once per day (keep 2):

    - create ~ldm/util directory
    - create dcrotatelog.csh in ~ldm/util

  - rotate ldm-mcidas log files once per day (~ldm/logs/ldm-mcidas.log)

Notes:

- the recopying of the GEMPAK 5.11.1 decoders from 
/home/gempak/NAWIPS/os/linux64/bin may
  not have been necessary (did you already do that?), but it couldn't hurt

- ditto for the ~ldm/etc/ldmd.conf entries

- perhaps ditto for the pqact pattern-action files

I performed these steps to make sure that 5.11.1 actions and decoders are being 
used/run.

Things appear to be running correctly now, but I havn't watched for long enough 
to
be 100% sure that there are no residual problems to address.

As soon as you are convinced that GEMPAK decoding is now working correctly, you 
should
delete the GEMPAK distributions from the ~ldm directory (to clean-up).

Also, when you are convinced that GEMPAK decoding is now working correctly, it 
would be
a good time to review the McIDAS setup and install the current distribution, 
v2008 (you
are still running v2006).

> Thanks.

No worries.

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: IZJ-689237
Department: Support Datastream
Priority: Normal
Status: Closed