Dan.. thanks for the try :) gave it a shot on one of my relays, the
same errors are occurring after restart.. perhaps it's at the source?
Stonie mentioned something. .. here's a sampling after the edits and
restart
Aug 21 09:08:05 dish2 noaaportIngester[17968] WARN: Gap in packet
sequence: 90844815 to 90844848 [skipped 32]
Aug 21 09:08:05 dish2 noaaportIngester[17968] WARN: Gap in packet
sequence: 90844848 to 90844853 [skipped 4]
Aug 21 09:08:05 dish2 noaaportIngester[17966] WARN: Gap in packet
sequence: 169012121 to 169012162 [skipped 40]
Aug 21 09:08:06 dish2 noaaportIngester[17966] WARN: Gap in packet
sequence: 169012163 to 169012177 [skipped 13]
Aug 21 09:08:06 dish2 noaaportIngester[17966] WARN: Gap in packet
sequence: 169012177 to 169012250 [skipped 72]
Aug 21 09:08:06 dish2 noaaportIngester[17966] WARN: Gap in packet
sequence: 169012251 to 169012321 [skipped 69]
I recently had a similar problem using the GOES-R simulator.
Just a guess, but if the data is coming in via UDP and the data rate is
higher than it was before then it may be a case of too little kernel
buffer space. You can try this (assuming this is Linux):
cat /proc/sys/net/core/rmem_max
cat /proc/sys/net/core/wmem_max
cat /proc/sys/net/core/rmem_default
cat /proc/sys/net/core/wmem_default
Save these values, if this doesn't help you can reset them.
echo 16777216 >/proc/sys/net/core/rmem_max
echo 16777216 >/proc/sys/net/core/wmem_max
echo 16777216 >/proc/sys/net/core/rmem_default
echo 16777216 >/proc/sys/net/core/wmem_default
And restart LDM.
If this works you can add these values to /etc/sysctl.conf.
--
---------------------------------------------------
Patrick L. Francis
Vice President of Research & Development
Media Logic Group
http://www.medialogicgroup.com
http://www.hamweather.com
http://www.alertsbroadcaster.com
http://www.weathernationtv.com
http://www.modelweather.com
FB: http://www.facebook.com/wxprofessor
Skype: wxprofessor
AOL IM: wxprofessor
GTalk: wxprofessor@xxxxxxxxx
---------------------------------------------------
--
