When I am trying to install the EMC Atmos Evaluation Edition on an ESX host, I get the following error message
No MDS is Master [Fatal]
when I run the command
./mds-shutdown.pl --shutdown --RMG
on the first VM AEE-r1s1-001.
Any ideas on what is going wrong here?
Related
Repost from user Jin G.
After going through the Flow installation tutorial I tried to run the sumo demo example using the following terminal command:
python examples/sumo/sugiyama.py
I got the following error message: Could not connect to TraCI server at localhost: 40335 [Errno 111] Connection refused
Any thoughts on what to do to fix this issue?
After days of retrying and searching I found a fix..
My issue was that I did not activate the conda environment when running the simulations.
To do so before running any simulations type the following into the command prompt:
source activate flow
I'm "extremely" new to Kubernetes, and I wanted to try it out on my local machine, which is running Windows 10 along with HyperV. I saw that minikube is used for local development, and I was able to find in on Chocolatey, so I installed it using that:
choco install minikube -y
(I think this also installs kubectl)
The problem I have is that I'm not able to start it; I'm running the following command:
minikube start --vm-driver=hyperv
I have an external switch configured in HyperV (I found it as a suggestion somewhere), but when I run the command, it's stuck in Creating VM ...
I thought maybe it would give me a clue if I look at the VM created in HyperV, and when I open that, I see the following:
So, it seems that it's waiting for input, and that's why it's stuck! I tried searching for the problem, but to no avail.
I would appreciate any help
PS: It seems to me that if I wait long enough, the following message appears on the console:
Temporary Error: provisioning: error getting ssh client: Error dialing
tcp via ssh client: ssh: handshake failed: ssh: unable to authenticate,
attempted methods [none publickey], no supported methods remain
So, somehow by chance, I think I found how to resolve the issue.
First thing is that: the fact the VM is displaying that prompt (minikube login) seems to be normal, and it does NOT prevent the minikube start from succeeding.
To resolve the issue, this is what I did:
Delete ~/.kube directory
Delete ~/.minikube directory (in case it exists)
The MOST IMPORTANT step: stop/start the Hyper-V Virtual Machine Management Windows service
These steps seem to have solved the issue for me
PS: I used this command to start minikube and enable verbose logging:
minikube start --vm-driver hyperv -v 7 --alsologtostderr
Farzad, what resources have you used for setting up the minikube? Can you please clarify what do you mean by "unable to start". Are the regular kubectl commands working?
For example kubectl get nodes? That is of course if below steps won't help you.
The screenshot you shared shows a running VM:
Minikube runs a single-node Kubernetes cluster inside a VM on your
laptop for users looking to try out Kubernetes or develop with it
day-to-day.
You mentioned that you've created the vSwitch, you should be using a flag that is pointing minikube to use that external vSwitch:
minikube start --vm-driver hyperv --hyperv-virtual-switch "vSwitch name"
You also mentioned choco, did you install kubernetes-cli (as you did not mention it in the question)? It might be the reason why your commands do not work (seems like the new version downloads kubectl with choco install minikube):
kubectl is a command line interface for running commands against
Kubernetes clusters
At this moment I recommend stoping the minikube VM:
minikub stop
Delete the cluster
minikube delete
Sometimes regular minikube stop, minikube delete does not work so you might have to manually turn off the minikubeVM in Hyper-V, then I recommend to go to c:\users\%username%\ and delete .kube and .minikube.
Use cuninst minikube
Restart and install again as specified in the minikube documentation:
choco install minikube
choco install kubernetes-cli
As for the error you mentioned, let's try to run the cluster properly, and if this persists, we will take care of it.
Try this:
kubectl config use-context minikube
I encountered the same issue. The reason was I chose the wrong disk file to start my VM after creating it in Virtual Box.
This solved my issue.
minikube delete
minikube start --vm-driver hyperv -v 7 --alsologtostderr
When I type "mfp start" in the terminal, this is what I get:
Initializing MobileFirst Console. objc[64598]: Class JavaLaunchHelper
is implemented in both
/Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/bin/java
(0x1075964c0) and
/Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre/lib/libinstrument.dylib
(0x1076904e0). One of the two will be used. Which one is undefined.
Starting server worklight. Server worklight start failed. Check server
logs for details.
Error: The server failed to start. The port may be in use by another instance of a running server, or the server may not exist.
when I type "mfp push" into the terminal, this is what I get:
Preparing for push... Verifying Server Configuration...
Runtime 'DoorbellIOSNative' will be used to push the project into.
Error: JAVA_HOME environment variable must be set and pointing to a Java Development Kit (JDK). See 'mobilefirst help build'. Error: error
code: 304 Error: There was an error building the application. Error:
undefined Error: Push has failed
How do I fix these issues and errors? I have tried uninstalling and reinstalling the CLI and I also have updated my java version to the latest version. I have also typed "mfp stop" in the terminal and typed in "mfp start" again but still got the same error.
Verify you do not have an already running server or something else is listening to the same port. Another thing you might want to check is the /etc/hosts file contains the right IP address for the localhost.
Double check to make sure your JAVA_HOME is set to the JDK, not JRE. Based on your first error, it should be:
/Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home
This query is regarding IBM MobileFirst CLI 6.3.0 Version. While running the deploy command We are getting error as below. Unable to figure out the root cause for the same. Please help
BUILD FAILED
/opt/ibm/MobileFirst-CLI/mobilefirst-cli/node_modules/generator-worklight-server/lib/build.xml:403:
Element inside , attribute
'warFile' is invalid for use with : It
does not end with '.war':
/users/wasadm/.ibm/mobilefirst/6.3.0/server/wlp/usr/servers/worklight/apps/.nfs0000000033c12d6600000221
Total time: 0 secondsError: Build process failed. Please check the
stack above for details.
Starting server worklight. Server worklight start failed. Check server
logs for details.
/users/wasadm/.ibm/mobilefirst/6.3.0/server/wlp/bin/server: line 744:
22493 Aborted (core dumped) "${JAVA_CMD}" "$#" >
"${JAVA_CMD_LOG}" 2>&1 Error: The MobileFirst server failed to start.
The port may be in use by another instance of a running server, or the
server may not exist. "
It sounds to me like you are failing because, as the error message says, the port is already occupied.
Make sure Eclipse is not running.
Also try killing the Java process and then try to start the server from the command line.
See here for more: IBM Mobilefirst CLI - Server start issue
I'm following these steps outlines on this link, however when I try to start the server nothing happens nor can I connect to anything from the client. Does anyone know how to run this?
when I try from a command prompt instead of double clicking the redis-server.exe I get this message
[11868] 23 Jul 11:58:26.325 # QForkMasterInit: system error caught. error code=0
x000005af, message=VirtualAllocEx failed.: unknown error
http://bartwullems.blogspot.ca/2013/07/unofficial-redis-for-windows.html
The easiest way to install Redis is through NuGet:
Open Visual Studio
Create an empty solution so that NuGet knows where to put the packages
Go the Package Manager Console: Tools –> Library Package Manager –>Package Manager Console
Type Install-Package Redis-64
image
Go to the Packages folder and browse to the Tools folder. Here you’ll find the Redis-server.exe. Double click on it to start it.
Redis is ready to use and start’s listening on a specific port(6379 in
my case)
image
Let’s open up a client and try to put a value into Redis. Start Redis-cli.exe. It already connects to the same port by default.
image
Add a value by executing following command:
image
Read the value again:
image
Try to run with redis-server --maxheap 4000000
Miguel is correct, but it is not that simple. To start redis-server either as a service or from the command prompt, the amount of available RAM and disk space must be sufficient for Redis to run as configured.
Now, if no configuration file is specified when running Redis, it will use the default configuration values. All of this is documented in the redis.windows.conf file as well as in the document "Redis on Windows.docx" (both deployed with the redis installation).
In my experience, errors when starting Redis usually come from lack of available resources (RAM or disk space) or some incorrect configuration of maxhead or maxmemory parameters.
To troubleshoot this kind of behavior, check your system's available resources and try running redis-server from the command line varying the parameters maxmemory, maxheap, and/or heapdir. The loglevel parameter set to verbose might also help diagnosing the issue.
Regards