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.
>From: "Mark J. Laufersweiler" <address@hidden> >Organization: OU >Keywords: 200303160058.h2G0w4B2018182 LDM-6 IDD Mark and Chuck, >Since I have nothing better to do today but baby sit my ldm machine >:-) Ah, a pleasant thing to do on a Saturday afternoon... NOT >I found this in the log file and am not sure how it may help, >but it seems to relate to the problems we had Friday trying to get >stats out from SLU and Chuck's ldm: > >Mar 15 23:45:08 stokes inflow(feed)[2198]: up6.c:299: Starting >Up(6.0.2): 20030315233331.023 TS_ENDT {{NNEXRAD, >"/p...(LSX|EAX|SGF)"}} >Mar 15 23:45:08 stokes inflow(feed)[2198]: topo: inflow.eas.slu.edu >NNEXRAD >Mar 15 23:53:49 stokes inflow(feed)[2198]: up6.c:168: HEREIS: RPC: >Unable to send; errno = Broken pipe >Mar 15 23:53:49 stokes inflow(feed)[2198]: up6.c:369: Product send >failure: Input/output error >Mar 15 23:53:55 stokes rpc.ldmd[1968]: child 2198 exited with status >6 >where rpc.ldmd[1968] is the parent for ldm. I believe that this is telling us that your LDM's trasfer of NNEXRAD data to Chuck's exited after getting a "write" (send) error. I agree that this is most likely related to something on Chuck's end. When he contacts his network administrator, about port 388 access things may get better. Tom