Cannot restart Google Cloud VM - virtual-machine

I ended my trial period with google cloud, and I have upgraded my account, still my virtual machine is stopped and I get this following error, which I couldn't manage to solve.
Starting VM instance "hasoffer-api" failed. Error: The default network interface [nic0] is frozen.
Can anyone give me a tip to solve this issue?
Many thanks in advance

Most of the times, that error is due to a deletion process of the project or a recently change in your billing account, what it seems to be your problem.
In this case, it is neccesary to file a case to Google Support.

Related

Colab keeps disconnecting very frequently

I keep trying to connect to the hosted runtime on Google Colab, but it disconnects me after a few seconds (up to 10 secs).
The JavaScript Console of Firefox (the latest version) shows this:
Error: "SocketIO error: xhr poll error: 0 - TransportError"
I experience similar disconnect with Kaggle. How can I fix that? Thanks.
Edit: This may not be the final answer, but turning off VPN seems to fix the issue with Colab. Turning VPN back on does not cause the issue, but Kaggle still does not work, it might now just be a Kaggle issue.
Edit 2: With VPN back on the issue comes up again.

My Openshift app (free plan) keeps disapearing after few days

Does anymore same experience or solution for that ?
My app works fine only several days after deployment, after that it turns to blank screen with "Not Found" text on it.
App is with "WildFly Application Server 8.2.1.Final" Cartridge with status "Started" - note that I am aware of iddling of apps at Openshift, this is not the case.
Recieved reply from OpenShift as following :
It looks like you're hosting your app on a small gear. The WildFly cartridge could be quite memory consuming, depending on what app you are deploying. Please check whether the gear is not having memory issues, as described
https://developers.openshift.com/faq/troubleshooting.html#_why_is_my_application_restarting_automatically_or_having_memory_issues
If there seems to be no memory issues, please check your log files for further information about the problem. You can check your log files by using the 'rhc tail' command, or by sshing into your application and looking in the ~/app-root/logs directory.
You can learn more about checking your log files in our Developer Portal (https://developers.openshift.com/en/managing-log-files.html)

Google Cloud Installation: Hostname unresolved

Okay, feel really dumb as I can't even install Google Cloud SDK. Started using command line and then moved to the installer. I got a "Download Failed:Resolving Hostname" Error. There seems to be nothing in the guides and any youtube videos say it installs easily - just keep clicking next?!?
Why am I being asked to set up a network proxy?
I'm using VPN? Could that be the issue?
Thanks in advance
It was the VPN. Annoying. Whilst posting this it occurred to me so I tried with the VPN disconnected and yipdy do dar, it worked.

DCOS: not able to start any service is always shows deploying

Enviornment :
DCOS : 1.7 running on vagrant
There are many reasons this could fail, but you did not provide enough information to narrow it down. However, the most common problem observed when getting started is missing the bit about having a private vs public agent available and the role being specified in the app json. I can't tell from the single screen shot what environment you are running or the json for the apps you were trying to run. If you are really stuck, try visiting https://dcos.io/docs/1.7/administration/installing/custom/troubleshooting/ and check out their slack channel for assistance. https://dcos-community.slack.com/
I got the same problem when installing DCOS form the Azure template, when I logged in, it appeared that I had 0 nodes connected in my cluster (which is obviously not good). I reinstalled it from another template and it fixed my problem. Hope it helps.

ASP.MVC 4, Azure Caching: Error on both local and remote - "role discovery data is unavailable"

Whew...ok, been wrestling with this for a while and I can't figure out what is going on.
I am new to Azure caching, but at this point I have read a good bit and I think I have it setup right, but something is obviously wrong so what do I know?
Ok, so first I setup a dedicated caching web worker role using this fine tutorial: http://berniecook.wordpress.com/2013/01/27/distributed-caching-in-azure-cache-worker-role/
I have an ASP.net MVC 4 website that is supposed to be using it.
I have my solution set to multiple starting projects with my cloud caching project set to start first, but no matter what I do, I get the "role discovery data is unavailable".
Sometimes in my output log I get that the Role Environment failed to initialize, but not very often. Most of the time the output log says that is succeeds. Regardless of that, I still get the error above.
I was thinking that maybe the issue was because I was running on local azure storage and compute emulators, so I reconfigured and published the Cloud Service to Azure to see if that helped.
It didn't...
The fun part is that there have been exactly 2 times when it suddenly worked (both when I was working locally). 2 times about of about 100. I didn't do anything different...just ran the debugger and poof, it all worked. This at least lends a bit of credit that it is actually setup correctly.
Needless to say, this is putting a huge damper on my productivity so any advice would be appreciated.
Update
Ok, I have figured out a workaround of sorts...I have learned that the reason that it consistently failed was because the development web server was holding onto a file which prevented the caching server to launch correctly.
The workaround is to stop the web server each and every time I want to recompile and run the code. This is obviously not ideal, so any ways to make this more reliable would be appreciated.
Thanks,
David
I don't know if this helps but I find that if I don't shut down the both the storage and compute emulator, I get weird errors, so after doing an F5 and closing the browser down, I manually shut down both emulators