start minishift with --memory and troubleshooting
by Claudio Miranda
Hi, I recently started use minishift and have a couple o questions:
1) Does the "minishift start --memory" parameter only work for the
first time minishift starts (that is when it creates the image
locally) ? I tried to set it after the first start but the memory is
not set. However I was able to change the memory by using virsh
command "sudo virsh edit minishift "
2) I followed the radanalytics tutorial [1], but somehow there is an
error somewhere in spark [2] I am unable to trace it. Can you provide
some commands or places to look at to investigate the problem ? When
this problem occur "minishift status" reports the cluster is not
running
3) When I increased the memory to 8G the error reported on [2] is
gone, but a http request results in a "504 Gateway Time-out"
$ curl http://vertx-sparkpi-myproject.192.168.42.247.nip.io/sparkpi
<html><body><h1>504 Gateway Time-out</h1>
The server didn't respond in time.
</body></html>
and the dc/vertx-sparkpi reports a "ERROR ConnectionBase:
java.io.IOException: Connection reset by peer"
I increased the memory to 8GB, for experimentation, because I couldn't
see anywhere a error saying there was not enough memory to run the
pods, but I would like to troubleshoot it.
I tried to run oc logs on all pods, but there were no errors.
My system is a fedora 28
1. https://radanalytics.io/my-first-radanalytics-app.html
2. https://gist.github.com/claudio4j/6b0251f3014bdf645574c360641cf49c
Thanks
--
Claudio Miranda <claudio(a)redhat.com>
Senior Software Engineer - Wildfly
4 years, 10 months
trying to use minishift
by kadamkailas＠gmail.com
Hi,
I have downloaded the minishift 1.21.0-darwin-amd64]# and trying to use it but it throws error as below while starting it
please assist me here
[root@localhost minishift-1.21.0-darwin-amd64]# ./minishift start
-bash: ./minishift: cannot execute binary file
[root@localhost minishift-1.21.0-darwin-amd64]#
4 years, 10 months
[openshift-sme]Diff mapping methods of *IdentityProviders*
by Kamesh Sampath
I was playing minishift to update the identity provider via `minishift
openshift config set —patch` command, when I execute the following
patch command
```minishift openshift config set --patch='{"oauthConfig":
{"identityProviders": [ {"challenge": "true","login":
"true","mappingMethod": "claim","name": "htpasswd","provider":
{"apiVersion": "v1","kind": "HTPasswdPasswordIdentityProvider","file":
"users.htpasswd"}}]}}'
```
It fails.
But when I run the following command:
```minishift openshift config set --patch='{"oauthConfig":
{"identityProviders": [ {"challenge": "true","login":
"true","mappingMethod": “add”,”name": "htpasswd","provider":
{"apiVersion": "v1","kind": "HTPasswdPasswordIdentityProvider","file":
"users.htpasswd"}}]}}'```
The patching was successful. The only difference between the two
commands is the **mappingMethod**.
Can experts please explain
1. Why this behaviour ?
2. What are the various mappingMethods available ?
3. When to use what ?
NOTE: there was a Minishift issue [1] raised with inability to patch
using `absolute` path for the `file` attribute., I guess we are allowed
to specify absolute path in the file property of
HTPasswdPasswordIdentityProvider.
[1] https://github.com/minishift/minishift/issues/2569
Thank you.
4 years, 11 months
minishift error under windows 8
by Bo Qiang
Hi,
Here is my configurations
Windows 8
virtualbox 5.2.14
minishift-1.20.0-windows-amd64
<https://github.com/minishift/minishift/releases/download/v1.20.0/minishif...>
Here are the messages I got when I tried to start minishift:
> minishift start --vm-driver virtualbox
-- Starting profile 'minishift'
-- Check if deprecated options are used ... OK
-- Checking if https://github.com is reachable ... OK
-- Checking if requested OpenShift version 'v3.9.0' is valid ... OK
-- Checking if requested OpenShift version 'v3.9.0' is supported ... OK
-- Checking if requested hypervisor 'virtualbox' is supported on this
platform ... OK
-- Checking if VirtualBox is installed ... OK
-- Checking the ISO URL ... OK
-- Checking if provided oc flags are supported ... OK
-- Starting local OpenShift cluster using 'virtualbox' hypervisor ...
-- Starting Minishift VM
...................................................... FAIL E0708
00:03:28.368248 7292 start.go:414] Error starting the VM: Error starting
stopped host: Too many retries waiting for SSH to be available. Last
error: Maximum number of retries (60) exceeded. Retrying.
Error starting the VM: Error starting stopped host: Too many retries
waiting for SSH to be available. Last error: Maximum number of retries
(60) exceeded
It seems the VM is running but for some reasons not accessible. Any ways to
fix this? Thanks!
4 years, 11 months
