I have a Bitnami Wordpress Multisite installed on Google Compute Engine. Recently, it was turned off repeatedly with no reason. I have rebooted it via the Bitnami control panel on Jul 2nd and it seemed to work, but now it does not. Here is my compute engine 7-day-report.
One thing to check in this case is the Google Compute Engine VM instance availability setting: it can be either live migrate or terminate, which tells Google Compute Engine what to do with your VM when the underlying host needs to undergo maintenance. Note that there's an automaticRestart setting as well, if you choose the terminate option.
This is a per-VM setting.
If it were set to "terminate", that may explain the issue you saw. Setting it to "live migrate" would mitigate the issue.
You should check your quotas page, you may be running out of something !
Quotas can be found under compute engine menu on the left.
Related
At the end of the Google Cloud trial period, my VM was stopped by Google. This is understandable, but what comes next doesn't seem so. I have now upgraded to a paid account, but I am still unable to restart the VM. Google cloud support will not help turn the VM back on. They've told me that my only support option is to post my issue here on Stackoverflow. It seems odd that a business like Google would rely on outsourcing it's technical support to the people here.
So here I am. I thank you in advance for reading my issue.
The error message is:
"Starting VM instance "myinstance" failed. Error: Google Compute Engine is not ready for use yet in the project. It may take several minutes if Google Compute Engine has just been enabled, or if this is the first time you use Google Compute Engine in the project."
I have tried multiple times over two days and I still get this same error. The one thing Google did check and verify is that my billing is set up correctly. The dashboard shows that the billing is linked to the project that contains this VM.
Can anyone suggest any troubleshooting steps or solutions?
Thank you.
I have an old Debian Compute Engine instance (created and running since December 2013) and got an email warning about the turndown of Legacy GCE and GKE metadata server endpoints (more details at https://cloud.google.com/compute/docs/migrating-to-v1-metadata-server).
I followed the directions for locating the process and found that the requests were coming from /usr/share/google/google_daemon/manage_addresses.py. The script seems to be the same as what's at https://github.com/gtt116/gce/blob/master/google_daemon/manage_addresses.py (also with what's in that directory).
I don't recall installing this, so I'm imaging it came with the provided Debian image I used in 2013.
Does anyone know what this manage_addresses.py script is, what it does, and what I should do with it now that the legacy metadata server endpoints are turning down? Is it safe to just stop running it? Or is there a new script I should replace it with? Or should I just try to update it myself to use the new endpoint?
I dug around and was able to trace /usr/share/google/google_daemon/manage_addresses.py as being installed by a package called google-compute-daemon. A search for that brought me to https://github.com/GoogleCloudPlatform/compute-image-packages#troubleshooting which explains that google-compute-daemon has been replaced with python-google-compute-engine. That led me to https://cloud.google.com/compute/docs/images/install-guest-environment . I followed the instructions there and manually installed the guest environment.
I noticed during installation that it said it was removing the google-compute-daemon package (and a packaged called google-startup-scripts), so this seems like the right thing. And I'm no longer seeing any requests to the legacy endpoints. So it seems like at some point the old guest environment failed to update.
TLDR; If you have this problem, follow the instructions at https://cloud.google.com/compute/docs/images/install-guest-environment#installing_guest_environment to manually update the guest environment.
I'm trying to set up GUI access to a linux VM on google compute engine. I've followed the advice here:
https://groups.google.com/forum/#!topic/gce-discussion/tN9oZs8xWps
I can get as far as getting the instance to show up on the "My Computers" section of the CRD app, but it is grayed out.
I'm wondering if I need to mess around with firewall settings, or try a different desktop (I've been trying cinnamon). I'd appreciate any help. Thanks!
You definitely have to open the ports to connect, so you will have to use a firewall rule. Cloud Platform has an implicit deny ingress rule. It is explained in the thread you posted that also if you are using CentOS there is an additional steps to disable a firewall rule.
I set up a LAMP instance in Google Compute Engine approx 45 days ago, and it came with phpMyAdmin already set up and accessible via a button in the console (in Compute Engine -> VM instances -> instance-name -> phpMyAdmin).
The button is now gone, and I can't find any documentation regarding the change. I can still access it via the browser at my-ip/phpmyadmin.
Just wondering if there was some recent change I was unaware of. I can update phpmyadmin manually but it appears that GCE no longer "officially" supports it.
I am assuming you deployed your LAMP stack via deployment manager. https://console.cloud.google.com/deployments/
If so, you should be able to access your deployment and all the relative details over there including login link for phpmyadmin.
As far as support from Google is concerned, since you have already deployed your instance, even if they remove it from their deployments, it will never affect what you have deployed. Moreover I just deployed a new instance and I can see that phpmyadmin is as an option (not sure if it always was). But even after adding it to my deployment, no extra instance for phpmyadmin was created. It is in the same instance as my rest of stack.
Since you are able to access it via your URL, there's nothing be worried about, and there are no changes on GCP side either. If anything, phpmyadmin is now optional.
By following steps given in below link I enabled tracing for compute engine.
https://cloud.google.com/cloud-trace/cloud-trace-quickstart
After enabling trace, it seems to automatically get disabled. I have tried many time but same result. Pls help.
At the moment Cloud Trace only traces Google App Engine, so it might not be helpful to you if you are using Google Compute Engine.
Try making sure you have an App Engine app deployed and that you have billing enabled.