I am getting error failed to connect to 127.0.0.1:7199: connection refused when I do a nodetool status on my RHEL machine. It was working fine until yesterday but today it suddenly started giving this error. I did not make any changes to the configuration files.
I have DSE installed and properly configured as it was running fine till yesterday from past 3-4 months. The cassandra.yaml has the cluster name, seed, rpc address, rpc port, listen address all configured correctly. Also I set -Djava.rmi.server.hostname=<server ip address>; in cassandra-env.sh. Still did not work. Nor am I able to connect to cqlsh, nor my SOLR is accessible after this. Also I have allowed all ports on my security group on my machine to check if it is any port problem but it is not.
Any help would be appreciated.
Check your /etc/cassandra/cassandra.yaml file. It should be like
authenticator: AllowAllAuthenticator
Problem may be caused of this.
I was getting the same error, and it worked for me after the following commands:
systemctl start cassandra
systemctl restart cassandra
Related
[
I install orcle database and oracle apex locally but
I am getting this error, when try to open the workspace
also the same schema when try to connect through the sql developer not connect and error show
How can I fix that?
To connect to the database, you make a request to a "listener" which then hands off your connection to the database. The listener listens (hence the name) on a port. If your listener is not running, or you are sending your request on the wrong port, then you see errors like this, because we can't find the listener.
Try this on a command line:
lsnrctl status
If you get errors, then your listener probably is not running. Go into Services, and you look for OracleTNS.... and start that. If your output suggests the listener is up and running already, then look for the information about the port and IP address (or hostname) that it is listening on. You then use those for your connection details in SQLDev and ORDS and the like.
While connecting to sybase, i'm trying to start my server using
startserver
but, i have encountered the above error.
The usual way to start a Sybase instance is:
startserver -f RUN_SERVER_FILENAME
e.g RUN_MY_INSTANCE or similar depending on what your Sybase instance is called. Once its started correctly then you should be able to connect. This is usually in the $SYBASE/$SYBASE_ASE/install directory on a default installation for Unix.
More info here:http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc30191.1570100/doc/html/san1367605056632.html
Are you getting any other messages? You should look at the instance errorlog to check for problems on startup.
I have a clickhouse server running on Linux subsystem for Windows on a Windows 2016 server. I've setup firewall rules for both inbound and outbound connections on both 9000 and 8123 ports. I used the default config. When I try to connect remotely got this exception:
DB::Exception: User default is not allowed to connect from address ::ffff:10.201.1.2
How should a user config look like so that a remote connection goes through.
In the users.xml configure the networks settings
<networks>
<ip>::/0</ip>
</networks>
In config.xml uncomment
<listen_host>::</listen_host>
You should allow access from external networks for default user. Add
<networks>
<ip>::/0</ip>
</networks>
to default user configuration. More details here.
Also it should be enabled by default.
I figured out the issue by myself.
I noticed that by default there is a allow_only_from_localhost.xml file inside the dbms\src\Server\user.d directory. So I thought I should remove this file and everything is going to work. It did not help, but I got inspired and moved my networks.xml file into the dbms\src\Server\user.d directory and TA-DA! remote connection finaly started working. Aside from relocating the file, I also adjusted its content, so that it matched the syntax from allow_only_from_localhost.xml file. It did not matter, Whether I kept the allow_only_from_localhost.xml file in the dbms\src\Server\user.d directory or not, remote connection worked in both cases.
I have setup 3 servers with Amazon EC2, and have each server with the following Zookeeper-config.
tickTime=2000
initLimit=10
syncLimit=5
clientPort=2181
server.1=server1address:2888:3888
server.2=server3address:2888:3888
server.3=server3address:2888:3888
I start zookeeper on each server, and after I start Solr on the servers, I get errors like this in Solr:
3766 [main] INFO org.apache.solr.common.cloud.ConnectionManager – Waiting for client to connect to ZooKeeper
3790 [main-SendThread(*serverAddress*:2181)] WARN org.apache.zookeeper.ClientCnxn – Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:350)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1068)
This was apparently coming because Zookeeper wasn't running properly. What I then figured out was that zookeeper was producing this error:
2013-06-09 08:00:57,953 [myid:1] - INFO [ec2amazonaddress.com/ipaddress#amazon:QuorumCnxManager$Listener#493] - Received connection request /ipaddress:60855
2013-06-09 08:00:57,963 [myid:1] - WARN [WorkerSender[myid=1]:QuorumCnxManager#368] - Cannot open
channel to 3 at election address ec2amazonaddress/ipaddress#amazon:
3888
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
at java.net.Socket.connect(Socket.java:579)
at org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:35
4)
So the problem is with ZooKeeper. What I did was to start another server before the server I previously started first, and then it worked. However, after some restarts that didn't work anymore. In other words, it seems like the order of when you start the ZK server matters. I was able to see that some servers who were fired up first went into follower mode instead of leader mode right away, and maybe that's the reason. I have deleted and reinstalled my whole setup, but the problem was still there.
I have checked the ports and have killed all processes using ports 2181 and 2888/3888 before launching Zookeeper. What bothers me is that this has worked with the same setup earlier.
Hope some of you guys have some experience with this problem. Any suggestion that could be related to not being able to connect to ZK-servers is also welcomed
Some of the project assets are ERBs (like file.js.coffee.erb) that will pull data from the database as to write themselves up. Database tables seems to be created ok, but Heroku keeps halting at the precompile with an error like this:
could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?
Well, ok. I searched in Heroku Devcenter for help and found an article that explained this was actually happening due to the lack of config vars in the environment. So the instruction was to run:
env RAILS_ENV=production DATABASE_URL=scheme://user:pass#127.0.0.1/dbname bundle exec rake assets:precompile 2>&1
So I run the command with the proper replacements, from the Heroku's tollbelt (heroku run ...), putting postgresql as the scheme, also filling user, pass, and dbname fields properly. An then, again:
rake aborted!
could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?
(in /app/app/assets/javascripts/file.js.coffee.erb)/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.9/lib/active_record/connection_adapters/postgresql_adapter.rb:1208:in `initialize'
Seems like I was suposed to use some real info from Heroku's automated database configurations, but I just have no idea what are those configurations.
I'm kinda stuck with that. Anyone could lend a hand?
Thanks very much!
You can get around this by enabling user-env-compile:
Heroku Labs: user-env-compile
It's generally discouraged but kind of needed in your situation.