Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I installed Jenkins yesterday (together with apache2). Jenkins started fine and everything was ok. Then I decided to stop jenkins and apache because I planned to configure them today. Now when I start Jenkins i get this error:
Jenkins startup error
I have tried some other Ports like 8081 or 4xxxx, nothing helped.
How can i fix this? Please help.
System:
Debian 6.0
Installation of Jenkins through the offical repo.
Apache has no vhosts except the 000-default
netstat shows nothing on 8080 or the 4xxxx Port
The problem is quite easy to pin:
Caused by: java.net.BindException: Address already in use
This means that for the given address:port there is already a process which is binding to it. Please, use the operating system tools to find this process and, eventually, kill it. Then start Jenkins again.
Additionally, I can add, that it almost certainly Jenkins, which was not stopped correctly or, due to some error, did not stopped entirely.
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 months ago.
Improve this question
I can't get Docker to start on my Mac (Intel). It's just stuck in Docker Desktop starting...
Here are the things I have tried:
Running with the desktop installer
Running with the brew installer (brew install --cask docker)
In the debug menu:
Clean /Purge data
Reset to factory defaults
Trying to run docker ps in terminal shows:
Error response from daemon: dial unix docker.raw.sock: connect: no such file or directory
If I quit docker, the com.docker.vmnetd process needs to be killed manually.
This problem started around version 4.5.0 Now I am on version 4.12.0., and still the same issue. If I downgrade to a version far back (with the previous UI), it works. But after a while, Docker forces itself to update, which puts me back in this same problem.
Does anyone have any clue what I can try?
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I have a two part question:
first is that can anyone please tell me the command lines to execute in docker to start building a container and vm?
second is i have already built a VM using docker but the problem is whenever the building of VM reaches the stage where it written WAITING FOR VM TO BOOT it's stuck there and the error of HYPERVISOR IS NOT RUNNING comes even when the HYPER-V MACHINE MANAGEMENT is on automatic and running.
So please, help me get rid of this problem.
To create a VM which will run docker, use docker-machine: copy docker-machine-Windows-x86_64.exe as docker-machine.exe anywhere you want.
docker-machine create -d virtualbox
docker-machine start
But Make sure you have removed the Windows feature HyperV, as it is not compatible with VirtualBox/VMWare.
Or use the Hyper-V driver. You have to chose one or the other.
See "Getting Docker running on Windows 10"
as it turns out, HyperV and VirtualBox will not run together side-by-side in 64 bit modes. And Scott's blog post about rebooting to a hypervisorlaunchtype off mode of Windows 8.1 worked flawlessly for Windows 10.
So I didn't have to un-install the HyperV feature, but as it turns out, I did have to disable HyperV
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
i am running CoreOS inside vagrant and want to use docker in this way, after i shut down vagrant, i changed the vm name to be shorter one, then i run vagrant up, firstly, i found authentication failure problem:
then i press Ctrl+C to interrupt it, then i run vagrant ssh in the folder, this time, the system ask me for password.
but i have never set such a password, so what is the default passord for CoreOS? or how can i login to this OS which is running inside vagrant?
btw, the image of coreos is downloaded from http://beta.release.core-os.net/amd64-usr/
some people said the reason system ask for password is the the authentication of public key fails, but why it fails?
vagrant ssh-keys shows:
now i cannot login to coreos even from vbox gui:
some debug message of vagrant up:
Edit 1
seems this problem have something to do with the ssh key, but why the default ssh key failed? and how to solve this problem now?
There is no password authentication available for CoreOS, you must use either the default ssh key as specified in the documentation, or equip a cloud config file with a new key.
Quote from the docs: CoreOS Vagrant Docs
You can provide cloud-config data to your CoreOS Vagrant VM by editing the user-data file inside of the cloned directory.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have a server with centos running rails application each time when I reboot my system I have doing following tasks manually. How to enable all the following tasks in start up
To stop and start my nginx I am using
sudo fuser -k 80/tcp # to stop
sudo /opt/nginx/sbin/nginx # to start
And to start my postgresql I am using following command
service postgresql-9.2 start/stop/restart
Once I connect my server using ssh and try some postgresql command ill get error as
postgresql-9.2: unrecognized service
To avoid this am using command
export PATH=/usr/pgsql-9.2/bin:$PATH
And then ill use postgresql(Doing export command each time when I connect through ssh).
And I am using ghost blog facing same issue whenever I reboot my server I need to run following command to start my ghost blog
NODE_ENV=production forever start index.js
How to solve all these. Can any one help
You can add the process in your init script that is at /etc/init.d/
.You can further read run script on startup
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
When I launch it with sudo /etc/init.d/dse start it seems to work. It returns:
Starting DSE daemon dse
DSE daemon starting with Hadoop and Solr disabled (edit /etc/default/dse to enable)
But when I try to connect to the tutorial "Test Cluster" (so localhost) with opscenter (on a distant machine but with port 8888 shared), I got this error:
Error creating cluster: Unable to connect to cluster
And if I check the health of dse with sudo /etc/init.d/dse status: I got:
dse dead but pid file exists
Original post:
The console or /var/log/cassandra/output.log will likely contain something like this (where nodename1 is whatever you named your node):
Error: Exception thrown by the agent : java.net.MalformedURLException: Local host name unknown: java.net.UnknownHostException: nodename1: nodename1
Same as problem on starting cassandra, basically you need to make sure that the hostname you are using can be resolved (by putting it into /etc/hosts).