Spam rule downloads generate curl 56 error

Products

• Messaging Gateway
• Messaging Gateway for Service Providers

Issue/Introduction

Spam rule sets are updating but the conduit process is generating large numbers of errors in the logs following the migration of Messaging Gateway and Messaging Gateway for Service Provider network data center (ALERT2628).

This and associated issues are being tracked in ALERT2629

---

Status

• As of 17:00 UTC, December 6, 2018:

  All issues have been resolved.

---

• As of 17:30 UTC, December 5, 2018 here is the latest update:

  Remediation has been put in place and the service is fully restored. We are continuing to monitor the service closely to ensure there is no further customer impact.

  The next update will be provided on December 6, 2018 at 18:30 UTC or as soon as new information becomes available

• As of 02:30 UTC, Dec 5, 2018 here is the latest update:
  
  Network and content interrupt (Curl 56 error) – Remediation has been put in place and the service is fully restored. We are monitoring closely to ensure there is no further customer impact.
  
  We will provide an update when more information becomes available.
• As of 00:30 UTC, Dec 5, 2018 here is the latest update:
  
  Network and content interrupt (Curl 56 error) – The fix is currently in a testing phase.  The error message does not represent a failure to download rules and does not have any impact to the efficacy of the service.
  
  We are focused on fully restoring service as soon as possible. The next update will be provided at 02:30 UTC on Dec 5, 2018, or as soon as new information becomes available.
• As of 22:30 UTC, here is the latest update:
  
  Network and content interrupt (Curl 56 error) – We continue to work on the fix, in testing state. The error message does not represent a failure to download rules and does not have any impact to the efficacy of the service.
  
  We are focused on fully restoring service as soon as possible. The next update will be provided at 00:30 UTC on Dec 5, 2018, or as soon as new information becomes available.

• As of 20:30 UTC, here is the latest update:
  
  Network and content interrupt (Curl 56 error) – We continue to work on the fix. The error message does not represent a failure to download rules and does not have any impact to the efficacy of the service.

• As of 18:30 UTC, here is the latest update:

  Network and content interrupt (Curl 56 error) – Engineering efforts are underway to isolate the issue. The error message does not represent a failure to download rules and does not have any impact to the efficacy of the service.

• Update Dec 4, 2018 16:30 UTC:
  We continue to investigate this issue and ensure all issues have been remediated. As of 16:30 UTC, here is the latest update:
  
  Network and content interrupt (Curl 56 error) – We have added additional computing resources and continue to investigate the underlying issue. The error does not represent a failure to download rules and does not have any impact to the efficacy of the service.
  
  We are focused on fully restoring service as soon as possible. The next update will be provided at 18:30 UTC on Dec 4, 2018, or as soon as new information becomes available.
   
• Update Dec 4, 2018 08:30 UTC:

We continue to investigate this issue and ensure all issues have been remediated. As of 00:30 UTC, here is the latest update:

We increased the capacity of our infrastructure to ensure that it is sufficient to handle all traffic. We are still seeing some errors in the internal workings of our software; however, it is only minor and does not represent real failure to download rules or impacts effectiveness of the service.

We are focused on fully restoring service as soon as possible. The next update will be provided at 16:00 UTC on Dec 4, 2018, or as soon as new information becomes available.

• Update Dec 4, 2018 00:30 UTC:

  We continue to investigate this issue and ensure all issues have been remediated. As of 00:30 UTC, here is the latest update:

  Network and content interrupt (Curl 56 error) – We continue to debug network logging to determine the cause of these errors. The additional processing added during this incident has reduced the timeout errors some customers were receiving.

  We are focused on fully restoring service as soon as possible. The next update will be provided at 08:30 UTC on Dec 4, 2018, or as soon as new information becomes available.

• Update Dec 3, 2018 22:30 UTC:
  We continue to work towards resolving this problem. As of 22:30 UTC, here is the latest update:
  
  Curl 56 Error – The additional processing added has reduced some timeout errors. We continuing to investigate the issue.
  
  We are focused on restoring service as soon as possible. The next update will be provided at 00:30 UTC on Dec 4, 2018, or as soon as new information becomes available
   
• Update Dec 3, 2018 20:30 UTC:
  We have various groups working together to address this problem.  As of 20:30 UTC, here is the latest update:
  
  Curl 56 error – We are actively working on narrowing down the issue. In parallel, additional processing has been added to reduce timeout errors.
  
  We are focused on restoring service as soon as possible. The next update will be provided at 22:30 UTC or as soon as new information becomes available.

conduit_log

2018-12-02T10:18:12Z (ERROR:8093.3402172192): [12034] Network error occurred, SSL read: error:00000000:lib(0):func(0):reason(0), errno 0 (56), check your network connection settings, check your proxy settings (if applicable), and check to ensure that port 443 (HTTPS) is open through any relevant firewalls.
2018-12-02T10:18:18Z (ERROR:8093.3402172192): [12034] Network error occurred, SSL read: error:00000000:lib(0):func(0):reason(0), errno 0 (56), check your network connection settings, check your proxy settings (if applicable), and check to ensure that port 443 (HTTPS) is open through any relevant firewalls.
2018-12-02T10:18:18Z (ERROR:8093.3402172192): [12034] Network error occurred, SSL read: error:00000000:lib(0):func(0):reason(0), errno 0 (56), check your network connection settings, check your proxy settings (if applicable), and check to ensure that port 443 (HTTPS) is open through any relevant firewalls.
 

Resolution

Antispam rule updates are unaffected by this error which is only generated only when there is no new rule file to download.

Symantec network enginering is investigating the root cause of the error messages