[LDM #GNE-820898]: LDM log output from 6.10.1

Carissa,

> We have just installed LDM-6.10.1 on Red Hat Enterprise Linux Server
> release 5.7 and are curious about the difference in logging behavior
> between 6.10.1 and 6.7.0 (our previous version). Specifically we are
> curious about the line "INFO: Deleting closed PIPE entry."  The output I
> have below is from our level 3 radar feed, but we are seeing this across
> all of the LDM's running this version. Each different LDM is running and
> filing data appropriately and we are not seeing any errors. I have
> included the log output from both LDM's.
> 
> ldm-6.10.1>ldmadmin tail
> Apr 10 17:18:36 vm-lnx-ncosrv5 radar3src.nws.noaa.gov[16627] INFO:
> 2309875 20120410171836.245 NEXRAD3 000  wsr88d17183.tbz2
> Apr 10 17:18:36 vm-lnx-ncosrv5 pqact[16626] INFO:  2309875
> 20120410171836.245 NEXRAD3 000  wsr88d17183.tbz2
> Apr 10 17:18:36 vm-lnx-ncosrv5 pqact[16626] INFO:                pipe:
> -close   /usr1/ldm/bin/process_hires_radarlvl3.sh
> /ops/ldm/hires_radar_level3/unprocessed_products wsr88d17183.tbz2
> Apr 10 17:18:36 vm-lnx-ncosrv5 pqact[16626] INFO: Deleting closed PIPE
> entry: pid=23999, cmd="-close /usr1/ldm/bin/process_hires_radarlvl3.sh
> /ops/ldm/hires_radar_level3/unprocessed_products wsr88d17183.tbz2"
> [filel.c:290]
> 
> ldm-6.7.0>ldmadmin tail
> Apr 10 17:20:19 vp-ncosrv5 radar3src.nws.noaa.gov[6597] INFO:  1665880
> 20120410172019.425 NEXRAD3 000  wsr88d17201.tbz2
> Apr 10 17:20:19 vp-ncosrv5 pqact[6596] INFO:  1665880 20120410172019.425
> NEXRAD3 000  wsr88d17201.tbz2
> Apr 10 17:20:19 vp-ncosrv5 pqact[6596] INFO:                pipe:
> -close        /usr1/ldm/bin/process_hires_radarlvl3.sh
> /ops/ldm/hires_radar_level3/unprocessed_products wsr88d17201.tbz2
> 
> 
> Is this "Deleting closed PIP entry" expected behavior or could there be
> an issue that we need to uncover?a

It's expected behavior. I added the INFO-level message somewhere between the 
two versions you have. It merely indicates that the pqact(1) process removed an 
entry in its internal table because the pipe to the indicated process was 
closed (likely due to the use of the "-close" option). I suppose one could 
argue for demoting it a DEBUG-level message. What do you think?

> Let me know if there is any further
> information I can provide to be helpful with our vague question.
> 
> Thanks,
> 
> --
> Carissa Klemmer
> NCEP Central Operations
> Production Management Branch Dataflow Team
> 301-763-8000 ext 7154

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: GNE-820898
Department: Support LDM
Priority: Normal
Status: Closed