>From: Gilbert Sebenste <address@hidden>
>Organization: NIU
>Keywords: 200504221620.j3MGK3v2005961 ldm-mcidas proftomd
Hi Gilbert,
>What would cause this in the ldmd.conf error log:
>
>Apr 22 15:49:31 climate pqact[32292]: pbuf_flush (5) write: Broken pipe
>Apr 22 15:49:31 climate pqact[32292]: pipe_put:
>-closedecoders/proftomd-vllogs/ldm-mcidas.profiler.log-d/home/data/mcidas-vU6W
> P$
>write error
>Apr 22 15:49:31 climate pqact[32292]: pipe_prodput: trying again
>Apr 22 15:49:31 climate pqact[32292]: pbuf_flush (5) write: Broken pipe
>Apr 22 15:49:31 climate pqact[32292]: pipe_put:
>-closedecoders/proftomd-vllogs/ldm-mcidas.profiler.log-d/home/data/mcidas-vU6W
> P$
>write error
>Apr 22 15:49:31 climate pqact[32292]: child 503 exited with status 1
>Apr 22 15:49:31 climate pqact[32292]: child 505 exited with status 1
This is most likely caused by one of two things:
- the output MD file into which proftomd wants to write exists and is
not writable by the user attempting the write ('ldm')
- more likey, the McIDAS files needed for the decoder do not exist, or
are not readable/viable in the directory in which the decoder wants
to write its output
I am betting that the problem is the second bullet. The solution (if this
is the problem) is to copy the needed files to the output directory:
<as 'mcidas'>
cd ~mcidas
cp data/SCHEMA /home/data/mcidas <- the file most probably missing/bad
cp data/SYSKEY.TAB /home/data/mcidas <- copy may not be needed if file is OK
cp workdata/ROUTE.SYS /home/data/mcidas <- copy may not be needed if file is OK
cd /home/data/mcidas
chmod 666 SCHEMA SYSKEY.TAB ROUTE.SYS
After these changes the decoder should start working _if_ the output MD
file does not already exist (if it already exists, it may be full or
not writable by 'ldm').
>The pqact entry for it seems correct:
>
>FSL2 ^FSL\.NetCDF\.NOAAnet\.windprofiler\.06min
> PIPE
> -close decoders/proftomd -vl logs/ldm-mcidas.profiler.log
> -d /home/data/mcidas -v U6 WPR6 91
No problems with this entry.
>I am helping out COD because they are having problems with this, and I am
>donating a little time to get this fixed. I can verify that in
>/home/data/mcidas, the files are getting written to, and file sizes are
>normal. The MDXX008* files are fine and the pqact entry generates no
>errors.
So, you are saying that the hourly summary profiler data is being decoded
correctly, but the 6 minute profiler data is not?
>I am wondering if they didn't include something in a McIDAS config
>file?
Hmm... if hourly summary decoding is OK, it should mean that the copies
of SCHEMA, SYSKEY.TAB, and ROUTE.SYS in /home/mcidas/data are OK. If
this is the case, the example copies I listed above should not be needed.
Let's see if the schema for the 6 minute profiler data is correctly included
in /home/data/mcidas/SCHEMA:
<as 'mcidas'>
cd workdata
redirect.k ADD SCHEMA \"/home/data/mcidas
lsche.k WPR6
The listing should look like:
/home/mcidas/workdata% lsche.k WPR6
NAME: WPR6 VERSION: 2 DATE: 1998338 TEXTID: "6-MIN WIND PROFILER UPPER AIR D
---- -------
DEFAULT NUMBER OF ROWS: 480 INTEGER ID: 0
COLS: 50 MISSING DATA VALUE:
-2139062144
REPEAT GROUP: NUMBER OF REPETITIONS: 37
STARTING POSITION: 16
SIZE: 4
NUMBER OF KEYS IN ROW HEADER: 4
COL HEADER: 0 STARTING AT POSITION 5
DATA RECORD: 159 STARTING AT POSITION 5
----
163 TOTAL
KEY SCALE UNIT KEY SCALE UNIT KEY SCALE UNIT
---- ----- ---- ---- ----- ---- ---- ----- ----
DAY 0 CYD TIME 0 HMS MODE 0 CHAR
CMAX 0 MOD 0 IDA 0 CHAR
IDB 0 CHAR IDN 0 LAT 4 DEG
LON 4 DEG ZS 0 M PSL 2 MB
T 2 K TD 2 K PCP 2 MM
Z 0 M SPD 2 MPS DIR 0 DEG
VWND 2 MPS
lsche.k: DONE
If it does not (like nothing gets listed), then do the following:
sche.k DCWPR6
lsche.k WPR6
The lsche.k invocation should then show that appropriate listing for the 6
minute profiler schema. If it didn't to begin with but does after registering
the schema, and IF the output MD files for the 6 minute data (MDXX009*) do
not exist, they should now be created.
Cheers,
Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web. If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.