I'm trying to setup my GCP account, so that I can use a cloud GPU to run my Tensorflow projects.
I am following this guide from google, but for some reason, when try to create a new notebook instance, I get the following error:
Account not found for tombstone account.
I have absolutely no idea what a tombstone account is, and how I would create one. Google doesn't mention anything about this, nor in the guide, so I really hope someone could point me in the right direction here.
"Account not found for tombstone account." is seen normally when you delete a Service Account and try to use it or recreated it after a short period of time.
I would try to create a new Service Account with a different name and specify it when you create the new AI Platform Notebooks instance.
Related
I decided to try mining ZCash on a Nanopool pool. I don't understand why an account is still not being created. Mining on nheqminer CPU produces better than GPU. The problem is that I still don't see my account with a balance.
Remember: to add your account to the database you should find at least one share
One share was found (unfortunately I can't provide a screenshot), but nothing has changed on the wallet page.
How to understand when a share will be found and whether a wallet will be created
Background and Goal
I have a Debian/Linux VM on GCP which I manually start every morning and after it runs, it shuts down by itself using a Linux command. I want to automate the start of the VM by using the Cloud Scheduler. The question asked in GCP auto shutdown and startup using Google Cloud Schedulers has several answers and I am interested in pursuing the answer (https://stackoverflow.com/a/65062924/10322004) proposed by #nikelone because it seems to be simple and also it has been endorsed by #Damien and #RayFoss as being easy. I am a neophyte in these matters and I could not comprehend their replies fully. So this post was created to elicit more clear answers for a person like me.
What I have tried
I have gone to https://cloud.google.com/compute/docs/reference/rest/v1/instances/start (call this page A) and tried the API and was able to successfully start my already stopped VM when I clicked on the execute button. I presume that this means that my entries were fine and can be used in conjunction with appropriate software like Cloud Scheduler to perform the start function on a predefined schedule. But the problem is that I do not know or understand how to proceed from here. I give below my questions.
My Questions
On page A, the last three paragraphs are titled Authorization Scopes, IAM permissions, and Examples, and none of them say anything specific about what the user should do. Is it correct to assume that they have nothing to do with the Cloud Scheduler, but related to other methods to achieve the same goal? If this is not correct then my next question is what should I be doing to follow the statements in these three paragraphs?
Assuming that the answer to question 1 is "yes", meaning I can now start scheduling with the Cloud Scheduler, I next looked at the quickstart for Cloud Scheduler at https://cloud.google.com/scheduler/docs/quickstart (call this page B). The list of items to do is quite large including installing Cloud SDK, running a quite a few commands on the console, enabling some features, set up Pub/Sub, create a job, run the job and verify the results in Pub/Sub. This looks like a daunting set of tasks and I could not understand why it is necessary to jump through the hoops to use something that has already been achieved with just a few keystrokes earlier. So are these steps all necessary? Or is there a way to use the Cloud Scheduler directly without going through so many intermediate steps?
Now assume that the answer to question 2 is that I have to perform all steps stated on page B. If I run into some problem while accomplishing the tasks outlined on page B, my VM may get messed up irretrievably. Is there a way in which the Cloud Platform or its components can be used to reset my VM to its current state as of today, which is working fine? I really do not want to end up with something worse than what I have now.
To answer your questions:
Auth Scopes and IAM permissions are required for you to call the Compute Engine API methods such as instance.start & instance.stop. You need to set the right scope and the right IAM permission on your job or else it will fail. They are indeed related to the method that you're interested to call so you must keep them in mind. What you see on the examples are the ways to call the {API} using different programming languages so you don't need to pay attention to them as you will create the job through the Cloud Console. To further address this part, see the full steps I included below.
The answer that you're trying to follow uses HTTP target while the quickstart you've linked uses Pub/Sub and they are different with each other because they have separate use cases. This link shows a proper instruction how to create a scheduler job with an HTTP target. You can create this kind of job straight from the Cloud Console or a one-liner gcloud command. If your config is incorrect, the trigger will not execute the endpoint URL and you will see an error that you must fix.
Addressed on answer #2
Basically, you just need to follow the instructions to the link you've sent. However, I'll post it here as well along with my explanation:
Go to https://cloud.google.com/scheduler. Click on Go to Console. Click on Create Job. Fill up the required fields (those with red asterisks) when creating a Scheduler Job.
Select HTTP as target type.
Enter this as your URL (modify the capitalized words).
https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/INSTANCE_ZONE/instances/INSTANCE_NAME/start
Choose HTTP method POST.
Click show more and choose Auth Header "Add OAuth Token"
Enter your service account. This is used to pass an OAuth Token when your scheduler job calls the Compute API. Make sure that the service account you will use have the "Compute Instance Admin" role because this role contains the permissions to start/stop your instance. See this instruction how to grant access on a service account. If you're not sure what service account to use, feel free to use the Compute Engine default service account.
Add this on Scope:
https://www.googleapis.com/auth/cloud-platform
The description of this scope:
See, edit, configure, and delete your Google Cloud Platform data.
Repeat for Stop instance job and change URL in #3.
We are planning a lecture series of machine learning and is trying to show some easy examples using Google Colab. However, some of the target audience is not that familiar computer or programming stuff, and we want to make it as easy as possible.
I'm wondering is it a must for everyone to have a Gmail account to view the examples in Colab? Or is there anything similar to using a 'group access' that we can set up a guest account?
Thank you very much!
Users can view notebooks shared publicly without sign-in.
In order to execute code, a Google account sign-in is required. Instructions to create an account are here.
Yes, in 2023 it is necessary to have a Google account. Just sharing the link is not working anymore. Because I had this issue I moved to binder. The setup is more difficult since all is backed by a public GitHub page and hence works only with public data.
My spreadsheet was working normally, but this error started to appear. My account is business, so I did not activate the charge.
I've done some spreadsheets and none of them needed it.
Can someone help me?
This error
The error message states that you do not have a billing account attached to this project and therefore you will not be able to perform querying in BigQuery of your own data until you attach a billing account. If you are saying that everything works from the UI of the Google Cloud Platform Console, you are probably using a different project there.
I'm playing with Actions on Google and created some projects. I've deleted all of them but I'm unable to create new ones. I receive an error messages stating that I've reached the project limit for my account. Is there a way to reset this counter once all the projects have been deleted?
Try to delete the same project on the Google CloudPlatform.
However, I fix this problem by creating a new google account or applying for additional quota for non-paid Cloud Services. I recommend the latter method, since you only need fill the application form and wait 2 work days to get approve.