network unreachable

[Toerktumlare]

I don't know if this is an issue or not

i pulled the Vagrant image and started it. Was able to login and start a project. But when trying to pull an image from docker hub i get network unrachable.

I have tried setting http_proxy in the vagrant and if i ssh into the machine i can pull and push images with docker inside the openshift-vagrant. But when using the openshift gui i cannot pull images.

i have tried setting the http_proxy in the docker-opts /etc/sysconfig/docker without any luck.

is this a known issue?

[stevekuznetsov]

I can't seem to reach that host from my machine -- can you ping it from inside the VM? How are you starting OpenShift? I suggest if possible doing a containerized start with oc cluster up.

[Toerktumlare]

i pulled the vagrant image and did a
vagrant up
then i accessed the gui at
localhost:8443
and logged in. and then i get that screenshot above

Then i sshd into the machine and did a oc cluster down and then tried to start the cluster with oc cluster up i then get an error saying that ports are still in use

-- Checking OpenShift client ... OK
-- Checking Docker client ... OK
-- Checking Docker version ... OK
-- Checking for existing OpenShift container ... OK
-- Checking for openshift/origin:v1.3.0 image ... OK
-- Checking Docker daemon configuration ... OK
-- Checking for available ports ... FAIL
   Error: a port needed by OpenShift is not available
   Caused By:
     Error: ports in use: [80 443 4001 7001 8443 10250 53]

the cluster doesn't seem to go down

[stevekuznetsov]

Ah, the pre-installed cluster is not created using oc cluster up -- you'll need to:

$ sudo systemctl stop openshift
$ oc cluster up

The systemctl unit name might be origin, not openshift -- I can't remember off the top of my head right now.

[Toerktumlare]

stopped the service with

$ sudo systemctl stop origin
$ oc cluster up
-- Checking OpenShift client ... OK
-- Checking Docker client ... OK
-- Checking Docker version ... OK
-- Checking for existing OpenShift container ... OK
-- Checking for openshift/origin:v1.3.0 image ... OK
-- Checking Docker daemon configuration ... OK
-- Checking for available ports ... FAIL
Error: a port needed by OpenShift is not available
Error: ports in use: [80 443]

so apparently some http-service is not going down when i stop the service.
i can start the service again with:

$ sudo systemctl start openshift

and i can login to the gui but i still have the same problem, can't pull images from docker.hub with the gui

[stevekuznetsov]

Can you figure out if there is some rogue process still going?

sudo systemctl stop openshift
ps -ef | grep -e openshift -e origin
lsof -i :80
lsof -i :443

[Toerktumlare]

destroyed the vagrant, started it again. took down the service with:

sudo systemctl stop origin

started cluster with

[vagrant@localhost ~]$ oc cluster up
-- Checking OpenShift client ... OK
-- Checking Docker client ... OK
-- Checking Docker version ... OK
-- Checking for existing OpenShift container ... OK
-- Checking for openshift/origin:v1.3.0 image ... OK
-- Checking Docker daemon configuration ... OK
-- Checking for available ports ... OK
-- Checking type of volume mount ...
   Using nsenter mounter for OpenShift volumes
-- Creating host directories ... OK
-- Finding server IP ...
   Using 10.0.2.15 as the server IP
-- Starting OpenShift container ...
   Creating initial OpenShift configuration
   Starting OpenShift using container 'origin'
   Waiting for API server to start listening
FAIL
   Error: cannot access master readiness URL https://10.0.2.15:8443/healthz/ready
   Details:
     Last 10 lines of "origin" container log:
     I0118 13:36:34.697420   15833 ensure.go:209] Created default security context constraint restricted
     I0118 13:36:34.701958   15833 ensure.go:209] Created default security context constraint anyuid
     I0118 13:36:34.707975   15833 ensure.go:209] Created default security context constraint hostnetwork
     I0118 13:36:35.544447   15833 trace.go:61] Trace "Create /oapi/v1/namespaces/default/rolebindings" (started 2017-01-18 13:36:34.711919024 +0000 UTC):
     [11.305µs] [11.305µs] About to convert to expected version
     [35.204µs] [23.899µs] Conversion done
     [819.153245ms] [819.118041ms] About to store object in database
     [832.408942ms] [13.255697ms] Object stored in database
     [832.417261ms] [8.319µs] Self-link added
     [832.483773ms] [66.512µs] END

[stevekuznetsov]

@csrwng could you help a little with oc cluster up failures?

[csrwng]

Make sure that the firewall allows access to port 8443. Also after cluster up fails, can you try curl'ing that URL and see why it's not accessible ? Is the container (origin) still running?

[naveenkumartangallapally]

hi csrwng ,
i am also facing the same issue.not able to do oc cluster up.
[root@master ~]# oc cluster up
-- Checking OpenShift client ... OK
-- Checking Docker client ... OK
-- Checking Docker version ... OK
-- Checking for existing OpenShift container ... OK
-- Checking for registry.access.redhat.com/openshift3/ose:v3.4.1.10 image ... OK
-- Checking Docker daemon configuration ... OK
-- Checking for available ports ... FAIL
Error: a port needed by OpenShift is not available
Caused By:
Error: ports in use: [10250]

and we have stopped origin and dns service also,but getting same error

[csrwng]

@naveenkumartangallapally try running sudo netstat -tnlp to see what process is using port 10250.

[naveenkumartangallapally]

i got below o/p

[root@master ~]# netstat -tnlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:2380 0.0.0.0:* LISTEN 1362/etcd
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1/systemd
tcp 0 0 0.0.0.0:20048 0.0.0.0:* LISTEN 1386/rpc.mountd
tcp 0 0 0.0.0.0:8053 0.0.0.0:* LISTEN 29970/openshift
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1869/sshd
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2557/master
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 29970/openshift
tcp 0 0 0.0.0.0:59261 0.0.0.0:* LISTEN 1373/rpc.statd
tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN -
tcp 0 0 192.168.57.90:2379 0.0.0.0:* LISTEN 1362/etcd
tcp6 0 0 :::111 :::* LISTEN 1/systemd
tcp6 0 0 :::20048 :::* LISTEN 1386/rpc.mountd
tcp6 0 0 :::22 :::* LISTEN 1869/sshd
tcp6 0 0 ::1:25 :::* LISTEN 2557/master
tcp6 0 0 :::2049 :::* LISTEN -
tcp6 0 0 :::9090 :::* LISTEN 1/systemd
tcp6 0 0 :::10250 :::* LISTEN 29031/openshift
tcp6 0 0 :::48714 :::* LISTEN 1373/rpc.statd
[root@master ~]#

[csrwng]

so it looks like you're running openshift (pid 29031) ... which is causing a conflict

[naveenkumartangallapally]

can u help me to fix the issue plz

[csrwng]

kill existing openshift related processes:
killall openshift or
kill 29031 29970

and then run oc cluster up

[csrwng]

or systemctl stop openshift