minishift: Unable to start minishift; connection to target machine actively refused
I just start the minishift and getting this issue , Please suggest.
PS C:\Users\mukul\minishift-1.7.0-windows-amd64\minishift-1.7.0-windows-amd64> .\minishift.exe start
-- Checking if Hyper-V driver is installed ... OK
-- Checking if Hyper-V driver is configured to use a Virtual Switch ... OK
-- Checking if user is a member of the Hyper-V Administrators group ... OK
-- Starting local OpenShift cluster using 'hyperv' hypervisor ...
-- Minishift VM will be configured with ...
Memory: 2 GB
vCPUs : 2
Disk size: 20 GB
-- Starting Minishift VM ................................................................................................ OK
-- Checking for IP address ... OK
-- Checking if external host is reachable from the Minishift VM ...
Pinging 8.8.8.8 ... OK
-- Checking HTTP connectivity from the VM ...
Retrieving http://minishift.io/index.html ... OK
-- Checking if persistent storage volume is mounted ... OK
-- Checking available disk space ... 0% used OK
-- OpenShift cluster will be configured with ...
Version: v3.6.0
-- Checking oc support for startup flags ...
routing-suffix ... OK
host-config-dir ... OK
host-data-dir ... OK
host-pv-dir ... OK
host-volumes-dir ... OK
Starting OpenShift using openshift/origin:v3.6.0 ...
Pulling image openshift/origin:v3.6.0
Pulled 1/4 layers, 26% complete
Pulled 1/4 layers, 56% complete
Pulled 2/4 layers, 81% complete
Pulled 3/4 layers, 87% complete
Pulled 4/4 layers, 100% complete
Extracting
Image pull complete
-- Checking OpenShift client ... OK
-- Checking Docker client ... OK
-- Checking Docker version ... OK
-- Checking for existing OpenShift container ... OK
-- Checking for openshift/origin:v3.6.0 image ...
Pulling image openshift/origin:v3.6.0
Pulled 1/4 layers, 26% complete
Pulled 1/4 layers, 56% complete
Pulled 2/4 layers, 81% complete
Pulled 3/4 layers, 87% complete
Pulled 4/4 layers, 100% complete
Extracting
Image pull complete
-- Checking Docker daemon configuration ... OK
-- Checking for available ports ... OK
-- Checking type of volume mount ...
Using Docker shared volumes for OpenShift volumes
-- Creating host directories ... OK
-- Finding server IP ...
Using 192.168.0.20 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://192.168.0.20:8443/healthz/ready
Details:
No log available from "origin" container
Caused By:
Error: Get https://192.168.0.20:8443/healthz/ready: dial tcp 192.168.0.20:8443: connectex: No connection could be made because the target machine actively refused it.
Error during 'cluster up' execution: Error starting the cluster.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 57 (32 by maintainers)
@helio-frota Reported as: https://github.com/openshift/origin/issues/17461
@helio-frota wasn’t aware of this. Thanks for the feedback. Will have a look at this.
@helio-frota you experienced #343, and related issues when IP changes: #1508, … What happens is that the SSL/TLS certificate created for OpenShift cannot be used as it was generated for a different IP address. We would like to be able to update this information, with something like with #1515, but so far this has proved to be difficult.