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.
Hello Patrick, The issue here, I believe, is an environment issue. ldmfail is a perl script, that will get executed via a borne shell. I suspect you are running in a c-shell (by the sea-shore). The borne shell will not grab the attributes(paths) that are in your c-shell. Soooo, we can either place the path for the decoders in the cron (set path, blah/blah/blah run ldmfail or you can "hack" your ldmfail program to include the paths to your decoders. Check the "Dependencies" i.e. > from motherlode ############################################################################## # END OF CONFIGURATION SECTION ############################################################################### # identify ourselves and set up some extra stuff we will need $PROGNAME = "ldmfail" ; $lock_file = "/tmp/.ldmadmin.lck"; $primary = "missing" ; $failover = "missing" ; # Dependencies: $ENV{ 'PATH' } = ".:/usr/ccs/bin:/opt/SUNWspro/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/gnu/bin:/usr/openwin/bin:/opt/ldm/bi n:/opt/ldm/util:/opt/ldm/decoders" ; and if your install is the same as motherlode this should work. If your ldm dir tree is different, then the appropriate changes would need to be made. on lenny: ############################################################################### # END OF CONFIGURATION SECTION ############################################################################### # identify ourselves and set up some extra stuff we will need $PROGNAME = "ldmfail" ; $lock_file = "/tmp/.ldmadmin.lck"; $primary = "missing" ; $failover = "missing" ; # Dependencies: $ENV{ 'PATH' } = ".:/bin:/usr/bin:/opt/SUNWspro/bin:/usr/ccs/bin:/usr/local/ldm/bin:/usr/local/ldm/decoders:/usr/loc al/bin:/usr/etc:/usr/ucb:/usr/local/gnu/bin" ; notice on lenny:/usr/local/ldm/decoders and on motherlode:/opt/ldm/decoders We are working on a more graceful ldmfail program, but that will be months. Hope this sheds some light on the subject. FYI...did not get your attachement. Thank you, -Jeff ____________________________ _____________________ Jeff Weber address@hidden Unidata Support PH:303-497-8676 NWS-COMET Case Study Library FX:303-497-8690 University Corp for Atmospheric Research 3300 Mitchell Ln http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 ________________________________________ ______________________ On Tue, 4 Dec 2001, Unidata Support wrote: > > ------- Forwarded Message > > >To: Unidata Support <address@hidden> > >From: "Patrick O'Reilly" <address@hidden> > >Subject: LDM Failover Issues > >Organization: UCAR/Unidata > >Keywords: 200112041640.fB4GeeN16636 > > Hi there again! > > I have found that when the LDM fails over, whether it is to the failover > host or back to the primary host, my hard drive fills up with errors, as > data is no longer being decoded due to broken pipes, write errors, etc. > I have attached a clip from a 13MB ldmd.log file to illustrate these > messages. I have found a support email that mentions this problem > without telling how to fix it > (http://www.unidata.ucar.edu/glimpse/ldm/3301). The fix actually > mentioned in the support email, I guess, is to comment out ldmfail in > cron, if the primary host is reliable. Have there been other reports of > this with ldmfail and are there fixes? Thanks! > > 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 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > ------- End of Forwarded Message > >