EcoStruxure Geo SCADA Expert Forum
Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-08-07 11:24 PM . Last Modified: 2023-05-02 11:53 PM
Hello Everyone,
We've client with hot-stand by GEO SCADA partner where the stand by server found shut down suddenly.
What could causes such behavior?
Thanks in advance
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-08-08 05:21 AM
Many reasons - disk space being one.
Check your server log files. Contact support line for help.
Steve
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-08-15 12:06 AM
Thanks @sbeadle but the disk space is not an issue.
We checked the log files, watchdog exception was found...
*** Exception Database watchdog timed out. at 00007FF85D989319 occurred **
How can we detect the cause/solve it?
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-08-15 03:15 AM
That message indicates that the database watchdog has detected that the server has stalled and so has shut it down.
To investigate what caused the server to stall you need to examine the DB logs in the minutes prior to the watchdog being triggered (default 4 minutes), or contact customer support and supply the DB log files and the dump file created by the watchdog.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-08-15 03:53 AM
what are the prospects could cause that?
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-08-15 03:58 AM
There are many possible reasons, for example oversized historic granules in the historian or poorly designed/optimised SQL queries.
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.