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

[LDM #KTG-709466]: ldm 6.10.1 log problem



Trent,

There's still something wrong with LDM logging: the LDM log file is missing 
messages and the system log file doesn't have them.

May I log onto the system in question as the LDM user in order to diagnose the 
problem? If so, then please add the attached public key file to 
~ldm/.ssh/authorized_keys and tell me the fully-qualified name of the host.

> I only see:
> 
> 2014-03-11T03:19:06.937528+00:00 netrs-sgpc1 rsyslogd-2039: Could not
> open output file '/home/ldm/var/logs/ldmd.log' [try
> http://www.rsyslog.com/e/2039 ]
> 2014-03-11T14:42:49.959458+00:00 netrs-sgpc1 rsyslogd: [origin
> software="rsyslogd" swVersion="5.8.10" x-pid="2121"
> x-info="http://www.rsyslog.com";] rsyslogd was HUPed
> 2014-03-11T14:53:32.134152+00:00 netrs-sgpc1 rsyslogd: [origin
> software="rsyslogd" swVersion="5.8.10" x-pid="2121"
> x-info="http://www.rsyslog.com";] rsyslogd was HUPed
> 2014-03-11T15:00:04.896196+00:00 netrs-sgpc1 rsyslogd: [origin
> software="rsyslogd" swVersion="5.8.10" x-pid="2121"
> x-info="http://www.rsyslog.com";] rsyslogd was HUPed
> 
> I think I've got the rsyslog problem fixed, though.
> 
> Thanks,
> 
> Trent
> --
> Trent Doyle
> Systems Admin. III
> Southern Great Plains
> Office: 580-388-4053


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: KTG-709466
Department: Support LDM
Priority: Normal
Status: Closed

Attachment: id_rsa.pub
Description: Binary data


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.