...
| Info |
|---|
Providing Delft-FEWS support with relevant log files, screenshots or even a copy of a config / local datastore may help us solving the issue more efficiently. |
Tip1: Logging from the Operator Client is stored in the log.txt of your REGION_HOME directory. On the Forecasting Shell this file is called out.txt. For some problem, these log files contain relevant information.
Tip2: If you send us a snippet of the log.txt, please remember to include always the build number section. This line looks typically like
...
. |
...
Tip3: Log files in the Master-controller / Forecasting Shells will only remain the last ten days / for a certain disk limit. In case of a problem, download the logs files via the Admin Interface the relevant logging is removed.
Below you will find some useful tips to analyse your system and provide useful information to the fews support helpdesk.
...
- Check the status of the system through Admin Interface system status page, is everything green?
- Check the View logs page in the Admin Interface for ERRORs
- Log files in the Master-controller / Forecasting Shells will by default only remain the last ten days / for a certain disk limit.
- Use Collect System log files from the Admin Interface to collect the log files from all FEWS backend components and send them to fews support
...
- Check the log.txt file from your Operator Client to find out whether it contains the Text ERROR. This file is located at the same level where the localDatastore folder is created. Please send this log.txt to fews support
- If you send us a snippet of the log.txt, please remember to include always the build number section.
- If it is an issue with your operator client please copy the localDatastore folder (and store it somewhere else) for hand over to fews support if needed
If there is a problem with missing data in the Operator Client / Forecasting Shell