Instances Schedule Not Working

[WaiKeat]

I have configure instances schedule, and confirmed that indeed:

- Necessary permission is granted (i.e service account can shutdown and bootup the servers)

- The servers are indeed included in the schedule (i.e I am not making the mistake of simply create the instances schedule and forget to add server/s to the schedule)

- Timezone is correct.

BUT, the time scheduled has come. Yet after 3 minutes of the scheduled time, my instances doesn't get shutdown.

I suspect it won't get shutdown if I am using it or remote into it, so I just turned on the VM without having anyone remote into it. Yet the instance won't shutdown automatically.

Anyone in the forum has experienced this before? or can offer any advice of where/what else I could check?

Best Regards,

Wai Keat

[alexmoore]

Hi there,

Couple of other things to check, according to the documentation it can take up to 15 minutes past the scheduled time to action, you mention you have waited 3 minutes, so perhaps wait a little longer?

Another point is the schedule and the VMs need to be in the same region, so another aspect to check.

See: https://cloud.google.com/compute/docs/instances/schedule-instance-start-stop#limitations

Just a couple of initial thoughts.

All the best,

Alex

[WaiKeat]

Thanks, let me try 15 minutes then.

As for making sure they are in same region, yes, both VMs and instance-scheduler are in same region.

Thanks Alex

[WaiKeat]

Hm....waited for more than 45 mins, no luck still.

[alexmoore]

Hi,

I just created a quick test and for me at least, the stop command was executed 6 minutes after the schedule, no issue.

Do you see anything in Cloud Logging?  You should see the GCE Service Agent account attempt the stop call against the VM?

Best,

Alex

[cktw]

I too, have exactly the same issue. Checked all things mentioned here but still could not get the schedule to work.  Any more pointers ? 

[chronowarper]

I seem to have the same problem as the OP as well; my instances don't start or stop based on the scheduler. I set them up through console.cloud.google.com. 

Timezone, permissions looked ok. I waited over 15 minutes.

I don't see any agent attempting to start/stop instances in the logging. I searched for "GCE" but maybe I'm not searching for the right keyword?

[raphscho]

Same over here. Although permissions are granted and timezone is set correctly, the scheduler doesn't try to stop the VM. Any idea?

[chronowarper]

So I did two things (not sure which was the trick) and I think that got my first schedule to run

#1. set up the default time zone (with running "glcoud init" in CLI)

#2. clicked the 'activate' banner at the top of the console.cloud.google.com website.