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

Re: 19991103: Running LDM on Irix 6.5 (fwd)


===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================

---------- Forwarded message ----------
Date: Wed, 3 Nov 1999 14:52:58 -0700 (MST)
From: Robb Kambic <address@hidden>
To: Erick Lorenz <address@hidden>
Subject: Re: 19991103: Running LDM on Irix 6.5

On Wed, 3 Nov 1999, Erick Lorenz wrote:

> Robb...
> `>
> `> After rebooting ATM12, our current ldm server, to add a disk I cannot
> `> get the ldm to restart.  When I do a "ldmadmin start" it either freezes
> `> or comes back with "LDM started" and a prompt but when I do a ps -ef
> `> there are no ldm processes running.  I recently made some changes
> `> to the system at Tom Yoksas' suggestion which are documented in the dialog
> `> below. I thought I had restarted the ldm since then but maybe not.
> `> Anyway it is behaving differently from previous problems in that nothing
> `> starts.
> `
> `I believe the problem is in pqact.conf somewhere. The ldmd.log file should
> `give you some messages. 
> 
> Actually one of my problems is that ldmd has not been writing to ldmd.log
> even when everything else was working properly.

Erick,

You can start the ldm on the command line with the log messages coming to
the screen to see what the problems are: ie, from LDMHOME

% bin/rpc.ldmd -vl - -q data/ldm.pq etc/ldmd.conf

Also look at this URL to see if syslog is configured correctly;

http://www.unidata.ucar.edu/packages/ldm/ldmPreInstallList.html#s8
 
http://www.unidata.ucar.edu/packages/ldm/ldmBinaryInstallList.html#s7



> 
> `I would comment out the exec pqact entry in the
> `etc/ldmd.conf file and then try to start the ldm. If the ldm starts ok,
> `then the problem is in pqact.conf.  Did you do:
> `
> `% ldmadmin pqactcheck
> 
> Yes I have done this and it finds no errors.
> 
> `This will tell you if the syntax is correct in the pqact.conf file. If the
> `syntax is correct then start to comment out the latest changes made in the
> `pqact.conf file until the culprit one is found.  You don't have to restart
> `the ldm after changing pqact.conf. You can do:
> `
> `% ldmadmin pqactHUP
> `% ldmadmin tail   ( checks the logs to see if pqact.conf file was reread )
> 
> I tried commenting out all the exec and ldm did start.  Then I selectivly
> added them back in. For a while I kept getting core dumps in /home/data/mcidas
>  but that has stopped now.
> 
> I am currently back to my original configuration:
> exec    "pqexpire"
> exec    "xcd_run MONITOR"
> exec    "pqact"
> exec    "pqbinstats"
> #exec   "pqsurf"
> 
> The ldm is running:
> 
> ldm 17800 17808  0 12:26:56 ?       0:00 pqbinstats
> 
> ldm 17801 17808  0 12:26:55 ?       0:00 pqact
> 
> ldm 17808     1  0 12:26:55 ?       0:00 rpc.ldmd -q /usr/local/ldm/data/
>                                          ldm.pq /usr/local/ldm/etc/ldmd.conf
> 
> ldm 17809 17808  0 12:26:56 ?       0:00 rpc.ldmd -q /usr/local/ldm/data/
>                                          ldm.pq /usr/local/ldm/etc/ldmd.conf
> 
> ldm 17814 17808  0 12:26:55 ?       0:01 pqexpire
> 
> ldm 17848  5303  0 12:27:45 pts/8   0:00 /usr/local/ldm/bin/pqutil -f ANY
>                                         -w /usr/local/ldm/data/ldm.pq
> 
> I don't see xcd_run in this list and in fact only AREA files are
> being updated.
> 

% ldmadmin ps   doesn't show the xcd_run program, you need to look at

% ps -eaf | grep xcd_run

You will find more info from the messages on the screen.

Look at:

http://www.unidata.ucar.edu/packages/mcidas/mcx/xcd_troubleshoot.html#pgfId=996751

To analyse the log messages.

Robb...



> Here is my pqact.conf:
> 
> DDPLUS|IDS      ^.*     PIPE
>         xcd_run DDS
> HRS     ^.*     PIPE
>         xcd_run HRS
> #
> MCIDAS  ^(LWTOA3 .*)
>         PIPE    -close
>         lwtoa3
>         -d /home/data/mcidas
>         -l /usr/local/ldm/logs/mcidas.log
> 
> All whitespaces larger than one blank are tabs.
> 
> I think that I may not be understanding the environment assignments
> for xcd_run.
> 
> Would you be willing to log in as ldm on ATM12 and poke around?
> 
> Thanks
> 
> Erick Lorenz, LAWR, UCDavis
> 
> 

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================