Skip Navigation Links 
NOAA logo-Select to go to the NOAA homepage National Weather Service      Select to go to the NWS homepage
Meteorological Development Laboratory banner

Right Arrow User Guides

Right Arrow Docs/Pubs

Right Arrow Training

Right Arrow Other Links

Contact us

Troubleshooting Tips

If your problem is not mentioned in the Troubleshooting Tips below, please try our Field Reports page, which contains communications between the developers and the field.

Version # and
Symptom Potential Solution


SAFESEAS table flickers causing slow workstation response.

Using the App Launcher's SAFESEAS Monitoring Area Configuration GUI, add enough zones/counties so you have a minimum of 12.


SAFESEAS displays an error box that reads, "The SAFESEAS display (or monitoring) threshold file is for < previous build > but not for < current build >."

Relocalize on any machine with the "-safeseas" option; run stopSSprocessor and startSSprocessor on px1, as "fxa".

OB6.0 to 6.1

Monitor Area setup GUI hangs, spawns runaway "fileChangeNotifyWish" process (due to a potentially corrupt APRSWXNET mesonet file, if the WFO is receiving that data). .

Go to /data/fxa/workFiles/safeseas/, and type in the commands:
tr -d '\015' < MA_setup.dat > temp1
mv temp1 MA_setup.dat
tr -d '\015' < Reg_setup.dat > temp1
mv temp1 Reg_setup.dat


SAFESEAS not updating in display or table for hours or days.

Load the Monitor Area Config GUI from the Apps Launcher. Double-click on your monitored counties/zones (in the Monitor Area Zones) box to see if any observing platforms are listed in the Associated Stations box. If you don't see stations in any of your counties then you can add them back in manually with that GUI. Another recovery option is to quickly re-create default localization settings by:
1. Going to /data/fxa/workFiles/safeseas/, and remove all *dat *old *txt *orig files.
2. Running /awips/fxa/data/localization/scripts/mainScript.csh -safeseas.
3. On px1, as fxa, restart the SAFESEAS processor (stopSSprocessor/startSSprocessor).


SAFESEAS table won't pop up after new build installation and localization.

1. (Optional, if users have customized SAFESEAS). Save any user customization files:
tar -cvf /data/fxa/workFiles/safeseasFiles.tar ./safeseas
2. Get rid of the corrupted localization files:
cd /data/fxa/workFiles/safeseas/
rm *.dat *.txt *old display_thresholds/*
3. Then, on any Linux machine, re-localize for SAFESEAS:
/awips/fxa/data/localization/scripts/mainScript.csh -safeseas
4. On px1, as fxa, restart SSprocessor:
5. This will get SAFESEAS back up and running with default settings. Contact MDL if you need help restoring personal or office customizations.

OB6 +

After loading SAFESEAS,
D-2D has obs, but the SAFESEAS table does not
(it just has gray "NA" values).

First, click on the "Vis" or "Wind Speed" boxes in the SAFESEAS table to make sure any obs aren't hiding from view due to sorting problems.  If there are still no obs, then compare the table's valid time to the D-2D display's valid time.  If the SAFESEAS table has jumped to the next
hour, use "Link to Frame" to fix it on the D-2D's time until the D-2D display has a chance to catch up.


SCAN | FFMP | SAFESEAS | Fog Monitor | GUARDIAN | FSI | Rip Current | SNOW
Autonowcaster | VLab

    US Dept of Commerce
    National Oceanic and Atmospheric Administration
    National Weather Service
    Meteorological Development Laboratory
    1325 East West Highway
    Silver Spring, MD 20910
    Page Author:
    Page last Modified: September 29, 2008.
Information Quality
Privacy Policy
Freedom of Information Act (FOIA)
About Us
Career Opportunities