0

SaF Reconnected Email

Every now and then we get this email alert. I'm told it is because the Sender at the source lost contact with the Historian SaF. The data is still buffered locally and does come in eventually. But there is no email saying it has reconnected. So I have to log in and confirm (which is a chore for some companies: VPN, citrix, jump servers, etc.). It would be nice to get an email saying it reconnected so I didn't have to worry.

 

2025/08/15 01:18:22.063 | Warn | Logger |  | (Server1) SourceA lost connection to the Store and Forward service. Will try to reconnect later.

4 replies

null
    • wise_james
    • 2 days ago
    • Reported - view

     We are getting this on one server as well and are looking into it. I think we DO get two emails but the reconnect says "Trends" while the disconnect says "Store and Forward". Not sure if it's the same for you or if this help but I wanted to mention it. 

    =======

    From: <REMOVED>
    Sent: Saturday, August 16, 2025 9:14 AM
    To: <REMOVED>
    Subject: Canary Logger Message

    2025/08/16 09:14:17.722 | Warn | Logger |  | <REMOVED> succeeded to reconnect to Trends.


    From: <REMOVED>
    Sent: Saturday, August 16, 2025 9:14 AM
    To: <REMOVED>
    Subject: Canary Logger Message

    2025/08/16 09:14:09.928 | Warn | Logger |  | <REMOVED> lost connection to the Store and Forward service. Will try to reconnect later.

    • damon_vinciguerra.1
    • 2 days ago
    • Reported - view

    Alas, nope, have never gotten a Trend email. 
     

    And I should not for Support that our alert is related to an OPC DA Logger instance local to the Historian server. It seems odd it would lose contact locally. 

      • wise_james
      • 2 days ago
      • Reported - view

       Which version are you running?

      I should also note that the following about my example:

      1. It is also OPC DA
      2. The OPC server and Canary collector are both together on the same VM
      3. The historian VM is a different VM BUT it is on the same physical server as the above and I'm also questioning whether or not we really lost network connection for example. There are other assets on the same OPC server/Canary Collector. While it isn't always the same one that generates the email, it's certainly not like all of them have this issue at the same time like one might expect with a network issue for example. 

      We are definitely still following up on this. There are some indications that we are getting this when a tag changes value. Maybe not every time it changes value but at least what seems like maybe a good portion of the time. The main one I looked at is a "trigger" tag that doesn't have a high rate of change compared to something like a temperature tag or something. 

    • damon_vinciguerra.1
    • 2 days ago
    • Reported - view

    Intriguing! Maybe I need to reopen my support case. 😁 This one is on 25.3. 

Content aside

print this pagePrint this page
  • 2 days agoLast active
  • 4Replies
  • 11Views
  • 2 Following