I am trying to start JBoss 7.x in debug mode by uncommenting the JAVA_OPTS line in standalone.conf file. I see a very strange behaviour that JBoss does not start, it quits with the error " JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)" BIND problem.
Has any one seen this issue. Port number is 8787 and when I do netstat I don't see anything running on 8787.
Any ideas?
if netstat | grep 8787 does not give any result, then you could try with netstat -an | grep 8787 to see the state of all sockets.
please provide the value of the JAVA_OPTS variable.
Point 1: the JAVA_OPTS can be found in two files : run.conf and run.conf.bat. It should be un-commented only in one place, otherwise you will get some error like 'multiple definition of JAVA_OPTS', or something like that.
Point 2: Accidentally, I hit the exact same error as you did - JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) - while following the advice from https://stackoverflow.com/a/1921406/11233118
setting address with address=HOSTNAME_OR_IP:8787 is wrong. Use only address=8787. Don't know if that is the cause of your problem, but I got that error this way. Please take a look at https://stackoverflow.com/a/516214/11233118 for detailed set-up information.
Related
I have code for web ui automation test created with Katalon, I have tried to run it locally and it worked well.
Then I push my code to server but when I run it from server, it failed. It failed to open the web/url that i want.
I generate the code to execute test from server but when I run that code this is happened :
bind failed
then it kept loading the browser until it timed out :
Can anyone suggest/comment or help with a solution for this?
This error message...
[SEVERE]: bind() failed: Cannot assign requested address (99)
...implies that the ChromeDriver was unable to bind the Browsing Context i.e. Chrome Browser session.
Initiating ChromeDriver with --verbose flag would have helped to debug the issue in a better way.
Solution
As per the documentation in [Errno 99] Cannot assign requested address when starting Dockerized web app the probhable cause and the solution would be to:
Close all processes that may be running on your port number. Assuming you are running on port 8000:
lsof -t -i tcp:8000 | xargs kill -9
You are probably using an app adress as localhost or 127.0.0.1 and you need to change it to 0.0.0.0
Another possible reason can be, google-chrome attempted to listen on IPv6 address, which was not enabled. You can either enable IPv6 support (which works only on Linux host) or ignore the error since ChromeDriver process will be listening on IPv4 after initial failed attempts.
When i start any web project in netbeans it start tomcat in xammp by dfault but when tomcat is in running state Mysql(php admin) page not open i think there is some kind of port issue please guide me about this issue
change pot mo in config files
Find out what ever the port that error cause and you can kill that usage by following theses steps. Here I take 3325 as my port.
Open cmd and type netstat -ano | findstr 3325.
Then type this code with what ever the output that you gets. Here I get 10360 as my output for the 1st one. taskkill /F /pid 10360
Using this method you can kill the process of port that already in use. Kill the relevant process that is not needed if there are multiple processes hang on this port. This might be helpful to fix your issue.
In preparation for remote debugging I have started (on Mac):
java Test -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9000
It is running in a loop.
Is there a simple way to verify that the process is indeed listening on port 9000?
Will a console command work for you?
netstat -aln | grep 9000
UPD: Who is listening on a given TCP port on Mac OS X?
Looks like the problem was trivial: "java Test -Xdebug... " instead of "java -XDebug ... Test". Wrong order in the command line. Now I see that the JVM listens!
I was following this simple guide on installing Mesos locally https://mesosphere.com/2014/07/07/installing-mesos-on-your-mac-with-homebrew/
I was able to start a mesos master and was able to see the master's console perfectly fine at localhost:5050. However when I tried to start a new slave using sudo /usr/local/sbin/mesos-slave --master=127.0.0.1:5050 , it gave me
WARNING: Logging before InitGoogleLogging() is written to STDERR
F0328 16:14:45.329051 2041414416 process.cpp:889] nodename nor servname provided, or not known
* Check failure stack trace: *
Any help will be appreciated, thanks
This can also happen if you working on a Framework and attempting to connect to a Mesos Master. Mesos is attempting to resolve your computer's name via DNS and isn't finding an entry. This can happen if you've changed your Mac's hostname post setup ( as I did, and had this same error ).
To fix, run hostname -f, that will will give you the value of what OS/X thinks it's name is. Then simply ensure you've got 127.0.0.1 VALUE_OF_HOSTNAME_-F in your /etc/hosts file.
I have RabbitMQ installed on a CentOS 5.x server which I use for message passing between my programs. I've installed rabbitmqadmin following the directions on https://www.rabbitmq.com/management-cli.html and have used it on my servers in the past.
From what I can tell it looks like this particular server is misconfigured. My web-searches have failed me on trying to get more information on how to troubleshoot this issue.
The error:
[root#server ~]# python26 /usr/local/bin/rabbitmqadmin list nodes
*** Could not connect: [Errno -2] Name or service not known
[root#server ~]#
I have tried several different rabbitmqadmin commands and they give the same result. If I run the command without the extra params it displays the normal help dialog. I have this setup and working on several other servers.
Any idea on what the root issue is? If not, anyway to get more details, like verbose?
Update:
I just tried to check the version of rabbitmq and its yielding an error too:
[root#server ~]# rabbitmqctl status
Status of node rabbit#server ...
Error: unable to connect to node rabbit#server: nodedown
DIAGNOSTICS
===========
attempted to contact: [rabbit#server]
rabbit#server:
* connected to epmd (port 4369) on server
* epmd reports node 'rabbit' running on port 25672
* TCP connection succeeded but Erlang distribution failed
* suggestion: hostname mismatch?
* suggestion: is the cookie set correctly?
current node details:
- node name: rabbitmqctl25451#server
- home dir: /var/lib/rabbitmq
- cookie hash: WXaeZT7XXm13naagfRX5cg==
[root#server ~]#
I'm going to see if I can find something from this... I find this weird because the server is passing messages fine and can be monitored through the web console.
Erlang version:
[root#server rabbitmq]# erl -eval 'erlang:display(erlang:system_info(otp_release)), halt().' -noshell
"R14B04"
[root#server rabbitmq]#
Rabbitmq Version:
[root#server rabbitmq]# python26 /usr/local/bin/rabbitmqadmin --version
rabbitmqadmin 3.3.5
[root#server rabbitmq]#
After much digging and frustration, I found my problem... I'm posting the solution in case anyone else has a similar experience
Previously, I found that if you setup RabbitMQ on a linux server then change the hostname that it can break some of the rabbit configuration.
The awesome part about this problem is that someone changed the name of the server from all capital letters to lowercase...
I've solve this one of two ways:
Solution 1:
Revert the host name back to the previous name. So that rabbitmq references with the appended server name work again.
Solution 2:
If you want to keep the server name change, then you can create a rabbitmq-env.conf files in /etc/rabbitmq like:
NODENAME=rabbit#OLDHOSTNAME
If you aren't sure what your previous name was, you can reference it by doing an ls in your /var/lib/rabbitmq/mnesia/ folder. You'll then see a folder that matches the nodename you need to specify.
Reference: https://www.rabbitmq.com/man/rabbitmq-env.conf.5.man.html
UPDATE:
Host name is CaSE SeNSiTIve... had someone change a hostname on me and the only difference was the case... so took a while to notice...
Yesterday I've lost a few hours with this same problem and it was in a fresh install, so the problem was that the erlang cookie from my user and root user was different than the one from rabbitmq user.
Find out the HOME for the user rabbitmq:
# cat /etc/passwd | grep rabbitmq
Check if the cookies differs from each other:
# vimdiff /var/lib/rabbitmq/.erlang.cookie ~/.erlang.cookie
If they are different, copy the cookie from rabbitmq for the user that you want to have access to the server:
# cp /var/lib/rabbitmq/.erlang.cookie ~/.erlang.cookie
References:
rabbitmqctl status says "TCP connection succeeded but Erlang distribution failed"
How Nodes (and CLI tools) Authenticate to Each Other: the Erlang Cookie