I have a problem when I install rabbitMQ Silently (not normal), It is installed successfully and I see the rabbitmq in services and started but when I try to run rabbitmqctl or rabbitmq-plugins I face the following error:
* Connection attempt from disallowed node 'rabbitmq-plugins1208079#WIN-IOBM5KICB89' **
I found a work around for this when I copy the .erlang.cookie from C:/{User} to C:/Windows, the problem is solved, any I dea why is this happening and if there is any other solutions for this?
The cookie is used by the underlying erlang environment to decide to allow/block the connections. More information is here
Related
When attempting to run Boot inside Docker, using the adzerk/boot-clj image, I receive connection refused errors.
Specifically, when the container starts up, boot is started, and then a stack trace is output. The trace (which is not easy to copy and paste between computers with no connectivity) essentially is to do with downloading - https://github.com/boot-clj/boot/releases/download/2.7.2/boot.jar - and receiving "Connection refused" errors.
I’m asking, and answering this, question in the hope that it might help someone else.
Where to start?
My main problem was with a Docker + Clojure + Boot setup, specifically when running “boot” from inside the container. Doing this spewed out a stack trace. This is where my journey begins.
I’m using the adzerk/boot-clj image. I’ve used it locally (OSX) without issue, the problem I experienced was in using a VM (CentOS 7) hosted within a corporate data center.
docker run -ti adzerk/boot-clj
Issuing this starts up the container, the entry point is Boot, and it starts pulling down some jars, specifically boot.jar from Github. The resulting stack trace details several problems, but the crux of it was
“java.net.ConnectException: Connection refused” (connecting to Clojars.org:443)
Hmmm…
So instead of running Boot straight away in the container, I specified the container entry point as “—-entrypoint bash” so I can prod around a little.
So, wget - connection refused.
What about without Docker in the way. Same thing. Connection refused.
After a little wrangling with the network team, I found that the “https_proxy” env variable needs to be set on CentOS to route traffic out to the internet. A very specific issue to me in the situation.
However….
wget is now fine, both on the host, and inside the adzerk/boot-clj container. Boot however was not.
In an effort to simplify things even more, I took Docker out of the equation entirely, and used boot locally.
Installed java-1.8.0-openjdk.x86_64, installed Boot. Same problem.
So dug around a little, and found this - https ://github.com/boot-clj/boot-bin/issues/2
This was a start. It mentions setting the BOOT_JVM_OPTIONS, specifically https.proxyHost and https.proxyPort.
It still didn’t work… Arrrg.
OK, let’s take Boot out of the equation.
I wrote a test harness in Java, very simple that connects to https ://clojars.org and attempts to read the index page. Copied from https ://docs.oracle.com/javase/tutorial/networking/urls/readingWriting.html, and setting the JVM_OPTS.
It still fails. “Connection refused”
…. Weird beard.
I finally stumbled on this SO - https ://stackoverflow.com/questions/43695299/java-httpurlconnection-works-on-windows-and-fails-on-linux - specifically the answer from Stephen C
“Java doesn't necessarily respect your system's default proxy settings. Since you are able to "curl" the URL on the Linux machine, the most likely explanation is that Java is not using the proxy that you have configured. The following links explains various ways to configure the proxies for Java:”
So taking the first link - https ://stackoverflow.com/questions/120797/how-do-i-set-the-proxy-to-be-used-by-the-jvm - and the answer from Leonel
I issued “java -Dhttps.proxyHost=xxx -Dhttps.proxyPort=80 HelloWorld”
I get an error, but a different one. This is progress. “Unable to tunnel through proxy”
A quick Google of this led me here: http ://www.oracle.com/technetwork/java/javase/8u111-relnotes-3124969.html - “Disable Basic authentication for HTTPS tunneling”
So updated to “java -Dhttps.proxyHost=xxx -Dhttps.proxyPort=80 -Djdk.http.auth.tunneling.disabledSchemes=“” HelloWorld
Profit.
Info:
java -v
openjdk version 1.8.0_144
Openjdk Runtime Environment (build 1.8.0_144-b01)
OpenJDK 64-Bit Server VM (build 25.144-b01, mixed mode)
Sorry for all my profanity Boot.
I am using Neo4j Community Edition 3.1.1 on Mac OS X Sierra. Whenever I try to start Neo4j locally via
neo4j start
I get the following:
Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase#a8ba98d' was successfully initialized, but failed to start.
Please see attached cause exception.
with the following exception at the tail of /usr/local/Cellar/neo4j/3.1.1/libexec/logs/neo4j.log
Caused by: org.neo4j.helpers.PortBindException: Address localhost:7687 is already in use, cannot bind to it.
I tried running
lsof -i -n -P | grep 7687
but it came back empty.
Please advise.
Note: I'd leave this as a comment, but don't have the required rep.
Are you sure that you have only one version of Neo4j installed?
Is your installation clean, without any traces of previous installations?
Is your JDK version >= 8?
Have you made other changes to your conf file?
Do you have the desktop app installed? des it work without issues?
Your lsof could be returning an empty value as some pids are only visible to root. Try:
sudo netstat -antlp
This should return all open ports, check if anything corresponds to 7687.
Also try running neo4j as a service. I believe it's launchctl on Mac (I use systemctl on Linux) and check if the error persists.
Cheers
I had the same exact issue, notice how neo4js is trying to get to localhost:7687?
I checked my /etc/hosts file and sure enough, I had a bogus entry for localhost (from previous testing).
I changed /etc/hosts entry back to
localhost 127.0.0.1
Saved, then ran again.
Neo4j started up fine after that.
My steps are below:
Download the heroku-osx.pkg, and installed it.
$ heroku login with my account and password
cloned the ruby-getting-started: $ git clone https://github.com/heroku/ruby-getting-started.git
But when I run $ heroku create in my Terminal.
Reports the error:
Creating app... !
▸ ENOTFOUND: getaddrinfo ENOTFOUND api.heroku.com api.heroku.com:443
I have find the related question in SO:
I got error while using "git push heroku master"
Hibernate unable to create schema automatically on Heroku postgres
But they are not when execute $ heroku create comes out the error.
The same was happening to me on Mac OS X 10.12.6 in iTerm2 3.1.5
Restarting iTerm solved the issue for me.
Carelessly, I don't know why, I tried several times of :
$ heroku create
It create succeed, with the logs:
Creating app... done, ⬢ still-harbor-32209
https://still-harbor-32209.herokuapp.com/ |
https://git.heroku.com/still-harbor-32209.git
So, I think try several times will solve it.
It means that the connection between api.heroku.com with a port of 443 and to your PC failed and results to shutdown. Thus retrying the command will succeeds.
You may not be connected to the internet. Make sure to check your connection as it is required to complete this command.
I experienced the same issue recently.
To debug this:
1) I tried restarting my terminal entirely CMD+Q, but still hit the timeout issue
2) I ran a whois on my-heroku-app.com and that command also timed out, even though I could connect to it through my browser
3) I disconnected my VPN and ran a whois command. This fixed the issue
After reconnecting my VPN, everything worked smoothly. Not sure what caused the hiccup, but I hope these steps help for anyone trying to debug this.
This happened to me when the internet temporarily cut out for a few seconds while I was trying to run a heroku command.
The Heroku CLI returned Error: getaddrinfo ENOTFOUND api.heroku.com
As soon as the internet connection was restored, everything was back to normal
I had a similar issue. my OS is windows, I solve this problem by restarting my command line and running the command all over and everything worked fine
The problem for me was network connection, by checking and re-establishing connection, it worked perfectly fine
I was getting the same , Because I was connected to VPN and I think network was blocking the same . So disconnect VPN and try once.
After installing RabbitMQ (rabbitmq-server-3.6.0) and Erlang (esl-erlang_18.2-1-windows_i386) I am not able to see the port 5672 in list of listening ports in by netstat -an command but in task manager under services category I am able to see RabbitMQ with Running status.
After installing RabbitMQ I had created two environment variables. they are:
RABBITMQ_SERVICE to C:\Program Files\RabbitMQ Server\rabbitmq_server-3.6.0
and
RABBITMQ_BASE to C:\Program Files\RabbitMQ Server
Later I reinstalled Rabbitmq and Erlang but not from scratch as I was not able to delete files completely.
Is my server up? Or is my installation wrong? Or do I have to anything in excess.
I completely have no idea on it or what is going on.
yes, this was solved. I didn't have permission to install new software on my machine. Though it showed as installed successfully because of permission issues I was not able to use the tool. once permission issues got resolved everything was fine :).
I also faced the same issue. I have got right permissions to install software. Still while installing rabbit-mq it was giving an error Port 5672 is not listening
After more investigation, I found that there was already running process on this port. I ran below commands:
netstat -ano | findstr ":5672"
taskkill /F /PID 18644
This resolved my issue.
I am totally new to Cassandra and met the following error when using cqlsh:
cqlsh
Connection error: Could not connect to localhost:9160
I read the solutions from the following link and tried them all. But none of them works for me.
How to connect Cassandra to localhost using cqlsh?
I am working on CentOS6.5 and installed Cassandra2.0 using yum intall dsc20.
I ran into the same issue running the same OS and same install method. While the cassandra service claims that it's starting ok, if you run service cassandra status it would tell me that the process was dead. Here are the steps I took to fix it:
Viewing the log file at /var/log/cassandra/cassandra.log gave told me that my heap size was too small. Manually set the heap size in /etc/cassandra/conf/cassandra-env.sh:
MAX_HEAP_SIZE="1G"
HEAP_NEWSIZE="256M"
Tips on setting the heap size for your system can be found here
Next, the error log claimed the stack size was too small. Once again in /etc/cassandra/conf/cassandra-env.sh find a line that looks like JVM_OPTS="$JVM_OPTS -Xss128k" and raise that number to JVM_OPTS="$JVM_OPTS -Xss256k"
Lastly, the log complained that the local url was misformed and threw a java exception. I found the answer to the last part here. Basically, you want to manually bind your server's hostname in your /etc/hosts file.
127.0.0.1 localhost localhost.localdomain server1.example.com
Hope this helps~
Change:
/etc/cassandra/cassandra.yaml
Whether to start the thrift rpc server.
start_rpc: false
to
start_rpc: true