20031001: 20031001: 20030930: 20030930: upgrade to 6.0.14 and GEMPAK dcmetr problems (cont.)

Kevin,

I see log entries of multiple instances starting up  at your ldm restart time.
>[1084] 031001/1749 [DC 3]  Starting up. Version 5.6.k
>[1086] 031001/1749 [DC 3]  Starting up. Version 5.6.k

Its odd to see those 2 process numbers consecutively unless there is a 
permission 
problem, disk space problem, or more than 1 dcmetr entry.

Assuming that you only have 1 dcmetr instance in your pqact.conf file,
You may need to make sure that your LDM usr has access to the GEMPAK tree.
Do you need to add the user to a RH group?

To be safe, you may need to cd to $NAWIPS and do a "chmod -R a+r *"
so that the file permissions for the gempak tables are readable by
the world in case unpacking the distribution tarfile had different
umask settings.

Since you say that the file eventually gets created, have you verified that
disk space isn't an issue? I'm assuming that the disk is local and not
subject to NFS mounting.

Steve Chiswell



>From: "Kevin W. Thomas" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200310012315.h91NFsk1013891

>>Kevin,
>>
>>You have 2 dcmetr decoder entries writing to the same output file.
>>This is unnecessary, and won't work- the decoders will be stepping on
>>the output file....and storing the same sets of data.
>>
>>Note that WMO feedtype abbreviation is the aggregation of HDS, IDS, DDS, and 
> PPS.
>>Also, DDPLUS is the aggregation of DDS and PPS.
>>
>>So "WMO       ^S[AP]" is essentially the same as "IDS|DDPLUS ^S[AP]" since
>>you won't find any SA or SP under the HDS feed.
>>
>>Here is the entry that I provide with the distribution:
>>#
>># US and Canadian sfc obs and specials
>>#
>>WMO     ^S[AP]
>>        PIPE    decoders/dcmetr -v 2 -a 500 -m 72 
>>      -s sfmetar_sa.tbl
>>        -d data/gempak/logs/dcmetr.log
>>        -e GEMTBL=@GEMTBL@
>>        data/gempak/surface/YYYYMMDD_sao.gem
>>
>>also note, you have -v 999 in one of the entries. The GEMPAK logging 
>>supports levels up to 4. 
>>
>>Steve Chiswell
>
>Steve...
>
>I commented out one of the "dcmetr" entries, removed the old ".gem" files and
>started things up.  In about 15 minutes, I've had a few signal 11 messages.
>I went ahead and gdb'd one of the core dumps.  Output looks like all that I've
>seen. 
>
>******************************************************************************
> *
>
>[ldm@quadling ~]$ gdb dcmetr core
>GNU gdb Red Hat Linux (5.2-2)
>Copyright 2002 Free Software Foundation, Inc.
>GDB is free software, covered by the GNU General Public License, and you are
>welcome to change it and/or distribute copies of it under certain conditions.
>Type "show copying" to see the conditions.
>There is absolutely no warranty for GDB.  Type "show warranty" for details.
>This GDB was configured as "i386-redhat-linux"...
>(no debugging symbols found)...
>Core was generated by `/usr/GEMPAK5.6/bin/linux/dcmetr -b 9 -m 24 -p /usr/GEMP
> AK5.6/gempak/tables/pack'.
>Program terminated with signal 11, Segmentation fault.
>Reading symbols from /lib/i686/libm.so.6...done.
>Loaded symbols for /lib/i686/libm.so.6
>Reading symbols from /lib/i686/libc.so.6...done.
>Loaded symbols for /lib/i686/libc.so.6
>Reading symbols from /lib/ld-linux.so.2...done.
>Loaded symbols for /lib/ld-linux.so.2
>#0  0x08089fa4 in strcpy () at strcpy:-1
>-1     strcpy: No such file or directory.
>       in strcpy
>(gdb) bt
>#0  0x08089fa4 in strcpy () at strcpy:-1
>#1  0x00000042 in ?? ()
>#2  0x0806661b in strcpy () at strcpy:-1
>#3  0x0804b820 in strcpy () at strcpy:-1
>#4  0x080494fc in strcpy () at strcpy:-1
>#5  0x40062657 in __libc_start_main (main=0x8049370 <strcpy+284>, argc=10, 
>    ubp_av=0xbfffe5e4, init=0x8048e1c, fini=0x808afd0 <__umoddi3+496>, 
>    rtld_fini=0x4000dcd4 <_dl_fini>, stack_end=0xbfffe5dc)
>    at ../sysdeps/generic/libc-start.c:129
>
>******************************************************************************
> *
>
>Here is "ldmd.log" (with early parts stripped out) since I restarted it:
>
>Oct 01 22:49:39 quadling rpc.ldmd[358]: Starting Up (version: 6.0.14; built: S
> ep 29 2003 16:45:36) 
>Oct 01 23:00:31 quadling pqact[360]: child 1687 terminated by signal 11 
>Oct 01 23:05:28 quadling pqact[364]: child 1686 terminated by signal 11 
>Oct 01 23:05:28 quadling pqact[360]: child 8611 terminated by signal 11 
>Oct 01 23:07:33 quadling pqact[364]: child 11730 terminated by signal 11 
>
>******************************************************************************
> *
>
>Here are "dcmetr.log" entries:
>
>[30807] 031001/1747 [DC 2]  read 285/88741 bytes strt 13659 newstrt 13944
>[30807] 031001/1747 [DC 2]  read 96/88456 bytes strt 13944 newstrt 14040
>[30808] 031001/1748 [DC 2]  Interrupt Signal
>[30808] 031001/1748 [DC 5]  Normal termination.
>[30807] 031001/1748 [DC 2]  Interrupt Signal
>[30808] 031001/1748 [DC 2]  Number of bulletins read and processed: 79
>[30807] 031001/1748 [DC 5]  Normal termination.
>[30808] 031001/1748 [DC 6]  Shutting down.
>[30807] 031001/1748 [DC 2]  Number of bulletins read and processed: 79
>[30807] 031001/1748 [DC 6]  Shutting down.
>[30805] 031001/1748 [DC 2]  Interrupt Signal
>[30804] 031001/1748 [DC 2]  Interrupt Signal
>[30805] 031001/1748 [DC 5]  Normal termination.
>[30804] 031001/1748 [DC 5]  Normal termination.
>[30805] 031001/1748 [DC 2]  Number of bulletins read and processed: 79
>[30804] 031001/1748 [DC 2]  Number of bulletins read and processed: 79
>[30805] 031001/1748 [DC 6]  Shutting down.
>[30804] 031001/1748 [DC 6]  Shutting down.
>[1084] 031001/1749 [DC 3]  Starting up. Version 5.6.k
>[1086] 031001/1749 [DC 3]  Starting up. Version 5.6.k
>[1084] 031001/1749 [FL -3]  Cannot create file /arpsdata2/ldm3/ingest/gempak/s
> urface/031001_sao.gem.
>[1084] 031001/1749 [DM -1]  File /arpsdata2/ldm3/ingest/gempak/surface/031001_
> sao.gem cannot be created.
>[1084] 031001/1749 [SF -1]  File /arpsdata2/ldm3/ingest/gempak/surface/031001_
> sao.gem could not be created.
>[1084] 031001/1749 [SF -1]  File /arpsdata2/ldm3/ingest/gempak/surface/031001_
> sao.gem could not be created.
>[1084] 031001/1749 [FL -4]  Cannot read file ....
>[1086] 031001/1749 [DC -9]  End of input data file.
>[1086] 031001/1749 [DC 5]  Normal termination.
>[1086] 031001/1749 [DC 2]  Number of bulletins read and processed: 21
>[1086] 031001/1749 [DC 6]  Shutting down.
>[1084] 031001/1749 [DC -9]  End of input data file.
>[1084] 031001/1749 [DC 5]  Normal termination.
>[1084] 031001/1749 [DC 2]  Number of bulletins read and processed: 21
>[1084] 031001/1749 [DC 6]  Shutting down.
>[1686] 031001/1749 [DC 3]  Starting up. Version 5.6.k
>[1687] 031001/1749 [DC 3]  Starting up. Version 5.6.k
>[8611] 031001/1800 [DC 3]  Starting up. Version 5.6.k
>[1686] 031001/1805 [FL -3]  Cannot create file /arpsdata2/ldm3/ingest/gempak/s
> urface/031002_sao.gem.
>[1686] 031001/1805 [DM -1]  File /arpsdata2/ldm3/ingest/gempak/surface/031002_
> sao.gem cannot be created.
>[1686] 031001/1805 [SF -1]  File /arpsdata2/ldm3/ingest/gempak/surface/031002_
> sao.gem could not be created.
>[1686] 031001/1805 [SF -1]  File /arpsdata2/ldm3/ingest/gempak/surface/031002_
> sao.gem could not be created.
>[11731] 031001/1805 [DC 3]  Starting up. Version 5.6.k
>[11730] 031001/1805 [DC 3]  Starting up. Version 5.6.k
>[12967] 031001/1807 [DC 3]  Starting up. Version 5.6.k
>
>I've had all the programs with LDM 6.0.14 sometimes complain with "File xxx.ge
> m
>cannot be created" messages, though the files eventually get created.  I don't
>see similar messages in the LDM 5.x logs.
>
>       == kwthomas ==
>