I am trying to connect to AWS Managed Cassandra using Perl. It's not working due to a vague error Error 0: Internal Server Error.
Using the DBD::Cassandra Library, I can connect to self hosted Cassandra clusters, but not AWS Cassandra. I think I have the AWS Root CA correct because it verifies with openssl s_client -connect cassandra.us-east-1.amazonaws.com:9142
DBI->connect("dbi:Cassandra:host=cassandra.us-east-1.amazonaws.com;port=9142;tls=1;keyspace=keyspace",
"**username**", "**password**");
The error response from the connection is
Unable to connect to any Cassandra server.
Last error: On cassandra.us-east-1.amazonaws.com:
Error 0: Internal Server Error
I can also connect using the cqlsh client and verified that the connection details are correct.
Any hints or a working example would be very helpful.
The issue appears to be setting the keyspace. Doing this either on the connection or subsequently with use keyspace results in a Error 0: Internal Server Error response from the server.
Also note that AWS Managed Cassandra only supports consistency local_quorum. The following will result in a valid connection:
DBI->connect("dbi:Cassandra:host=cassandra.us-east-1.amazonaws.com;
port=9142;tls=1;consistency=local_quorum",
"**username**", "**password**");
Since there are issues setting the keyspace, tables must be referenced using keyspace.tablename in queries.
Related
I am using DMS to migrate date from MySQL to Redshift. I need to add new task,but it does not run because endpoint connection test fails, but I use already working endpoint. Although task with this endpoint is running without error, test is failing with this strange error
Test Endpoint failed: Application-Status: 1020912, Application-Message: Failed in prepare imp for Redshift Base general error.
Restarting DMS instance fixed the issue.
we created a project with ibm functions and event-streams in IBM Cloud.
Now, I am trying to connect KSQL with IBM cloud Event Stream, and I am following along the Document for getting basic ideas of integration.
By following the instructions, I created a file called ksql-server.properties and modified bootstrap.servers, username, password according to my credentials. Then I ran ksql http://localhost:8088 --config-file ksql-server.properties with ksql local cli. I assume everying runs correctly so far since the ksql> shows in the front of every new line...
Then I decided to check if the ksql connected with my ibm cloud by running SHOW topics;
Turns out some error lines:
`Error issuing POST to KSQL server. path:ksql'`
`Caused by: com.fasterxml.jackson.databind.JsonMappingException: Failed to set 'ssl.protocol' to 'TLSv1.2' (through reference chain: io.confluent.ksql.rest.entity.KsqlRequest["streamsProperties"])`
`Caused by: Failed to set 'ssl.protocol' to 'TLSv1.2' (through reference chain: io.confluent.ksql.rest.entity.KsqlRequest["streamsProperties"])
`
`Caused by: Failed to set 'ssl.protocol' to 'TLSv1.2'`
`Caused by: Cannot override property 'ssl.protocol'`
Also, I am quick lost at step 4 when it tells me to:
`Then start DataGen twice as follows:
i. With bootstrap-server=HOSTNAME:PORTNUMBER quickstart=users format=json topic=users maxInterval=10000 to start creating users events.
ii. With bootstrap-server=HOSTNAME:PORTNUMBER quickstart=pageviews format=delimited topic=pageviews maxInterval=10000 to start creating pageviews events.`
Is there anyone have done this before or would love to help me out? Thank you very much!!!
The IBM document is very out of date. KSQL runs as a client/server. The server needs to be run with the details of the broker, and then you can connect to it with a client, including the CLI, REST API, or web interface provided by Confluent Control Center.
So you need to run the KSQL server using your properties file:
./bin/ksql-server-start ksql-server.properties
and then connect to it with the CLI (for example):
./bin/ksql http://localhost:8088
See https://docs.confluent.io/current/ksql/docs/installation/installing.html for more information.
I'm trying to create a service-connector to my s3 instance like this:
cf service-connector 13001 mybucketname.ds31s3.swisscom.com:443
But I get the following error:
Server-Error 403: Check of security groups failed (no access)
I have created my service key according to this documentation.
Connecting to my MongoDB works perfectly using a service connector.
You can access Swisscom's S3 directly without the service connector.
The error message suggests that your current org and space do no have access to the S3. This is usually the case is there is no app-binding for that service in the current space. Please check whether you created your service key in the right org and space.
There was a misconfiguration due to security changes. We fixed the issue, so connecting to s3 with the service-connector should now work.
This is regarding WSO2 API Manager Worker cluster configuration with external Postgres db. I have used 2 databases i.e wso2_carbon for registry and user management and the wso2_am, for storing APIs. Respective xmls have been configured. The postgres scripts have been run to create the database tables. My log console when wso2server.sh is run, shows enabled clustering and the members of the domain. However on the https://: when I try to create to create APIs, it throws and error in the design phase itself.
ERROR - add:jag org.wso2.carbon.apimgt.api.APIManagementException: Error while checking whether context exists
[2016-12-13 04:32:37,737] ERROR - ApiMgtDAO Error while locating API: admin-hello-v.1.2.3 from the database
java.sql.SQLException: org.postgres.Driver cannot be found by jdbc-pool_7.0.34.wso2v2
As per the error message, the driver class name you have given is org.postgres.Driver which is not correct. It should be org.postgresql.Driver. Double check master-datasource.xml config.
I tried to establish connection using Dataworks Forge for sql db, I got following error.
Unable to establish a connection using the supplied values.Check that all values are correct and try again. Internal Details: Failed to send the request to the handler: The agent at yp-iis-dataworks-ga-wdc01-2-12-0-0-5-vm5:31531 is not available.; nested exception is: com.ibm.iis.prs.exception.CommunicationException: Failed to send the request to the handler: The agent at yp-iis-dataworks-ga-wdc01-2-12-0-0-5-vm5:31531 is not available.
I input the values based on VCAP_Service, and double checked it. How can I troubleshoot this?
Connection name sqldb1
Host 75.126.155.1xx
Database SQLDB
User user06xxx
Port 50000
Password xxx
Today, I did same thing when I posted this question and could establish connection successfully.
As Nigel mentioned, the dataworks service states when I posted was green. But maybe there were some issues. And they were fixed now.