[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20011026: working on FSL2 6-minute profiler decoding on weather
- Subject: 20011026: working on FSL2 6-minute profiler decoding on weather
- Date: Fri, 26 Oct 2001 14:20:24 -0600
>From: Unidata User Support <address@hidden>
>Organization: Unidata Program Center/UCAR
>Keywords: LDM ldm-mcidas McIDAS
Dave,
I am the one stopping and restarting the LDM on weather. I am trying to
find out why the 6-minute profiler decoding is not working.
On a related note, I see that the LDM on weather has not been logging
since April:
weather:~/etc%cd ~ldm/logs
%ls -alt ldmd.log*
weather:~/logs> ls -alt ldmd.log*
-rw-r--r-- 1 ldm ldm 0 Apr 18 2001 ldmd.log
-rw-rw-rw- 1 ldm ldm 106057 Apr 18 2001 ldmd.log.1
-rw-r--r-- 1 ldm ldm 216061 Apr 18 2001 ldmd.log.2
-rw-r--r-- 1 ldm ldm 38145 Apr 17 2001 ldmd.log.3
The error seen when starting the LDM is:
starting the LDM server...
syslogd: no process killed
hupsyslog: system("/etc/killall -HUP syslogd") returns 256
(E.G. It didn't work. Check that this program is setuid)
the LDM server has been started
This is the old "Debian doesn't run syslogd, it runs syslog-ng":
weather:~/logs> ps -eaf | grep syslog
root 165 1 0 Sep11 ? 00:48:49 /sbin/syslog-ng
ldm 29687 20401 0 15:18 pts/24 00:00:00 grep syslog
Didn't we figure out a fix for this sometime back? It really should be
fixed so we can log the output from decoders. This will help find out
why the 6-minute profiler decoding is no longer working.
Tom
>From address@hidden Fri Oct 26 14:23:40 2001
>Subject: Re: 20011026: working on FSL2 6-minute profiler decoding on weather
Well still dont know how to set up syslog-ng to log to the ldm port but if
you look under /var/log/debug.log I think thats where all the DEBUG
messages (this includes LDM) goes to.
Ya thanks for letting me know at least, i figured out it was you when i
saw the logins coming from gale.unidata.ucar.edu. and idle times of 0
seconds :)
TTYL
-dave