My purpose is to download nagios for business purpose. I started a Linux machine(Centos 7) but could not install packages. Then I concluded that it is because of a network problem
I tried the following troubleshooting steps
ping ip-addr
ping google.com
It shows Network unreachable
but ping 127.0.0.1 works
What may be the problem
I think you have not setup your network card with a proper outgoing connection.
Try following this tutorial Centos Network Setup to get you going ...
Yes I tried to follow the steps mentioned in the manual. But after edit connection when
I give the followimng command service network restart. It shows the following error
Job for network.service failed as the control process failed with the error code
systemctl restart network shows the same too
Related
So I got to know about Azure and I want to run a nodejs file in VM. I know the steps on how to deploy the nodejs in Digital Ocean, and It worked fine. I tried to follow the same steps but seems like there were some issues while pulling images from docker.
I followed this tutorial in order to install docker in my VM. But it seems like there is an issue:
Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
on running sudo docker pull hello-world
while the same error is occuring on docker-compose
(This is just an example, I want to run docker-compose but It gave the same error)
I tried running all the solutions that I found but all didn't help. Is there anyone else who has created a vm in azure and came across this issue and fixed it?
I found about 5-6 links with the same question but none of the answers fixed my problem :(
I created a Linux VM with the help of this tutorial
Look for the image on hub.docker.com and make sure that you pass a correct name of the image. The article is from 2018 so it could be out dated.
Below are the steps I followed:
Access Linux server using putty from Windows 7
Run docker run -d -P -p 4545:4444 --name standalone_grid selenium/standalone-chrome on Linux
Launch chrome browser on windows and try to access
http://<linux_server_ip>:4545. Error site can't be reached. This server also has Jenkins installed which can be accessed at http://<linux_server_ip>:8080
How can I fix this? Am I doing anything wrong?
docker ps out put
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
60422c2cd9b1 selenium/standalone-chrome "/opt/bin/entry_poin…" About an hour ago Up About an hour 0.0.0.0:4545->4444/tcp standalone_grid
As mentioned in the comments first thing you want to check if the container is up:
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b7a560331584 selenium/standalone-chrome "/opt/bin/entry_poin…" 2 minutes ago Up 2 minutes 0.0.0.0:4545->4444/tcp standalone_grid
Next step would be just to verify locally is it working from the Linux console:
curl http://<linux_server_ip>:4545
If this works you already know it is a networking issue. Please check your local iptables rules:
sudo iptables -L INPUT
to see if there are any restrictions for incoming connections. If this is empty the the issue lays in connectivity within the network itself. You can try to workaround it by using a Putty ssh tunnel.
EDIT:
The issue was related to port 4545, using a different port resolved the problem.
I'm new to Docker so please be kind but I am testing it out on a Windows 10 image on Azure (I know I could run it directly but I wanted to try it in a VM first).
I have a fresh Windows 10 image that I have installed Docker for Windows 2.0.0 on.
Note: I did not tick the option to use Windows containers instead of linux containers.
Once it installed (and rebooted) I was prompted to install Hyper-V and Containers features (causing restarts).
Once it was all installed I open an Administrative PowerShell window to download Jenkins:
docker run -p 8080:8080 -p 50000:50000 -v jenkins_home:/var/jenkins_home jenkins/jenkins:lts
This gave me the error:
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: driver failed programming external connectivity on endpoint goofy_lederberg (deaba2deeea0486c92ba8a1a32740295f03859b1b5829d39e39eff0b24613ebf): Error starting userland proxy: Bind for 0.0.0.0:50000: unexpected error Permission denied.
I thought this was strange as 50000 wasn't a port that I expected to be in use, changing this to different ports (50001) produced the same error.
Running:
netstat -a -n -o
Showed that the port was not in use.
If I remove -p 50000:50000 from the command it can bind and start Jenkins but I assume it needs this port mapping to work correctly.
Previous posts have suggested stopping the World Wide Web Publishing service but that isn't installed.
There are no other running Docker containers.
I assume the port is in use or something is stopping the port mapping.
Assuming a user has permission to create a port binding from their terminal are there any other techniques beside netstat to determine if something is bound to a port - either something internal to docker's own checking process or something at the host OS level?
Rather embarrassingly this worked this morning with no changes other than the VM was shutdown over the weekend.
Maybe all it needed was a reboot?
I'm new to Grails and attempting to implement the Hello World app described at grails.org's Getting Started guide.
I have installed Grails using SDKman on an Ubuntu Server 16.04 VM (VirtualBox, running as a service). My host machine is Windows 10.
I configured two network adapters in VirtualBox: the first a NAT with port forwarding (3022 host -> 22 guest, 8080 host -> 8080 guest), the second a Host-Only adapter.
I can SSH into my VM just fine from my Windows host (using Bash): ssh -p 3022 user#localhost
When I run python3 -m http.server 8080 from that SSH session, it successfully listens on both localhost:8080 and :8080. I can access both URLs from a browser on my host machine.
When I run grails run-app it hangs forever, and none of the above endpoints work from my host.
When I run grails run-app --verbose I see it compile without complaint through "Building 85% > :bootRun". I understand that this is expected behavior, but I never see "Application started" or any similar message. It never starts.
ONE TIME the following command succeeded in building and running the app, creating exactly the result I needed:
grails -Dserver.port=8080 -Dserver.host=0.0.0.0 run-app --verbose --stacktrace
However when I stopped the app and tried again, it failed as before.
I notice that VirtualBox > Settings > Network > Adapter #2 which I had set as "Host-Only Network" has multiple times reset itself to Bridged. I suspect that this reset may have caused my problem. But I don't know how to prevent the reset, or to restore that functionality I so briefly had.
Thanks, anyone who can help!
Resolved! Turns out run-app just takes a LONG time to finish compiling and building, upwards of 10 minutes. So I just needed to wait ~5+ minutes with no visual sign of action before the completion message would show and I could access my site. :)
Today I installed Kong (API Management Layer) on my Mac OS X (Yosemite 10.10.5). I used the .pkg file which is available here. I followed the installation instructions and everything was successful.
I also installed Cassandra using the information given on the Cassandra home page.
But when I start Kong, using the command:
$ kong start
It throws the following error:
dnsmasq: failed to create listening socket for fe80::3e15:XXXX:XXXX%en0: Can't assign requested address
Looks like you have already something running on the kong port 8000,8001 or 9042. Try to shut down anything that might be using those ports and retry?
you can configure Kong to run on any custom ports for (proxy and admin) by changing the values in the /etc/kong/kong.yml file. see full config reference here
The problem is that dnsmasq on Kong is listening by default on port 8053 (https://github.com/Mashape/kong/blob/master/kong.yml#L29), which seems to be already taken on your system.
Make sure that there is nothing else running on that port.
You can kill the process that is running on the dnsmasq port and restart the kong.
Kill the process:
sudo kill `sudo lsof -t -i:8053`
Start Kong:
kong start
/usr/local/bin/kong start
/usr/local/bin/kong stop
/usr/local/bin/kong reload
/usr/local/bin/kong status