In my Pulsar consumer/producer, when trying to connect to Pulsar, I'm getting this error message:
java.util.concurrent.CompletionException:
org.apache.pulsar.client.api.PulsarClientException:
java.util.concurrent.CompletionException:
org.apache.pulsar.shade.io.netty.channel.AbstractChannel$AnnotatedConnectException:
syscall:getsockopt(..) failed: Connection refused:
pulsar-ms-tls.mydomain.com/10.16.60.179:6652
What could be the issue?
You are trying to reach the wrong port. Pulsar, by default, uses port 6651. Please verify that you're using the correct port (based on how your Pulsar cluster has been configured).
It's also possible that your IP address is incorrect, so be sure to double-check that you're hitting an IP address that's running a broker instance.
Related
I am trying to connect to oracle database hosted on Linux server remotely from my windows machine and getting error ORA-12170: TNS: Connect Timeout. I've already checked the following:
listener.ora configuration and it's status.
tnsnames.ora naming parameters.
firewall is listening on the IP and the default port 1521
If there is no firewall between the client and the target database then you should not normally need to adjust the timeout. You can try adjusting the sqlnet parameters mentioned in the error message: *Action: If the error occurred because of a slow network or system,
// reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT,
// SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values.
- -
However, I think you should ask your network team to trace your connection attempt especially if after increasing the timeout you still get the error. The full Oracle version in use and the platforms (client and target) may be important.
I am new to Cassandra. I installed Cassandra in Cloud server & its up and running.
I downloaded "No Sql Manager" to connect to Cassandra DB. While trying to connect giving error as below.
All hosts tried for query failed (tried 127.0.0.1:49984: SocketException 'A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied') Details: A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied
How to connect?
Is your Cassandra node running on the same node as NoSQL Manager? If not, then you should supply the actual (external) IP address, and not 127.0.0.1.
Also, Apache Cassandra by default accepts client connections on port 9042. I'm not sure where 49984 is coming from, but try changing that to 9042, instead.
When executing into a pod I get following message
Error from server: error dialing backend: dial tcp: lookup k8s-worker-node-a on 192.168.1.1:53: no such host
Is it possible to tell kubectl to use /etc/hosts to lookup machines as I have saved them inside there.
Can the API server resolve that hostname? It's insufficient for just your workstation to know the hostname, since the API server must be able to contact kubelet on the Node to construct the URL used to view the logs
Turning up the verbosity of kubectl will show the actual handshaking that goes on between your machine, the API server, and the kubelet on the Node, which is how we discovered a similar misconfiguration in our cluster.
Your server is not listening or accepting connections on 127.0.0.1:9042. Verify host and port information is correct
VM: 127.0.0.1:9042
JDBC URL :jdbc:cassandra://127.0.0.1:9042/quantum_cassandra
Driver:cdata.jdbc.cassandra.CassandraDriver
Appreciate your help on this.
This error message in Aqua Data Studio indicates that your host/port is incorrect, or your server is not listening on that port, or a firewall is blocking network access to it.
You just need to make sure your server is running correctly and no firewall is blocking your connection. Note that IP address 127.0.0.1 is a local loopback and is only accessible on the same machine and not remotely.
i'm trying to create restcomm cluster: sip-balancer + a few restcomm instances. But i can't connect restcomm node and sip-loadbalancer.
i used this tutorial - http://docs.telestax.com/sip-servlets-clustering-high-availability/ however haven't got any result.
Seems it should be 2 steps
change path-name attribute in
standalone/configuration/standalone-sip.xml
add org.mobicents.ha.javax.sip.BALANCERS to
standalone/configuration/mss-sip-stack.properties
as i understand node and loadbalancer use rmi as channel. i see(i used netstat) that server listens port 2000 and node establishes connection to it.
but when i try to use loadbalancer from sip client it returns "error 500 - no available nodes".
also i used remote debugged - nodes list is empty.
have i missed something?
p.s. i used docker restromm instance and sip-loadbalancer on the same machine.
thanks,
so i have found my issue.
According to the log file on restcomm node - it can't connect to balancer by RMI.
Connection error is very strange - Connection refused to host: 127.0.0.1 and sometimes Connection refused to host: 127.0.1.1
yesterday i tired to specify java.rmi.server.hostname but it did not help me
today i created small RMI client to balancer and it worked from my local machine(balancer is hosted on it too). however this app did work from virtual machine. so i added more logs to code and found:
app can lookup remote been
remote endpoint of this been is 127.0.0.1, but should be ip address of remote machine
After that i specified externalHost and public-ip for my sip-balancer and got bean endpoint address with 127.0.1.1
so issue was found - ubuntu uses this "local" ip address for your "machine name".
you can find it in /etc/hosts.
sip-balancer(java application) gets it as ip address of endpoint for services
My fix is - change 127.0.1.1 to 127.0.0.1 in /etc/hosts. after that sip-balancer provides real ip address of your machine for remote objects.
Conclusion: my issue - wrong operation system :)
Common solution: developer should check address type and don't use loopback addresses.