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.
Gilbert, > College of DuPage is getting a new NOAAPort dish installed as I type this. > But, at least for today, they have a very noisy feed, with lots of > "Gap in SBN" messages. > > One of the things that I have always noticed is that when you have a > noisy NOAAport feed, the LDM will eventually crash. Their LDM did just > that today, and so, before they get a reliable feed, I checked their > LDM, and saw that it had choked. With their system admin's permission > (Dave Bukowski), I'd like to show this to you, in the hopes you can > prevent this from at least crashing the LDM. And with the logging that > LDM 6.11.1 has, hopefully you can see what the issue is. See below. > > Gilbert > > ******************************************************************************* > Gilbert Sebenste ******** > (My opinions only!) ****** > Staff Meteorologist, Northern Illinois University **** > E-mail: address@hidden *** > web: http://weather.admin.niu.edu ** > Twitter: http://www.twitter.com/NIU_Weather ** > Facebook: http://www.facebook.com/niu.weather * > ******************************************************************************* > > Nov 12 06:02:15 noaaport dvbs_multicast[19872] ERROR: Gap in SBN last > 3858643, this 3858671, gap 27 > Nov 12 06:02:15 noaaport dvbs_multicast[19872] ERROR: Gap in SBN last > 3858643, this 3858671, gap 27 > Nov 12 06:02:15 noaaport readnoaaport[19877] ERROR: Can "want" exceed 1 > packet? > Nov 12 06:02:15 noaaport readnoaaport[19877] ERROR: Can "want" exceed 1 > packet? > Nov 12 00:02:15 readnoaaport[19877] last message repeated 3 times > Nov 12 06:02:15 noaaport readnoaaport[19877] ERROR: large inflate error: -3 > Nov 12 00:02:15 readnoaaport[19877] last message repeated 3 times > Nov 12 06:02:15 noaaport readnoaaport[19877] ERROR: large inflate error: -3 > Nov 12 06:02:15 noaaport ldmd[19869] NOTE: child 19877 terminated by signal > 6: readnoaaport -m 224.0.1.2 > Nov 12 06:02:15 noaaport ldmd[19869] NOTE: child 19877 terminated by signal > 6: readnoaaport -m 224.0.1.2 Signal 6 is a SIGABRT on my system. What is it on yours? If it's SIGABRT, then an assertion is likely failing. Can you get a core dump and send me a stack track? Does this problem occur if you use noaaportIngester(1) rather than dvbs_multicast(1) and readnoaaport(1)? > Nov 12 06:02:15 noaaport ldmd[19869] NOTE: Killing (SIGTERM) process group > Nov 12 06:02:15 noaaport weather.cod.edu(feed)[30301] NOTE: Exiting > Nov 12 06:02:15 noaaport ldmd[19869] NOTE: Exiting > Nov 12 06:02:15 noaaport ldmd[19869] NOTE: Terminating process group > Nov 12 06:02:15 noaaport climate.cod.edu(feed)[1950] NOTE: Exiting > Nov 12 06:02:15 noaaport cdstats.cod.edu(feed)[1842] NOTE: Exiting > Nov 12 06:02:15 noaaport ldmd[19869] NOTE: Killing (SIGTERM) process group > Nov 12 06:02:15 noaaport weather.cod.edu(feed)[30301] NOTE: Exiting > Nov 12 06:02:15 noaaport ldmd[19869] NOTE: Exiting > Nov 12 06:02:15 noaaport ldmd[19869] NOTE: Terminating process group > Nov 12 06:02:15 noaaport climate.cod.edu(feed)[1950] NOTE: Exiting > Nov 12 06:02:15 noaaport cdstats.cod.edu(feed)[1842] NOTE: Exiting > Nov 12 06:02:15 noaaport climate.cod.edu(feed)[16544] NOTE: Exiting > Nov 12 06:02:15 noaaport 10.11.3.63(feed)[30302] NOTE: Exiting > Nov 12 06:02:15 noaaport climate.cod.edu(feed)[16544] NOTE: Exiting > Nov 12 06:02:15 noaaport 10.11.3.63(feed)[30302] NOTE: Exiting > > And that was the end of the log file. Regards, Steve Emmerson Ticket Details =================== Ticket ID: KMJ-130268 Department: Support NOAAPORT Priority: Normal Status: Closed