Kevin may have hit this problem right on the head. We're only running 2
gb of RAM in the ingest machine running noaaport. And this was returned
after running 'dmesg':
Out of memory: Kill process 16773 (noaaportIngeste) score 262 or
sacrifice child
Killed process 16773, UID 501, (noaaportIngeste) total-vm:1851364kB,
anon-rss:20656kB, file-rss:1757796kB
Interesting that noaaport in ldm 6.12.6 ran just fine in the current
hardware configuration.
Bruce
On 3/19/2015 11:43 AM, Kevin W. Thomas wrote:
Jobs killed by SIGKILL (signal 9) are being killed by the kernel, or maybe
an OOM (Out Of Memory) daemon.
Something on your system, not necessarily LDM, is using up all the available
memory on your computer. The only choices are to start killing processes or
for the kernel to crash.
Monitor "top" and see if there is something else running away. You might also
try running "dmesg" to see if the kernel has logged other problems. You can
also start LDM in verbose mode to see if it will provide you with any more
useful information.
Kevin W. Thomas
Center for Analysis and Prediction of Storms
University of Oklahoma
Norman, Oklahoma
Email: kwthomas@xxxxxx
Howdy! We seem to be having a problem with noaaport in the latest
release of ldm 6.12.9. More specifically... when ldm is started, the
system load goes sky high until noaaport eventually crashes. I have
included a snippet of the ldmd.log file. Any clues? Thanks! Bruce
Mar 19 16:15:33 vologda ldmd[14201] NOTE: Starting Up (version: 6.12.9;
built: Mar 18 2015 16:33:34)
Mar 19 16:15:33 vologda ldmd[14201] NOTE: Starting Up (version: 6.12.9;
built: Mar 18 2015 16:33:34)
Mar 19 16:15:33 vologda ldmd[14201] NOTE: Using local address 0.0.0.0:388
Mar 19 16:15:33 vologda ldmd[14201] NOTE: Using local address 0.0.0.0:388
Mar 19 16:17:06 vologda ldmd[14201] NOTE: child 14203 terminated by
signal 9: noaaportIngester -m 224.0.1.1
Mar 19 16:17:06 vologda ldmd[14201] NOTE: child 14203 terminated by
signal 9: noaaportIngester -m 224.0.1.1
Mar 19 16:17:06 vologda ldmd[14201] NOTE: child 14206 terminated by
signal 9: noaaportIngester -m 224.0.1.4
Mar 19 16:17:06 vologda ldmd[14201] NOTE: child 14204 terminated by
signal 9: noaaportIngester -m 224.0.1.2
Mar 19 16:17:06 vologda ldmd[14201] NOTE: child 14210 terminated by
signal 9: noaaportIngester -m 224.0.1.8
Mar 19 16:17:06 vologda ldmd[14201] NOTE: child 14206 terminated by
signal 9: noaaportIngester -m 224.0.1.4
Mar 19 16:17:06 vologda ldmd[14201] NOTE: child 14204 terminated by
signal 9: noaaportIngester -m 224.0.1.2
Mar 19 16:17:06 vologda ldmd[14201] NOTE: child 14210 terminated by
signal 9: noaaportIngester -m 224.0.1.8
Mar 19 16:17:33 vologda ldmd[14201] NOTE: child 14205 terminated by
signal 9: noaaportIngester -m 224.0.1.3
Mar 19 16:17:33 vologda ldmd[14201] NOTE: child 14205 terminated by
signal 9: noaaportIngester -m 224.0.1.3
Mar 19 16:18:25 vologda ldmd[14201] NOTE: child 14207 terminated by
signal 9: noaaportIngester -m 224.0.1.5
Mar 19 16:18:25 vologda ldmd[14201] NOTE: child 14207 terminated by
signal 9: noaaportIngester -m 224.0.1.5
Mar 19 16:18:26 vologda ldmd[14201] NOTE: child 14208 terminated by
signal 9: noaaportIngester -m 224.0.1.6
Mar 19 16:18:26 vologda ldmd[14201] NOTE: child 14208 terminated by
signal 9: noaaportIngester -m 224.0.1.6
Mar 19 16:19:24 vologda ldmd[14201] NOTE: child 14209 terminated by
signal 9: noaaportIngester -m 224.0.1.7
Mar 19 16:19:24 vologda ldmd[14201] NOTE: child 14209 terminated by
signal 9: noaaportIngester -m 224.0.1.7
_______________________________________________
ldm-users mailing list
ldm-users@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
