---------- Forwarded message ---------- From: Mail Delivery Subsystem <[email protected]> Date: Sat, Nov 5, 2016 at 5:14 PM Subject: Delivery Status Notification (Failure) To: [email protected]
Hello [email protected], We're writing to let you know that the group you tried to contact (jclouds-dev) may not exist, or you may not have permission to post messages to the group. A few more details on why you weren't able to post: * You might have spelled or formatted the group name incorrectly. * The owner of the group may have removed this group. * You may need to join the group before receiving permission to post. * This group may not be open to posting. If you have questions related to this or any other Google Group, visit the Help Center at https://groups.google.com/support/. Thanks, Google Groups ----- Original message ----- X-Received: by 10.28.157.213 with SMTP id g204mr244524wme.21.1478362484427; Sat, 05 Nov 2016 09:14:44 -0700 (PDT) Return-Path: <[email protected]> Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com. [2a00:1450:4010:c07::22d]) by gmr-mx.google.com with ESMTPS id y7si194832wme.0.2016.11.05.09. 14.44 for <[email protected]> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 05 Nov 2016 09:14:44 -0700 (PDT) Received-SPF: pass (google.com: domain of [email protected] designates 2a00:1450:4010:c07::22d as permitted sender) client-ip=2a00:1450:4010:c07:: 22d; Authentication-Results: gmr-mx.google.com; dkim=pass [email protected]; spf=pass (google.com: domain of [email protected] designates 2a00:1450:4010:c07::22d as permitted sender) smtp.mailfrom=run2obtain@ gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Received: by mail-lf0-x22d.google.com with SMTP id o141so12813704lff.1 for <[email protected]>; Sat, 05 Nov 2016 09:14:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=janoJdSe/cACZQGSUidIGojVMqVMOu6iQqOm/b9ahKY=; b=hsCry6gb5P/3t+EONSDqzCs0XOC39o0pOG+3VF6jGH5XiCbtFEsLMHrxDzsAdF5Wvu YKR7F7Z+wJUC/rkY0Vt+YxX/PiGQhI1SuBZm9oaYX0qv13pSKZLj6q BuWPJhuEQZP7V6 2w4mUuXQvj9s88QOvY32hjN9YXPm+e/jEgVKvULx0lZDPuRGLQDb0ZbLXqvlf Do8t7Gx GEDQOvPdqi8UXK4gOgYf5Z2xBZk7KI5UXWwHhRS+ Z0qceCFmfEqZO3RCtpmOQRuMAtvI lO4G9vtNTg87YLqJDexH83TfjRYCC0jXRraYvCkpQWIDJ5MlEgMglYxZGaAS 5EofE4dc sihQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=janoJdSe/cACZQGSUidIGojVMqVMOu6iQqOm/b9ahKY=; b=YSweR2FdXMEP4ux93S6RSAaariccvru3kAgvxEz62rHP9M/p4sBFO2BwezPVtSeuPo Lq917UzvO5AZpjy1QJIhX3NGqMiEvBk2AH2e3cilWet88116TpkJaO99xt39 8gr5r8LU SbNDhm/oPmdpsXEoRufzYen2sYjdNhbkugjAAKy4+fl/I+drb9HCSm63+ U4V2nr7fcuW 5krWhKsBdE69y2g81AtufKo4d7WJFqoW3BVPrEiEPoEDq+QHae+ uh0NbhFsUHs+6qFlM LeWMF75xuAZl5J3/J2lpBF/NLJAlPuRwOzC3Tk57Us55CJajtPRrS trZxEm0GcM1rTxQ uEFA== X-Gm-Message-State: ABUngvfRYCPqbKTotZzkLqphBB3GF+ cqNK2L6n9wOnLzNWJh4I8Q5UVtsLJaqjx84ythZY7wwdLaS5cj35Clmg== X-Received: by 10.25.39.13 with SMTP id n13mr10103095lfn.34.1478362483560; Sat, 05 Nov 2016 09:14:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.160.20 with HTTP; Sat, 5 Nov 2016 09:14:43 -0700 (PDT) From: Ken <[email protected]> Date: Sat, 5 Nov 2016 17:14:43 +0100 Message-ID: <CAGeQc9DzfGZ19zBP6E+myJxfT+WvSk+PBDf3Mp6ZZp8ZmFUuSw@mail. gmail.com> Subject: JClouds Swift Connection Issue To: [email protected] Content-Type: multipart/alternative; boundary=001a11403cc4ae9604054090164a Hi everyone, I have tried to resolve this error since yesterday without any progress. The scenario ; I have an OpenStack cloud running behind a firewall. I have configured port forwarding and I can ssh into the VM. I want to use Jcloud swift and nova, the connection always time outs after successfully authenticating... " Create Container 17:04:59.927 [main] DEBUG o.j.rest.internal.InvokeHttpMethod - >> invoking AuthenticationApi.authenticateWithTenantNameAndCredentials 17:04:59.930 [main] DEBUG o.j.h.i.JavaUrlHttpCommandExecutorService - Sending request -522644011: POST http://seclab.hpi.uni-potsdam.de:50034/v2.0/tokens HTTP/1.1 17:04:59.930 [main] DEBUG jclouds.wire - >> "Sensitive data in payload, use PROPERTY_LOGGER_WIRE_LOG_SENSITIVE_INFO override to enable logging this data." 17:04:59.930 [main] DEBUG jclouds.headers - >> POST http://seclab.hpi.uni-potsdam.de:50034/v2.0/tokens HTTP/1.1 17:04:59.930 [main] DEBUG jclouds.headers - >> Accept: application/json 17:04:59.930 [main] DEBUG jclouds.headers - >> Content-Type: application/json 17:04:59.930 [main] DEBUG jclouds.headers - >> Content-Length: 93 17:05:00.108 [main] DEBUG o.j.h.i.JavaUrlHttpCommandExecutorService - Receiving response -522644011: HTTP/1.1 200 OK 17:05:00.108 [main] DEBUG jclouds.headers - << HTTP/1.1 200 OK 17:05:00.108 [main] DEBUG jclouds.headers - << Keep-Alive: timeout=5, max=100 17:05:00.109 [main] DEBUG jclouds.headers - << Server: Apache/2.4.7 (Ubuntu) 17:05:00.109 [main] DEBUG jclouds.headers - << Connection: Keep-Alive 17:05:00.109 [main] DEBUG jclouds.headers - << x-openstack-request-id: req-e9eba153-3fd2-45d0-ba17-1003596986bc 17:05:00.109 [main] DEBUG jclouds.headers - << Vary: X-Auth-Token 17:05:00.109 [main] DEBUG jclouds.headers - << Date: Sat, 05 Nov 2016 16:04:18 GMT 17:05:00.109 [main] DEBUG jclouds.headers - << Content-Type: application/json 17:05:00.109 [main] DEBUG jclouds.headers - << Content-Length: 3518 17:05:00.112 [main] DEBUG jclouds.wire - << "{"access": {"token": ----- Message truncated -----
