-
1. Re: S3_Ping - Authentication Failed
galder.zamarreno Jun 22, 2018 9:40 AM (in response to balajiora) -
2. Re: S3_Ping - Authentication Failed
balajiora Jun 25, 2018 5:30 AM (in response to galder.zamarreno)Tried that option also and I am getting the following error message. And I checked in the jgroups.xsd (http://www.jgroups.org/schema/jgroups.xsd) not finding the attribute for NATIVE_S3_PING)
Caused by: java.lang.Exception: JGRP000002: unable to load protocol org.jgroups.aws.s3.NATIVE_S3_PING (either with relative - org.jgroups.aws.s3.NATIVE_S3_PING - or absolute - org.jgroups.protocols.org.jgroups.aws.s3.NATIVE_S3_PING - class name)
Version of Infinispan (infinispan-core-8.4.2.Final-redhat-1.jar:8.4.2.Final-redhat-1) & JDK1.8
Regards
Balaji Subramaniam
-
3. Re: S3_Ping - Authentication Failed
balajiora Aug 7, 2018 8:57 AM (in response to balajiora)I removed the bucket name and getting the following error message
<S3_PING
host="dummyhost"
access_key="dummy_access_key"
secret_access_key="dummy_secret_access_key"
/>
Caused by: java.io.IOException: bucket '/tmp/jgroups' could not be accessed (rsp=403 (Forbidden). Maybe the bucket is owned by somebody else or the authentication failed
at org.jgroups.protocols.S3_PING$AWSAuthConnection.checkBucketExists(S3_PING.java:491) ~[jgroups-4.0.1.Final-redhat-1.jar:4.0.1.Final-redhat-1]
If I add the bucket name "<bucket name>" I am getting different error
<S3_PING
host="dummyhost"
access_key="dummy_access_key"
secret_access_key="dummy_secret_access_key"
location="bucketname"
/>
Caused by: java.net.UnknownHostException: dev_hostanem.net
Can anyone help me understand, why the host and bucket name is appending here in host info?
Regards
Balaji Subramaniam
-
4. Re: S3_Ping - Authentication Failed
belaban Jul 2, 2018 3:11 AM (in response to balajiora)You have to include the dependency on NATIVE_S3_PING JAR in your POM, see [1] for details.
[1] GitHub - jgroups-extras/native-s3-ping: A port of Zalando's NATIVE_S3_PING to JGroups 4.x
-
5. Re: S3_Ping - Authentication Failed
belaban Jul 23, 2019 3:53 AM (in response to balajiora)I guess the DNS server cannot resolve bucketname.s3.xx.yyy. I suggest check with the admins running that domain. If you ping bucketname.s3.amazonaws.com (take *any* bucket name), this always resolves correctly.