IV. GLM Troubleshooting

The terrestrial GLM ingest utilizes a direct connection between the LDAD LDM and the CPSBN LDM to minimize latency in the delivered product. This direct connection is new to most sites. The following are some steps to take if data does not store and ingest as expected.

  • If GLM data was previously storing correctly and then stopped, and an AWIPS install has been performed, check the CPSBN ldmd.conf for the necessary REQUEST entry. An AWIPS install may overwrite the ldmd.conf file on the CPSBN machines.
  • Check to see if the files are being received at LDAD.

As user ldm on ls1, run the following command

notifyme -vxl - -h localhost -f EXP -p IXTR99  (for CONUS/PACUS GLM, phasing out in late 2020/early 2021)
​​​​​​​notifyme -vxl - -h localhost -f EXP -p OR_GLM  (for Full Disk GLM)

Files should start appearing within a couple of minutes. If they do not, then check the REQUEST entry in the LDAD ldmd.conf file (see the site prep guide starting at step A.20 for full disk GLM). You may also want to confirm with your regional headquarters that the files are up to date on their LDM.

  • Check to see if files are being received at the CPSBN

As user ldm on the active cp1f, run the following command

notifyme -vxl - -h cp1f -f EXP -p IXTR99 (for CONUS/PACUS GLM, phasing out in late 2020/early 2021)
​​​​​​​notifyme -vxl - -h cp1f -f EXP -p OR_GLM (for Full Disk GLM)

(you can use cpsbn1 instead of cp1f in the above command). Files should start appearing within a couple of minutes. If they do not, then check the REQUEST entry in the cp1f ldmd.conf file (see the site prep guide). Also check the ALLOW entry in the LDAD ldmd.conf.

  • If files ARE appearing on cp1f, but data is not available in CAVE, verify that the proper TOWR-S RPM has been installed and EDEX has been restarted.
  • If data are arriving to /data_store/goes-r, but not displaying in CAVE, check the (dx3 or dx4 /awips2/edex/logs) unrecognized files log to see if there may be a distribution problem
  • If files with the name IXTR99 (CONUS/PACUS), or OR_GLM (Full disk) are showing up in the (dx3 or dx4 /awips2/edex/logs) satellite ingest files, but say "No Valid Records were found," then make sure you bounced edex after the last RPM install. 
  • If data are arriving to /data_store/goes-r, but not displaying in CAVE , look in common_static/site/<site_name>/satellite/goesr/descriptions/Level2 for the file GLMG_FD_tile.xml (for full disk GLM).  If that file exists, make sure you bounced edex.  If it doesn't exist, you do not have the right TOWR-S RPM installed.

 

For any GLM-specific questions or information, you can join the NWS Chat group called glm-support.

Point of Contacts: Lee Byerle, and John Evans.