IBM BlueMix provides a beta version of Virtual machines service, I am unable to provision any virtual machine, and every time I get the following error:
Your VM is in error - Build of instance 369779a3-b3da-4e0c-9958-491044797e9d aborted: Failed to allocate the network(s), not rescheduling.
I get this error using IBM BlueMix portal or even using BlueMix API.
If I tried to restart the VM, I get the following error:
Cannot 'reboot' instance 369779a3-b3da-4e0c-9958-491044797e9d while it is in task_state spawning
So, I think that there is an error regarding openstack they are using in their datacenters !!
Please do note that this issue raised in United Kingdom Region
Does it sound an internal error in IBM services ??
We are aware of this issue and it is being worked on. Will post a response as soon as it is fixed.
I just checked and I get the same error, so it does sound like an issue with IBM services
The service has been up and running. Please mark the answer as accepted if you can access the VMs.
Related
I followed the exact steps of the evosuite official tutorial (http://www.evosuite.org/documentation/tutorial-part-1/), and what I always get is this:
IMAGE
It always says that "failed to register client service", then java exceptions were thrown due to connection failure. My device is perfectly connected to the internet. I tried to ping the connection site and there was reply. What should I do?
I restarted my computer then it worked.
I'm using Mobile Foundation on IBM Bluemix and I'm facing problems in setup IBM MobileFirst-CLI to deploy adapters and apps throw my corporate proxy.
In time, I'm on a macOS with the CLI version below:
mfpdev -v
8.0.0-2016070716
At this time, every time I have to interact with the server in have to connect to it using my phone tethering. Please help, I'm running out of all my data plan.
The actual error:
$ mfpdev adapter deploy
Error: Cannot connect to server 'mfp-bluemix-dev' at 'https://xxxx-server.mybluemix.net:443'.
Reason: Missing runtime configuration details.: connect ECONNREFUSED 158.99.999.99:443
ps: address and ip of server obfuscated.
Best regards,
Bernardo Baumblatt.
At the moment, MFP Dev CLI does not have the feature to configure a proxy. However, if all communications in your enterprise are routed through the corporate proxy, and the proxy can connect to IBM Bluemix, there should not be a problem.
You can submit a Request for Enhancement to add proxy feature to MFP Dev CLI.
What Pat said in his comment is correct. I suspect that you have two issues to address:
Your corporate proxy must allow access to your server's HTTP and HTTPS endpoints (9080 and 9443). I've also heard of cases where the personal firewall on the individual's workstation has interfered.
You are running a VERY old version of the CLI. Assuming your instance of Foundation Server on Bluemix isn't that old, you'll need to upgrade to interact with it properly. I strongly suggest that you upgrade to the latest version via npm -g install mfpdev-cli.
I am new to Mesos and just finished setting up mesos and along with zookeeper on my test server.
Unfortunately I keep getting this error message on my mesos console indicating i am unable to connect to mesos on port 5050 and can't seem to figure out why.
I have included the error in the screen shot below
The mesos log files doesn't point to why the error is showing either.
I resolved the problem by this:
./bin/mesos-master.sh --ip=x.x.x.x --work_dir=/var/lib/mesos --hostname=x.x.x.x
We can avoid this problem by starting mesos-master with following option:
--ip=xx.xx.xx.xx --hostname_lookup=false
I have resolved this problem. Open the web page in Chrome, and open the developer tool, you will see the chrome is accessing the web site with domain, in my case the domain name is "mesosphere", as there is no mesosphere in dns, so the accessing was failed.
I solved the problem by adding the mesosphere in the hosts file, C:/windows/system32/etc/hosts/
If you use the domain name for the Mesos cluster you must set the domain name in windows hosts.
There can be multiple issues here.
Is your mesos-master running and healthy ?
Has leader election process completed, if all is good.
Check if you are able to do
ping leader.mesos
If above ping doesn't work, that means leader has not been elected. First fix that.
I had this problem also. Luckily, I have a running mesos server also. So, I can compare the different between my demo and the running mesos server. I captured the packets between client and server in my demo. I found the explorer didn`t resend fresh request, only some keepalive packets.
but, when I catch the packets in the running mesos server, I found the explorer send get request frequently. like the image
I think, if you run some task or add some agent, maybe it will activate the explore to send request frequently. Then the "Failed to connect" will disappeared.
I was having the same issues and what fixed it for me was the zookeeper configuration. In my case I was using the EC2 public IP Address rather than the private one. Once I changed the /etc/mesos/zk file to zk://<private IP>:2181/mesos I was able to connect without the constant error messages. In other words, zookeeper was reporting to be running in one IP and mesos-master was trying to connect using a different IP.
My configuration was correct as suggested. But failed to start mesos-master service. But There is alternative way to start mesos-master node with exact same configuration. Commands to start mesos-master
$ cd /usr/sbin [or mesos_installation directory/bin]
$sudo ./mesos-master --work_dir=/var/lib/mesos --log_dir=/home/rajeev/logs/mesos/
Its start mesos-master service successfully for me.
I have installed Worklight 6.2 on Linux, using Liberty 8.5.5 and DB2 10.5. Created the DB2 databases for WRKLGHT and WLREPORT. Have executed the Server Configuration Tool and successfully created a Worklight Server configuration (did not have any errors in the Console view when running the Ant tasks, tables were created successfully in the database, and configuration shows deployed status in the SCT). Created a runtime environment in the SCT, also seemed to succeed (no errors in Console view, tables created/updated, runtime environment shows deployed in the SCT). Stopped and restarted the Liberty server.
Can hit Worklight admin at (/worklightconsole) and log in successfully using my demo user, however it then indicates there are no runtime environments. When trying to access runtime environment at /worklight/console (which should be the correct URL given how I created the runtime config in SCT using my Worklight project WAR), I get various errors: first "Service unavailable since initialization is not yet complete." then after retrying for about a minute or two I get "javax.servlet.ServletException: java.lang.RuntimeException: Timeout while waiting for the management service to start up at com.worklight.core.auth.impl.AuthenticationFilter.isWaitingForInitialization(AuthenticationFilter.java:561)".
Seems the management service is not starting up successfully. Upon reviewing the messages.log I see the following error precede it: "FWLSE0242E: Failed to synchronize application runtime information. The servlet initialization failed and the servlet will deny serve. The most common reason is a failure in JMX communication with the ''worklightadmin'' service. You need to restart the web application after fixing the problem. [project worklight]" and this creates an FFDC log.
I know this is a lot of information but trying to be complete. Anything I should check to fix the JMX communication issue and get the management service starting?
Thank you for the replies back. Turns out there is an issue with Liberty (I was on 8.5.5.0) and the IBM JDK I was using (1.7_64). Swapped out to the Oracle JRE (1.7.0_60-b19), pointed Liberty to use it, and the problem was solved. I am pursuing a fix with the Liberty team through IBM Support for this issue.
I cannot give a unique solution, but I can explain the situation and this may lead to a solution.
The runtime servlet initialization tries to contact the Worklight Admin service. The Worklight Admin service is a web application that must be running when the runtime starts. The runtime was not able to find the Worklight Admin service. It waited a while, in case that the Worklight Admin service is just starting up, but then gave up due to a timeout because within a given time, it could not find the Worklight Admin service.
Possible reasons:
the web server is not at all configured to run the Worklight Admin service. In your case, this seems not the problem, since you can access the Worklight Console. You should also see in the log file whether the Worklight Admin service did start.
the worklightadmin service might never start up ... this could be a configuration problem, e.g. with the WLADMIN data base. This could also be detected from the server logs.
when the runtimes and the Worklight Admin service start up together, it might be that the Worklight Admin service simply takes too long to start. Let's say you have 100 webapps, and the runtime starts first and the Worklight Admin service starts last, it could be that the 98 other webapps take too much time to start. In that case, make your web server lighter ... run only Worklight on that webserver, nothing else.
the Worklight Admin service starts, but the runtime cannot communicate with it. This indicates that the JMX communication is misconfigured. Follow the documentation of the webserver how to configure JMX. For liberty, see http://www-01.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.ibm.websphere.wlp.core.doc/ae/twlp_admin_restconnector.html?cp=SSD28V_8.5.5%2F1-5-2-10-1&lang=en
I recently tried using Jelastic trial version.I created 3 or 4 accounts on it.On each of the environment that i created i used Glassfish server and MongoDB database.All those environments crashed within a day and i get 502 Application Down Error.
Why does this happen?
As a potential cause it could be a lack of resources (cloudlets). GlassFish is a heavy application server, in Jelastic it requires 6 cloudlets at least.
You need to check your application server's logs to get the cause of failure in details.1
If it does not help, contact your support by clicking Help | Contact Support.