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.
Unidata Support wrote: > > ------- Forwarded Message > > >To: Unidata Support <address@hidden> > >From: "Patrick O'Reilly" <address@hidden> > >Subject: LDM not starting at boot > >Organization: UCAR/Unidata > >Keywords: 200110101540.f9AFep112053 > > This is a multi-part message in MIME format. > > ------=_NextPart_000_0027_01C15178.1154F3B0 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > Hi all, > > During my installation of LDM, I followed directions on starting the LDM = > at boot. What I did specifically: > > Put the supplied script in /etc/init.d as ldm.start > Made a link in /etc/rc3.d to ldm.start called S95ldmd > > I also tried putting the script right in /etc/rc3.d as S95ldmd. After = > making sure it was executable, I have rebooted several times, (trying to = > fix the problem that the ldm cron jobs are failing) all to no avail. =20 > > Also, like I mentioned, my ldm cron jobs now are failing. It began over = > a week ago, so the scour, statistics, etc. are not being done. I am = > having to run the scour script manually. It seems the root cron stuff = > is all still being done, just ldm's have begun to fail. Any help would = > be great. > > Patrick > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Patrick O'Reilly Support Scientist > The STORM Project address@hidden > 208 Latham Hall ph: 319-273-3789 > University of Northern Iowa > Cedar Falls, IA 50614 =20 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ =20 > Hi Patrick, First, I understand from Tom that the cron problem is solved. Is that behaving for you now? Regarding starting the ldm at system boot, I have logged on to your machine and I can't see any problems. I recommend that you run the boot script from the command line and see if it reports any errors. That is, as 'root' in /etc/rc3.d, do './S95ldm stop' to stop the ldm, then do './S95ldm start' to start it. In initial testing you could comment out the lines that delete and remake the queue to save the associated overhead of rebuilding it and retrieving the past hour's worth of data. If that works ok, the I'd try it with rebuilding the queue just to eliminate all variables. If the script works from the command line but still doesn't work at boot time, then I would suspect something in the ldm environment. I would then move the ldm .cshrc and .login file to the side and try rebooting again. Please try these things and let me know what happens. Anne -- *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://www.unidata.ucar.edu/ ****************************************************