The Unidata Local Data Manager (LDM) system includes network client and server programs designed for event-driven data distribution, and is the fundamental component of the Unidata Internet Data Distribution (IDD) system.
I am using LDM 6.13.13 on RHEL8 64 bit. My usage scenario is to have clients out on the internet push data to my LDM server every minute with data from weather equipment. The clients use ldmsend to do this.
On the server side, for each ldmsend the following gets logged
20201119T152648.134997Z xxx[444490] svc_tcp.c:readtcp:363 NOTE EOF on socket 2
20201119T152648.135077Z xxx[444490] one_svc_run.c:one_svc_run:96 NOTE RPC layer closed connection on socket 2
20201119T152648.135102Z xxx[444490] ldmd.c:runSvc:556 NOTE Connection with client LDM, xxx.xxx.xxxx.xxx, has been lost
20201119T152648.135147Z xxx[444490] ldmd.c:cleanup:197 NOTE Exiting
This ends up creating lots of logging. It would be nice if there wasn't so much logging with these sessions, but I am unsure exactly what to suggest. Initially, it seems conflicting to see both EOF on socket 2 and RPC layer closed connection on socket 2. It seems like those messages could be combined? The message about the client connection being 'lost' doesn't seem accurate as the client cleanly closed the connection via RPC, right?
I am using LDM 6.13.13 on RHEL8 64 bit. My usage scenario is to have clients out on the internet push data to my LDM server every minute with data from weather equipment. The clients use
ldmsendto do this.On the server side, for each
ldmsendthe following gets loggedThis ends up creating lots of logging. It would be nice if there wasn't so much logging with these sessions, but I am unsure exactly what to suggest. Initially, it seems conflicting to see both
EOF on socket 2andRPC layer closed connection on socket 2. It seems like those messages could be combined? The message about the client connection being 'lost' doesn't seem accurate as the client cleanly closed the connection via RPC, right?Thanks for your consideration.