Skip to main content
NetApp Knowledge Base

Proxy server: AltaVault is sending the backup data directly to the cloud instead of through the proxy

  1. Last updated
  2. Save as PDF
Views:
247
Visibility:
Public
Votes:
0
Category:
altavault
Specialty:
legacy
Last Updated:

Applies to

  • AltaVault (AVA)
  • proxy server

Issue

  • AltaVault Alarm - Inconsistent cloud connectivity
  • [curl.INFO] (8438) (15:21:03.405884): HTTP/1.1 503 Service Unavailable followed by [curl.INFO] (13031) (01:19:23.866147): Proxy CONNECT aborted
  • Here is an example of a connectivity issue found in the messages logs of a system dump (sysdump)
    • Jun  5 15:21:03 localhost rfsd[8239]: [curl.INFO] (8438) (15:21:03.333976): Establish HTTP proxy tunnel to cloud.provider:443
    • Jun  5 15:21:03 localhost rfsd[8239]: [curl.INFO] (8438) (15:21:03.333998): CONNECT cloud.provider:443 HTTP/1.1
    • Jun  5 15:21:03 localhost rfsd[8239]: [curl.INFO] (8438) (15:21:03.333998): Host: cloud.provider:443
    • Jun  5 15:21:03 localhost rfsd[8239]: [curl.INFO] (8438) (15:21:03.333998): Proxy-Connection: Keep-Alive
    • Jun  5 15:21:03 localhost rfsd[8239]: [curl.INFO] (8438) (15:21:03.405884): HTTP/1.1 503 Service Unavailable
    • Jun  5 15:21:03 localhost rfsd[8239]: [curl.INFO] (8438) (15:21:03.405912): Date: Fri, 05 Jun 2020 20:21:03 GMT
    • Jun  5 15:21:03 localhost rfsd[8239]: [curl.INFO] (8438) (15:21:03.405922): X-Squid-Error: ERR_DNS_FAIL 0
    • Jun  5 15:21:03 localhost rfsd[8239]: [curl.INFO] (8438) (15:21:03.406129): Received HTTP code 503 from proxy after CONNECT
  • and continues with the abort
    • Jun  6 01:19:23 localhost rfsd[8239]: [curl.INFO] (13031) (01:18:24.121145): Establish HTTP proxy tunnel to cloud.provider:443
    • Jun  6 01:19:23 localhost rfsd[8239]: [curl.INFO] (13031) (01:18:24.121163): CONNECT cloud.provider:443 HTTP/1.1
    • Jun  6 01:19:23 localhost rfsd[8239]: [curl.INFO] (13031) (01:18:24.121163): Host: cloud.provider:443
    • Jun  6 01:19:23 localhost rfsd[8239]: [curl.INFO] (13031) (01:18:24.121163): Proxy-Connection: Keep-Alive
    • Jun  6 01:19:23 localhost rfsd[8239]: [curl.INFO] (13031) (01:19:23.866147): Proxy CONNECT aborted
  • When using a web proxy a good connection looks like this:
    • Jun  5 09:09:29 localhost rfsd[8239]: [curl.INFO] (20275) (09:08:28.353982): Establish HTTP proxy tunnel to cloud.provider:443
    • Jun  5 09:09:29 localhost rfsd[8239]: [curl.INFO] (20275) (09:08:28.353996): CONNECT cloud.provider:443 HTTP/1.1
    • Jun  5 09:09:29 localhost rfsd[8239]: [curl.INFO] (20275) (09:08:28.353996): Host: cloud.provider:443
    • Jun  5 09:09:29 localhost rfsd[8239]: [curl.INFO] (20275) (09:08:28.353996): Proxy-Connection: Keep-Alive
    • Jun  5 09:09:29 localhost rfsd[8239]: [curl.INFO] (20275) (09:08:29.521238): HTTP/1.1 200 Connection established
    • Jun  5 09:09:29 localhost rfsd[8239]: [curl.INFO] (20275) (09:08:29.521259): Proxy replied OK to CONNECT request

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.