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

Re: Possible cause of problem? (fwd)

Good Morning Jim,

I'll tackle your messages in reverse order.  I'll try to pick out the
unresolved issues...


"James R. Frysinger" wrote:
> 
>         After I fixed those two links I mentioned earlier (entry in
> syslog.conf and link from /usr/local/ldm) pqact started converting
> files like crazy. A whole bunch of directories got created in my ldm
> data area and they contain files with .wmo extensions. I noticed a few
> errors flashing by but couldn't catch them. One had to do with OZONE, I
> remember seeing.
> 
>         Still no sign that statistics are building.
> 

Let's hold off on statistics for the moment...  Glad to hear you're able
to file data.


>         I did "pqactHUP" followed by "ldmadmin tail" with these results:
> /export/home/ldm 78 > ldmadmin pqactHUP
> Check pqact HUP with command  ldmadmin tail
> Hangup
> /export/home/ldm 79 > ldmadmin tail
>    [nothing happened here for several minutes so I used ^C]
> ^C/export/home/ldm 80 >
> 

ldmadmin tail won't show you anything, as the log is apparently still
not being written.  This is important to solve.

Maybe you've actually fixed the logging problem with the changes you
made to syslog.conf, but, depending on the start up sequence, you might
not see anything written to the log if you can't get the ldm to start
properly.  (When it starts up the ldm hups the syslog daemon to get it
to log to ldmd.log.)

Otherwise: 

Please send me a copy of your /etc/syslog.conf file.  Or, just send me
the entries in the file that have the string 'ldm' in them.

Are you sure the syslog daemon is running?  Try 'ps -ef | grep syslog'.


> 
>         I did try this and now I'm stuck. I had one heck of a time
> getting LDM started yesterday but attributed that to operator error on
> my part. I just now tried to stop and restart LDM and this is what
> happened, closely resembling the problems I had starting LDM the first
> time:
> weather[1] ldmadmin stop   [here I am logged in as ldm]
> stopping the LDM server...
> Jan 11 22:19:35 UTC weather.cofc.edu : make_lockfile: another ldmadmin 
> process exists
> weather[2] ldmadmin start
> starting the LDM server...
> Jan 11 22:19:46 UTC weather.cofc.edu : make_lockfile: another ldmadmin 
> process exists
> 
>  I went in as root and killed off the residiual oper processes but
> that did not help. I don't know what to do from here except to diddle
> around until I get LDM restarted and running like I did yesterday,
> somehow. One of the things I did yesterday that seemed to be a part of
> the solution was to kill off all rpc processes and to rm ldmd.pid.
> That didn't help today.By the way, pqact says nothing is coming in now,
> as confirmed by ldmadmin watch. And ldmadmin log is still null:
> 

This message can be misleading.  The ldm uses two files for housekeeping
purposes: /tmp/.ldmadmin.lck and ~ldm/ldmd.pid.  If ldm processes die an
unusual death one or the other of these files may be left lying around,
which would confuse the ldm when it goes to start up again.  If you're
sure that the ldm is not running, but are having this problem, do
'ldmadmin clean' to mop up.  This should allow you to start the ldm
properly.

Consider, however, that if the an ldm process died an unusual death, it
might have left the queue in a wierd/corrupted state.  If you do
'ldmadmin clean' but still have trouble starting, try deleting then
remaking the queue.

In summary, at this point, I suggest you do 'ldmadmin clean', remake the
queue (just to be sure to start with a clean slate), then try restarting
the ldm.  Hopefully it will start up, and the changes you made to
syslog.conf will get the logging going.

I'll now look back at your previous message.

Anne
-- 
***************************************************
Anne Wilson                     UCAR Unidata Program            
address@hidden                 P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************