[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20030502: LDM logging trouble
- Subject: 20030502: LDM logging trouble
- Date: Fri, 02 May 2003 13:27:10 -0600
Dana,
> To: Unidata Support <address@hidden>
> From: Dana Price <address@hidden>
> Subject: Re: 20030502: kickin my server
> Organization: UCAR/Unidata
The above message contained the following:
> This is actually something I've been meaning to email support about. Ever
> since the upgrade to 6.0.10, ldmd dosen't log much at all to it's logfile.
> I get all the usual PNG decoder output in it:
>
> ldmd.log:
> May 02 18:24:52 web.envsci.rutgers.edu pnga2area[4411]: Starting Up
> May 02 18:24:52 web.envsci.rutgers.edu pnga2area[4411]: output file
> pathname: /data/wx/mcidas/AREA0131
> May 02 18:24:52 web.envsci.rutgers.edu pnga2area[4409]: unPNG:: 163436
> 613456 3.7535
> May 02 18:24:52 web.envsci.rutgers.edu pnga2area[4409]: Exiting
>
> But nothing from ldmd itself (startups, shutdowns, connections..). I
> didn't change syslog.conf at all, it's still got:
>
> local0.debug /users/ldm/logs/ldmd.log
>
> And I run 'ldmadmin newlog' regularly, but I still only get output from
> pnga2area..
Well that's weird.
What kind of system is it (i.e., what's the output of the command
"uname -a")?
How is pnga2area being invoked? Is it being explicitly told to log to
the file?
This could take a while to diagnose. Is there any way I could log onto
the system as user LDM?
> Thanks,
> Dana
>
> -----------------------------------------------------------
> Dana Price <address@hidden>
> Systems Administrator Voice: 732-932-5833
> Rutgers, The State University Fax: 732-932-8644
> Department of Environmental Sciences
> Center for Environmental Prediction
> -----------------------------------------------------------
Regards,
Steve Emmerson
>From address@hidden Wed May 14 13:35:41 2003
>cc: address@hidden, <address@hidden>,
> <address@hidden>
>Subject: Rutgers on ldm-6.0.11 / log trouble fixed
FYI,
The upgrade to ldm-6.0.11 fixed the problems I mentioned on the 2nd
regarding ldmd.log being more or less devoid of activity.. it's back to
normal now.
> This is actually something I've been meaning to email support about.
> Ever since the upgrade to 6.0.10, ldmd dosen't log much at all to it's
> logfile. I get all the usual PNG decoder output in it:
>
> ldmd.log:
> May 02 18:24:52 web.envsci.rutgers.edu pnga2area[4411]: Starting Up
> May 02 18:24:52 web.envsci.rutgers.edu pnga2area[4411]: output file
> pathname: /data/wx/mcidas/AREA0131
> May 02 18:24:52 web.envsci.rutgers.edu pnga2area[4409]: unPNG:: 163436
> 613456 3.7535
> May 02 18:24:52 web.envsci.rutgers.edu pnga2area[4409]: Exiting
>
> But nothing from ldmd itself (startups, shutdowns, connections..). I
> didn't change syslog.conf at all, it's still got:
--
-----------------------------------------------------------
Dana Price <address@hidden>
Systems Administrator Voice: 732-932-5833
Rutgers, The State University Fax: 732-932-8644
Department of Environmental Sciences
Center for Environmental Prediction
-----------------------------------------------------------