Re: 19990121: LDM-5.0.6 Problem

Jim,

I talked to Glenn about this problem. Your need to do some investigative
work on the LDM ulog.

% cd src/ulog
% rm ulog.o
% make test

This will show some output to the screen.

% test0

This should write to the ldmd.log file.
If it doesn't, you going to look at the BSD ifdefs in the ulog.c file. The
first one I would use would be for:

#if (LOG_NFACILITIES > 0) 

change to 

#if 1

recompile and start over until it write to the ldmd.log file.  When you
get it to work then do

% make clean 

in the ulog directory. Then in the src directory

% make install
% make install_setuids

We don't have a system here to check out the correct defines but it
shouldn't be too hard.  Let me know your results so that I can enter in
the ldm support DB.

Thanks,
Robb...



On Mon, 25 Jan 1999, Jim Koermer wrote:

> Robb Kambic wrote:
> > 
> > Jim,
> > 
> > What are the results of:
> > 
> > % strings ulog.o
> >
> Robb,
> 
> Here is what I get:
> 
> <ldm>strings ulog.o
> 8-u#
> <u;j>
> ulog
> /dev/log
> <%d>
> %b %d %H:%M:%S
> [%d]
> /dev/console
> Going silent
> Adding debug
> Adding verbose
> Going verbose
> : %s
> assertion "%s" failed: file "%s", line %d
> regexp(3l): %s
> 
> ****
> 
> > Also, try running the LDM in debug mode and the doing a trace command on
> > the ldm.  There are man pages for instructions. UPC doesn't have a FreeBSD
> > system, our system is BSDI. For some reason, I don't thing that ulog is
> > being compile correctly because it's not getting the correct flags.
> 
> I'll check this out.
> 
> > Also,
> > what version/maker of FreeBSD do you have installed.
> >
> 
> I am using FreeBSD Version 3.0 from freebsd.
>  
> > Robb...
> > 
> > On Fri, 22 Jan 1999, Jim Koermer wrote:
> > 
> > > Robb,
> > >
> > > I tried the test script with logger and got the following lines:
> > >
> > > Jan 22 15:24:38 cyclone test[19673]: err
> > > Jan 22 15:24:38 cyclone test[19675]: warning
> > > Jan 22 15:24:38 cyclone test[19677]: notice
> > > Jan 22 15:24:38 cyclone test[19679]: info
> > >
> > > in my ldmd.log file. The test seems to work okay. However, nothing else
> > > seems to want to write to ldmd.log. The files to shuffle on an stop and
> > > start, so ldmadmin must know that the files are there.
> > >
> > >                               Jim
> > >
> > > Robb Kambic wrote:
> > > >
> > > > Jim,
> > > >
> > > > I forgot about the logger command. Look in the src/ulog directory, there
> > > > are instructions on how to use it. Let me know the results.
> > > >
> > > > Thanks,
> > > > Robb...
> > > >
> > > > On Thu, 21 Jan 1999, Jim Koermer wrote:
> > > >
> > > > > Robb Kambic wrote:
> > > > > >
> > > > > > On Thu, 21 Jan 1999, Unidata Support wrote:
> > > > > >
> > > > > > > >To: address@hidden
> > > > > > > >From: Jim Koermer <address@hidden>
> > > > > > > >Subject: LDM-5.0.6 Problem
> > > > > > > >Organization: .
> > > > > > > >Keywords: 199901211542.IAA22899
> > > > > > >
> > > > > > > I have just finished installing LDM-5.0.6 on a FreeBSD machine. 
> > > > > > > I'm
> > > > > > > feeding it with another of my machines. Data seems to be 
> > > > > > > ingesting okay,
> > > > > > > but I can't seem to generate an ldmd.log, no matter what I have 
> > > > > > > tried.
> > > > > > > Any ideas on what might be my problem?
> > > > > > >
> > > > > > >                               Jim
> > > > > >
> > > > > > Jim,
> > > > > >
> > > > > > There is no /etc/syslog.pid file on BSD, so one has to use the 
> > > > > > killall
> > > > > > command. I would first test it from the command line aw user root.
> > > > > >
> > > > > > % /usr/bin/killall -HUP syslogd
> > > > > >
> > > > >
> > > > > It seemed to work. At least, I didn't get any error messages.
> > > > >
> > > > > > If that works, then create a new hupsyslog in the bin directory by 
> > > > > > making
> > > > > > a hupsyslog shell script.
> > > > > >
> > > > > > #! /bin/sh
> > > > > > #
> > > > > > # Script to send a SIGHUP to syslog(8), causing it to close and 
> > > > > > reopen
> > > > > > # all log files.
> > > > > > # NB: Must be run by root or the killall(1) will fail;
> > > > > > #
> > > > > > /usr/bin/killall -HUP syslogd || exit 1
> > > > > >
> > > > > > Then execute these commands as root to make the correct permissions:
> > > > > >
> > > > > > % chmod 550 hupsyslog
> > > > > > % chown root hupsyslog
> > > > > > % chmod u+srwx,g+rwx,o+rx hupsyslog
> > > > > >
> > > > >
> > > > > I did all of the above.
> > > > >
> > > > > > If syslogd doesn't get a HUP, then it doesn't know about the 
> > > > > > ldmd.log
> > > > > > file.  For sanity sake, you did edit syslog.conf and add 
> > > > > > local0.debug etc
> > > > >
> > > > > These items were done before my initial attempts.
> > > > >
> > > > > > and did a touch on the ldmd.log file.
> > > > > >
> > > > >
> > > > > This was also done.
> > > > > > Review at:
> > > > > > http://www.unidata.ucar.edu/packages/ldm/ldmPreInstallList.html#s8
> > > > > >
> > > > >
> > > > > I followed this guidance line by line.
> > > > >
> > > > > Robb,
> > > > >
> > > > > I'm still getting no ldmd.log file, even though everything else seems 
> > > > > to
> > > > > be working okay.
> > > > >
> > > > > I did build LDM 5.0.3 on an older FreeBSD machine several years ago 
> > > > > and
> > > > > it has been working fine and building a log file without problem. I
> > > > > tried cross checking each configuration item and still am not turning 
> > > > > up
> > > > > any clues.
> > > > >
> > > > >                                       Jim
> > > > >
> > > > >                               Jim
> > > > > --
> > > > > James P. Koermer                  E-Mail: address@hidden
> > > > > Professor of Meteorology          Office Phone: (603)535-2325
> > > > > Chair, Natural Science Department   Office Fax: (603)535-2723
> > > > > Plymouth State College                    WWW: 
> > > > > http://vortex.plymouth.edu/
> > > > > Plymouth, NH 03264
> > > > >
> > > >
> > > > ===============================================================================
> > > > Robb Kambic                                Unidata Program Center
> > > > Software Engineer III                      Univ. Corp for Atmospheric 
> > > > Research
> > > > address@hidden                   WWW: http://www.unidata.ucar.edu/
> > > > ===============================================================================
> > >
> > > --
> > > James P. Koermer                  E-Mail: address@hidden
> > > Professor of Meteorology          Office Phone: (603)535-2325
> > > Chair, Natural Science Department   Office Fax: (603)535-2723
> > > Plymouth State College                    WWW: http://vortex.plymouth.edu/
> > > Plymouth, NH 03264
> > >
> > 
> > ===============================================================================
> > Robb Kambic                                Unidata Program Center
> > Software Engineer III                      Univ. Corp for Atmospheric 
> > Research
> > address@hidden                   WWW: http://www.unidata.ucar.edu/
> > ===============================================================================
> 
> --
> James P. Koermer                    E-Mail: address@hidden
> Professor of Meteorology            Office Phone: (603)535-2325
> Chair, Natural Science Department   Office Fax: (603)535-2723
> Plymouth State College              WWW: http://vortex.plymouth.edu/
> Plymouth, NH 03264
> 

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================