From user-return-2850-archive-asf-public=cust-asf.ponee.io@jclouds.apache.org Sun Sep 16 07:19:18 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 5C537180652 for ; Sun, 16 Sep 2018 07:19:18 +0200 (CEST) Received: (qmail 51637 invoked by uid 500); 16 Sep 2018 05:19:17 -0000 Mailing-List: contact user-help@jclouds.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@jclouds.apache.org Delivered-To: mailing list user@jclouds.apache.org Received: (qmail 51627 invoked by uid 99); 16 Sep 2018 05:19:17 -0000 Received: from ui-eu-01.ponee.io (HELO localhost) (176.9.59.70) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 16 Sep 2018 05:19:17 +0000 References: MIME-Version: 1.0 X-Mailer: LuaSocket 3.0-rc1 Message-ID: In-Reply-To: Content-Type: text/plain; charset=utf-8 To: x-ponymail-sender: 21219614ed8989b1a896340bd9adb1f87f95c146 Subject: hgst hcp server returning 500 internal server error Date: Sun, 16 Sep 2018 05:19:15 -0000 x-ponymail-agent: PonyMail Composer/0.3 From: john.calcote@gmail.com Hi Andrew, I know it's not your business to support HCP, but I'm hoping you've seen this sort of thing in the past and know of a possible fix/work-around for it. I've got a little test program that connects to an HGST HCP cloud server and sends a single file - no matter what settings I use, I get back a 500 internal server error (with no error details, of course). The configuration is an SSL connection using https and port 443. I had handshake fatal alerts from the server when I ran it on windows, but moving my program to a RedHat 7.3 system got me past the SSL connection issues. Now I just see that 500 internal server error when trying to putBlob. Note that I do a removeBlob first, and that succeeds (though it's likely the blob is not there). I've also tried several different content forms, including stream, string, byte array, etc. Do you know of any special configuration that must be used with HCP? (It might also interest you to know, if you don't already, that HCP returns an empty entity on this error, which jclouds attempts to parse as XML with a SAX parser. This generates a stack trace in the log. It's incidental, but you might want to try to do a little pre-checking of the content before attempting to parse it with SAX. Just a thought.) Thanks in advance, John Calcote Hammerspace, Inc.