Timeout waiting for WinRM #8
Comments
|
Yeah it takes almost 5 hours on my test host box. I've seen it complete just 10 minutes short of the 5 hour timeout so it might be a good idea to extend to 8h (ugh). I do think there are things to be done to speed up the updates. However the dism and file zapping take a while too but clearly the updates take the longest by far. The idea here is that building images is an infrequent event as opposed to provisioning VMs. So I'm willing to put up with the wait but it does suck that packer deletes the artifacts on failure making it difficult to troubleshoot. |
|
Hi Matt, My feedback wasn't about the length of time it takes to run so much as the error that I'm getting. Notice above that it fails with this error: I don't see any other instructions in the README besides downloading the .iso and running |
|
Sorry for the misunderstanding. I go into alot more detail in my blog post. The packer flow is that once it can connect via winrm, it shuts down the box and starts the provisioners. I dont put all the setup stuff in a provisioner because boxstarter reboots would cause that to fail. So instead, I leave winrm off until everything is done. This way packer just waits until the whole process is complete and thats why I was talking about the timeout. If it does not complete before the timeout. Packer fails the entire build. |
|
Got it now! I'll give that a shot and close the issue after confirming. Thanks Matt :) |
|
OK, I tried again and it worked great! Sounds like it didn't complete in the timeout period the first time (computer went to sleep perhaps?), but did the second time. @mwrock: thanks for the help. |
|
Pardon for the late entry, I've rather basic question. my packer build hosts are on redhat and debian. Is the winrm communicator for when the build host is a windows box? thx |
|
These still use a winrm communicator even though they are linux hosts. The main difference on linux hosts (assuming you are running as a server and not desktop) is that the VirtualBox build is headless and therefore you cant see into what the VM is doing while the host is waiting for WinRM to connect. |
|
OK. So the communicators (winrm, ssh) are truly build host agnostic. That's what I was hoping. Thanks! |
|
Hi Matt Sorry again for the late entry. Iam facing the same issue of winrm getting timed out .Please suggest any solution in regards with this since I have been lingering on the step for nearly 2 days. I have also set the winrm timeout to 8 hrs but also the winrm is timing out. PS C:\Users\panugpr1\Desktop\chef-repo\packer-templates-master> .\packer.exe build -force -only virtualbox-iso vbox-2012r2.json ==> virtualbox-iso: Downloading or copying Guest additions ==> virtualbox-iso: Timeout waiting for WinRM. ==> Some builds didn't complete successfully and had errors: |
First, I just want to say that this is a great contribution, and something that will make it easy for folks to create Windows Server boxes that they can use with Vagrant and Test Kitchen.
I downloaded the .iso and ran
packer. It was taking a long time (hours) for the Windows Updates to complete, so I walked away from my computer for awhile. When I came back, the process completed with errors.Here's my output. Did I miss something along the way?
The text was updated successfully, but these errors were encountered: