Logs and Generic Troubleshooting

Logs

Logs files are located in three different locations. EDEX logs are located in the /awips2/edex/logs directory on the EDEX cluster (dv3, dv4, and dv5). The EDEX logs on dv3, dv4, and dv5 are different from each other. These logs include information on GFE processes executed through EDEX. All log entries related to the creation of grids by smart inits are included in the EDEX smartInit log file (edex-ingest-smartInit-YYYYMMDD.log, where YYYYMMDD is the date). The log file associated with the EDEX request process includes entries for several important processes in GFE, including: ISC grid processing, IRT registration, GFE Perspective requests for data, GFE Site Activation, file updates, D2DParmIDCache, and transmission of grids to the central server/NDFD. The log file associated with the EDEX ingest process includes entries for several important processes in GFE, including: GFE Site Activation, file updates, and data purging. GFESuite logs are located in the /awips2/GFESuite/logs/XXX/YYYYMMDD/machinename directory, where XXX is your site id and YYYYMMDD is the date, on the EDEX cluster (dv3, dv4, and dv5). The GFESuite logs on dv3, dv4, and dv5 are identical to each other. The logs include information of GFE specific components such as Service Backup, ISC, and GFE utilities. Console logs are located in each user's caveData directory (/home/username/caveData/logs/consoleLogs/machinename). These logs include information on each CAVE, AlertViz, and gfeclient session started by the user.

Generic Troubleshooting

Looking through the various log files is a way to find and diagnose problems/errors. Once an issue has been identified and isolated begin diagnosing the situation. Start with the most probable and common issue and progress to the least probable and uncommon issue. You may need to troubleshoot user errors, machine errors, server problems/errors, or program errors. Check the syntax when making changes to any GFE config or GFE server config file in the Localization Perspective. Restarting GFE and/or restarting the GFE server process using the GFE Site Activation GUI or by manually running the scripts via the command line in a terminal to deactivate and then activate the site can solve problems/errors. A way to troubleshoot GFE errors is to start GFE via the command line with the noredirect switch in terminal which is discussed more in the Command Line Scripts section. This will output any errors GFE encounters to the terminal. Ask forecasters to save off AlertViz messages and send to you for evaluation and troubleshooting.