Close Notification for SaF
When SaF service loses connection with the Historian, you get an email alert like below.
2025/05/16 01:06:46.096 | Warn | Logger | | (MY-SERVER) PHD lost connection to the Store and Forward service. Will try to reconnect later.
Right now, there is no follow-up email indicating the SaF re-established connection. Can we please get an email alert when it's back?
5 replies
-
Hi ,
There is a follow-up email, but I'm not sure why it would not have been sent in your circumstance. I got a few of these messages over the weekend.2025/05/19 08:11:53.153 | Warn | Logger | | (MyMachine) SimData succeeded to reconnect to Trends.
-
What should I do next time this happens. Anything I can do or collect to help you figure out why I didn't get the close alert?
-
Do you see these corresponding messages in the message log? The bottom one is when the Logger disconnected. The top two are logged when it reestablishes the connection.
Just curious if these were not logged either or if it is specifically the email notification that was not sent.
-
No. Looks like maybe the service crashed?
-
No, it looks like the Logger was stopped manually based upon those messages, but that's probably why you did not receive the confirmation that it reconnected. I imagine the SaF service was stopped first which would've triggered the notification, then the Logger service was stopped next. Once the Logger service is stopped, I think it loses its state of connectivity to the SaF service. Had the SaF service been stopped and started while the Logger is still running, you would've received both messages. If there was a server shutdown, perhaps it was a race condition as to which service stopped first. Ideally, if you're manually stopping both, the Logger should be stopped first, followed by the SaF. Then reverse order for starting up. You would at least avoid some error messages of the Logger trying to connect to the SaF service.
-
Print this page