Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
I've attached a slightly cleaned up example of my logs for this occurrence. Namely, there is a 'NOTE: Exiting' entry for EACH of my DOWNSTREAMHOST entries...but only some of them have the longer line with the "Couldn't flush connection..." It is slightly concerning that readnoaaport can kill rpc.ldmd ... anyone have insights to this? -- Eric M. Hudish ZedX, Incorporated 369 Rolling Ridge Road Bellefonte, PA 16823 Phone: +1.814.357.8490 +225 Cell: +1.724.977.3314 PGP Security Available Search http://keyserver.pgp.com
Oct 07 19:41:48 MYHOST rpc.ldmd[11998] NOTE: child 12009 terminated by signal 11: readnoaaport -m 224.0.1.3 Oct 07 19:41:48 MYHOST rpc.ldmd[11998] NOTE: Killing (SIGTERM) process group Oct 07 19:41:48 MYHOST rtstats[12000] NOTE: Exiting Oct 07 19:41:48 MYHOST DOWNSTREAMHOST(feed)[12018] NOTE: Exiting Oct 07 19:41:48 MYHOST DOWNSTREAMHOST(feed)[18956] ERROR: Couldn't flush connection; nullproc_6() failure to tornado.zedxinc.com: RPC: Unable to receive; errno = Bad file descriptor Oct 07 19:41:48 MYHOST rpc.ldmd[11998] NOTE: Exiting Oct 07 19:41:48 MYHOST pqact[11999] NOTE: Exiting Oct 07 19:41:48 MYHOST rpc.ldmd[11998] NOTE: Terminating process group Oct 07 19:41:48 MYHOST pqact[11999] NOTE: Behind by 0.310809 s
ldm-users archives: