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.
Hi Doug, re: > We're having trouble getting ldm to write to it's logfile on a linux > system. LDM is opening the logfile, but not writing anything to it. > > Is there a standard configuration error users encounter in writing the > ldmd.log file on linux system? Typically we see that sites don't: - configure /etc/syslog.conf - have not turned off SELINUX - have not performed the final LDM installation step (which is the 'make install_setuids' step that needs to be done as 'root') - there is some write permission issue with the LDM log file or LDM logs directory > We've followed all of the setup instructions found in: > > http://www.unidata.ucar.edu/software/ldm/ldm-6.8.1/basics/preinstallation.html > > under "Edit file /etc/syslog.conf" The thing to do at this point is test to see if logging should be working: <as 'ldm'> logger -p local0.debug 'test of LDM logging' After running 'logger', check the size/contents of ~ldm/logs/ldmd.log. If the test log message is not in the file, recheck the /etc/syslog.conf settings (or /etc/rsyslog.conf on newer Fedora systems); and/or check to make sure that SELINUX is disabled (in /etc/selinux/config, SELINUX needs to be set to disabled or permissive; if this needs changing, the machine has to be rebooted for the change to take effect). I these do not work, please send us the contents/output of: /etc/syslog.conf /etc/selinux/config ps -eaf | grep syslog ls -alt ~ldm/logs > Thanks, No worries. > Begin forwarded message: > > > From: Paul Goodman <address@hidden> > > Date: August 28, 2009 9:43:36 AM MDT > > To: Douglas Schuster <address@hidden> > > Cc: Chi-Fan Shih <address@hidden> > > Subject: Re: [Fwd: Re: ldm can not write to /home/ldm/logs or /TIGGE/ > > dasg011] > > > > Is there an LDM command I can use for testing? I'd like to play > > around a bit with some different things, and it'd probably be easier if we > > didn't have all the back and forth and I could just run a command to test > > logging. > > > > -Paul > > > > Douglas Schuster wrote: > >> That didn't work either. > >> > >> > >> On Aug 27, 2009, at 3:23 PM, Paul Goodman wrote: > >> > >>> hmmmm, I think it may be a permissions issue with the CAVES storage. > >>> Syslog > >>> logs as root, even though LDM runs as the ldm user, and a local > >>> root user > >>> won't have permissions on the network storage. Just to test this, > >>> I've > >>> created a local log file in /usr/local/ldm. Can yo try again to > >>> see if it > >>> will log there? > >>> > >>> -Paul > >>> > >>> Douglas Schuster wrote: > >>>> Paul, > >>>> > >>>> I'm not seeing the ldm output in /var/log/messages anymore, but > >>>> I'm also > >>>> not seeing it in /home/ldm/logs/ldmd.log > >>>> I did log out and log back in after you made the changes. > >>>> > >>>> Doug > >>>> > >>>> > >>>> On Aug 27, 2009, at 2:59 PM, Paul Goodman wrote: > >>>> > >>>>> I restarted the syslog service and it should be logging to > >>>>> /home/ldm/logs now. > >>>>> > >>>>> -Paul > >>>>> > >>>>> Douglas Schuster wrote: > >>>>>> Guys, > >>>>>> > >>>>>> It looks like the ldm log is currently going into /var/log/ > >>>>>> messages > >>>>>> instead of /home/ldm/logs/ldmd.log > >>>>>> > >>>>>> Doug > >>>>>> > >>>>>> > >>>>>> On Aug 27, 2009, at 1:15 PM, chifan wrote: > >>>>>> > >>>>>>> FYI. > >>>>>>> > >>>>>>> -- > >>>>>>> address@hidden, Tel:303/497-1833, Fax:303/497-1291, > >>>>>>> http://dss.ucar.edu > >>>>>>> Mail: NCAR, P.O. Box 3000, Boulder, CO 80307-3000 > >>>>>>> Overnight: NCAR, ML 288A, 1850 Table Mesa Drive, Boulder, CO > >>>>>>> 80305 > >>>>>>> > >>>>>>> > >>>>>>> *From: *Paul Goodman <address@hidden <mailto:address@hidden > >>>>>>> >> > >>>>>>> *Date: *August 27, 2009 12:32:00 PM MDT > >>>>>>> *To: *chifan <address@hidden <mailto:address@hidden>> > >>>>>>> *Cc: *Joseph Mendoza <address@hidden <mailto:address@hidden>> > >>>>>>> *Subject: **Re: ldm can not write to /home/ldm/logs or > >>>>>>> /TIGGE/dasg011* > >>>>>>> > >>>>>>> > >>>>>>> If he was logged in as ldm when I made the changes, he'll need > >>>>>>> to > >>>>>>> log out > >>>>>>> and back in for them to take effect. I just tested, and user > >>>>>>> ldm can > >>>>>>> write > >>>>>>> to both these locations. > >>>>>>> > >>>>>>> -Paul > >>>>>>> > >>>>>>> chifan wrote: > >>>>>>>> Paul, > >>>>>>>> > >>>>>>>> Doug is testing ldm now. He reports that ldm can not write to > >>>>>>>> /home/ldm/logs or /TIGGE/dasg011 > >>>>>>>> after you add 'ldm' to the group. Could you check again? > >>>>>>>> Thanks. > >>>>>>>> > >>>>>>>> -- Chi-Fan > >>>>>>>> address@hidden, Tel:303/497-1833, Fax:303/497-1291, > >>>>>>>> http://dss.ucar.edu > >>>>>>>> Mail: NCAR, P.O. Box 3000, Boulder, CO 80307-3000 > >>>>>>>> Overnight: NCAR, ML 288A, 1850 Table Mesa Drive, Boulder, CO > >>>>>>>> 80305 > >>>>>>>> > >>>>>>> > >>>>>>> -- > >>>>>>> Paul Goodman, 303-497-1235 > >>>>>>> address@hidden <mailto:address@hidden> > >>>>>>> NCAR/CISL > >>>>>>> > >>>>>>> > >>>>>> > >>>>> > >>>>> -- > >>>>> Paul Goodman, 303-497-1235 > >>>>> address@hidden > >>>>> NCAR/CISL > >>>> > >>> > >>> -- > >>> Paul Goodman, 303-497-1235 > >>> address@hidden > >>> NCAR/CISL > >> > > > > -- > > Paul Goodman, 303-497-1235 > > address@hidden > > NCAR/CISL Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: LJA-831211 Department: Support IDD TIGGE Priority: Normal Status: Closed