Waiting For Metadata Server

[Steven Osborne]

Compute Engine running Ubuntu 16.4.

I was migrating one of my compute engines from US East1-d to US Central1-c when I started experiencing this problem.

From the Serial Port:

Jul 5 20:45:33 aw1 google: Waiting for metadata server, attempt 2392

Jul 5 20:45:33 aw1 google: There is likely a problem with the network.

Jul 5 20:45:35 aw1 google: Waiting for metadata server, attempt 2393

Jul 5 20:45:35 aw1 google: There is likely a problem with the network.

Jul 5 20:45:37 aw1 google: Waiting for metadata server, attempt 2394

Jul 5 20:45:37 aw1 google: There is likely a problem with the network.

Jul 5 20:45:38 aw1 google: Waiting for metadata server, attempt 2395

Jul 5 20:45:38 aw1 google: There is likely a problem with the network.

Jul 5 20:45:40 aw1 google: Waiting for metadata server, attempt 2396

Jul 5 20:45:40 aw1 google: There is likely a problem with the network.

Jul 5 20:45:42 aw1 google: Waiting for metadata server, attempt 2397

Jul 5 20:45:42 aw1 google: There is likely a problem with the network.

Jul 5 20:45:42 aw1 accounts-from-metadata: WARNING error while trying to update accounts: <urlopen error [Errno 101] Network is unreachable>

Jul 5 20:45:43 aw1 google: Waiting for metadata server, attempt 2398

Jul 5 20:45:43 aw1 google: There is likely a problem with the network.

Jul 5 20:45:45 aw1 google: Waiting for metadata server, attempt 2399

Jul 5 20:45:45 aw1 google: There is likely a problem with the network.

Jul 5 20:45:47 aw1 google: Waiting for metadata server, attempt 2400

Jul 5 20:45:47 aw1 google: There is likely a problem with the network.

Jul 5 20:45:48 aw1 google: Waiting for metadata server, attempt 2401

Jul 5 20:45:48 aw1 google: There is likely a problem with the network.

Jul 5 20:45:50 aw1 google: Waiting for metadata server, attempt 2402

Jul 5 20:45:50 aw1 google: There is likely a problem with the network.

Jul 5 20:45:52 aw1 google: Waiting for metadata server, attempt 2403

Jul 5 20:45:52 aw1 google: There is likely a problem with the network.

Jul 5 20:45:53 aw1 google: Waiting for metadata server, attempt 2404

Jul 5 20:45:53 aw1 google: There is likely a problem with the network.

Jul 5 20:45:54 aw1 ntpd[1233]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)

Jul 5 20:45:55 aw1 google: Waiting for metadata server, attempt 2405

Jul 5 20:45:55 aw1 google: There is likely a problem with the network.

Jul 5 20:45:57 aw1 google: Waiting for metadata server, attempt 2406

Jul 5 20:45:57 aw1 google: There is likely a problem with the network.

Jul 5 20:45:58 aw1 google: Waiting for metadata server, attempt 2407

Jul 5 20:45:58 aw1 google: There is likely a problem with the network.

I've keep getting "Unable to connect on port 22" when I try using SSH from the GCP Console. I've spent the last couple hours searching for an answer, but I haven't turned up anything.

If there's anything else you need to know, please ask.

[George (Google Cloud Support)]

Hello Steven,

Before migrating the instance, was there any modification on the networking side of the machine? If you are aware of any changes, you can revert them by attaching the instance's disk as a secondary disk to another instance, mount it and modify the changes. Once done, detach the disk and create a new instance with it.

Looking forward to your reply.

Sincerely,

George

[Steven Osborne]

George,

I can recall no changes to anything network related on the operating system, the only thing I did was preemptively switch my domains to the new IP. I tried switching the IP of the domains around several times (TTL is 5m) but saw no change. I did also try attaching a copy of the disk to another instance and tried messing with the DNS settings, but I it still have me the same problem when I spun up an instance with the modified disk.

[George (Google Cloud Support)]

Hello Steven,

I wasn't able to reproduce on my test account with the following image: "Ubuntu 16.04 LTS amd64 xenial image built on 2016-06-27".

Is this the same image build that you had issues with? Did you follow the requirements mentioned in this Help Center article before the instance move?

Looking forward to your reply.

Sincerely,

George

[Eric Muthama]

 you can revert them by attaching the instance's disk as a secondary disk to another instance  - How do you do this on cloud compute

[Shanmugam Kulandaivel]

Please see the section titled 'Use your disk on a new instance' in https://cloud.google.com/compute/docs/troubleshooting  

--
© 2016 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
 
Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-discussion@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
---
You received this message because you are subscribed to the Google Groups "gce-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gce-discussion+unsubscribe@googlegroups.com.
To post to this group, send email to gce-discussion@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/gce-discussion/071b6b03-90b2-4920-a9bc-f682789cc360%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Thanks,

Shanmugam