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

[IDD #RDQ-217349]: IDD/LDM startup problem, no data, no log



Hi Mike,

re:
> I'm probably doing something very dumb. Please help me get this going.  :-)

We'll try :-)

> I'm not getting any data and nothing appears in the log. I do not have LDM
> starting at boot time yet. Rather, I am running it per "Activating the LDM 
> Installation".
> (http://www.unidata.ucar.edu/software/ldm/ldm-6.6.5/basics/activating.html) I
> thought I would run it manually at first.

OK, no worries.

> Also, my LDMHOME is not standard, it is "/export/caymus2r/ldm".

Where the LDM is installed is not important as long as the configuration for
things like syslogd logging use the real location.

> All the steps seem to check out OK. When I run "ldmadmin watch" I see stuff 
> like:
> 
> Apr 22 22:16:11 pqutil INFO:      427 20080422221611.797 IDS|DDPLUS 221057152 
>  SAAF35 KWBC 222200 RRB
> Apr 22 22:16:11 pqutil INFO:     1391 20080422221611.797 IDS|DDPLUS 221057153 
>  SXXX90 KWAL 222215
> Apr 22 22:16:11 pqutil INFO:      145 20080422221611.797 IDS|DDPLUS 221057154 
>  SAAW34 KWBC 222045 RRH
> Apr 22 22:16:11 pqutil INFO:      146 20080422221611.797 IDS|DDPLUS 221057155 
>  SAUS80 KWBC 222200 RRE
> Apr 22 22:16:11 pqutil INFO:      106 20080422221611.798 IDS|DDPLUS 221057156 
>  SACA31 KWBC 222200 RRC
> Apr 22 22:16:11 pqutil INFO:       99 20080422221611.798 IDS|DDPLUS 221057157 
>  SACA35 KWBC 222200 RRC
> Apr 22 22:16:11 pqutil INFO:     3730 20080422221611.798 IDS|DDPLUS 221057158 
>  SAUS70 KWBC 222216
> Apr 22 22:16:11 pqutil INFO:      266 20080422221611.798 IDS|DDPLUS 221057159 
>  SAXX60 KWBC 222200 RRJ
> Apr 22 22:16:11 pqutil INFO:      109 20080422221611.798 IDS|DDPLUS 221057160 
>  SPEM31 KWBC 222216
> Apr 22 22:16:11 pqutil INFO:      332 20080422221611.798 IDS|DDPLUS 221057161 
>  SAAU31 KWBC 222200 RRB
> Apr 22 22:16:11 pqutil INFO:      138 20080422221611.798 IDS|DDPLUS 221057162 
>  SAAS32 KWBC 222200 RRC
> Apr 22 22:16:11 pqutil INFO:      977 20080422221611.799 IDS|DDPLUS 221057163 
>  CDUS27 KZHU 222216
> Apr 22 22:16:11 pqutil INFO:      144 20080422221611.799 IDS|DDPLUS 221057164 
>  SAAW34 KWBC 222145 RRF
> Apr 22 22:16:11 pqutil INFO:       99 20080422221611.799 IDS|DDPLUS 221057165 
>  SACA45 KWBC 222200 RRB
> Apr 22 22:16:11 pqutil INFO:      213 20080422221611.799 IDS|DDPLUS 221057166 
>  SAKO31 KWBC 222200 RRA
> Apr 22 22:16:11 pqutil INFO:      258 20080422221611.799 IDS|DDPLUS 221057167 
>  SPUS70 KWBC 222216
> Apr 22 22:16:11 pqutil INFO:     2804 20080422221611.799 IDS|DDPLUS 221057168 
>  SAUS70 KWBC 222216 RRA

Very good; you are receiving IDS|DDPLUS data.

> But nothing is going into the log file:
> 
> bash-2.03$ pwd
> /export/caymus2r/ldm/logs
> bash-2.03$ ls
> ldmd.log
> bash-2.03$ cat ldmd.log
> bash-2.03$

This typically means one of a small number of things:

- you did not setup /etc/syslog.conf entries for LDM logging

- you are on a Linux machine that has SELINUX configured to control
  syslogd logging

- you have some sort of an error in the configuration of /etc/syslog.conf
 
> And I dont see anything other than the product queue in the data directory:
> 
> bash-2.03$ cd ../data
> bash-2.03$ ls
> ldm.pq
> bash-2.03$ ls -l
> total 803872
> -rw-r--r--   1 ldm      unidata  411369472 Apr 21 20:01 ldm.pq
> bash-2.03$

OK.  Troubleshooting product processing will be easier when LDM logging is
working, but let's continue.

> I am attaching my config files. I put some notes in the bottom of my 
> "pqact.conf" file
> to indicate that the only time I did get some data, it appeared in LDMHOME 
> instead
> of LDMHOME/data.

One comment:

The single action in the pqact.conf file that you attached:

PPS ^_ELSE_$    STDIOFILE   -overwrite -flush -close -strip -log    data/\1

uses the '\1' value for file naming.  The regular expression to match products,
however, does not have any pieces that would match the '\1'.  The pieces
are sections of the extended regular expression that are enclosed by 
parentheses.

Next, in order to figure out why when the action worked the products were 
written
to the LDM home directory.

1) Please send the results of the following:

<login as 'ldm'>
cd ~ldm
ls -alt

2) please send us your /etc/syslog.conf file

3) please send the results of:

uname -a

4) please send us the results of:

cat /etc/selinux/config

> Thanks in advance for any help you can offer,

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: RDQ-217349
Department: Support LDM
Priority: Normal
Status: Closed


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.