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

[TIGGE #SHQ-122936]: tigge logging not working on ultrazone

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [TIGGE #SHQ-122936]: tigge logging not working on ultrazone
  • Date: Fri, 06 Oct 2006 13:44:41 -0600
David,

> The ultrazone ldm installation is working well except that nothing is
> being written to the log file ldmd.log.
> The log file is created but it remains a zero-length file forever.
> There are no error messages when the
> the ldm is started:
> 
> $ ldmadmin restart
> Flushing the LDM product-queue to disk...
> Stopping the LDM server...
> Waiting for the LDM to terminate
> Waiting for the LDM to terminate
> Waiting for the LDM to terminate
> The product-queue is OK.
> /usr/local/ldm/etc/pqact.conf is syntactically correct
> Starting the LDM server...
> 
> ldmadmin-pl.conf  contains the standard stuff I think:
> $ grep log *
> ldmadmin-pl.conf:# default number of logs to rotate with the newlog(1)
> command
> ldmadmin-pl.conf:$numlogs = "7";
> ldmadmin-pl.conf:$log_path = "$ldmhome/logs";
> ldmadmin-pl.conf:$log_file = "$log_path/ldmd.log";
> ldmadmin-pl.conf:# set this to 0 if you don't want the ldm log files
> rotated whenever you
> ldmadmin-pl.conf:$log_rotate = "1";
> 
> /etc/syslog.conf looks like this:
> 
> #bunch of comments
> #...
> 
> *.err;kern.notice;auth.notice;local0.none       /dev/sysmsg
> *.err;kern.debug;daemon.notice;mail.crit;local0.none
> /var/adm/messages
> 
> local0.debug    /usr/local/ldm/logs/ldmd.log
> 
> *.alert;kern.err;daemon.err                     operator
> *.alert                                         root
> 
> *.emerg                                         *
> 
> # if a non-loghost machine chooses to have authentication messages
> # sent to the loghost machine, un-comment out the following line:
> #auth.notice                    ifdef(`LOGHOST', /var/log/authlog,
> @loghost)
> 
> mail.debug                      ifdef(`LOGHOST', /var/log/syslog,
> @loghost)
> 
> #
> # non-loghost machines will use the following lines to cause "user"
> # log messages to be logged locally.
> #
> ifdef(`LOGHOST', ,
> user.err                                        /dev/sysmsg
> user.err                                        /var/adm/messages
> user.alert                                      `root, operator'
> user.emerg                                      *
> )
> 
> 
> I am wondering if there is some issue with Solaris 10.
> Here uname -a:
> SunOS ultrazone 5.10 Generic_118833-23 sun4u sparc SUNW,Sun-Fire-V890

Is the syslogd(8) daemon running?

Is the LDM utility ~ldm/bin/hupsyslog owned by root and setuid?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: SHQ-122936
Department: Support IDD TIGGE
Priority: Normal
Status: On Hold