Closed purkhusid closed 7 years ago
Yep, I got a similar error under Packer 0.11.0; crash.log
EDIT: moved log to gist
@Xyon I fail to see the similarities and it's not very useful to report issues with such old versions lik 0.11.0.
Sure it's helpful; now you know it wasn't introduced with 0.12. I will admit, I don't appreciate Packer's release or development cycle, but 0.11 -> 0.12 didn't seem like a massive leap to me, hence the conjuction.
As for similarity, the OP's report is significant here:
2017/01/06 16:03:42 packer.exe: panic: runtime error: invalid memory address or nil pointer dereference
2017/01/06 16:03:42 packer.exe: panic: runtime error: invalid memory address or nil pointer dereference
2017/01/06 16:03:42 packer.exe: [signal 0xc0000005 code=0x0 addr=0x30 pc=0xa17539]
Which signal, by the by, is STATUS_ACCESS_VIOLATION (or, SIGSEGV in the *NIX world).
Mine is significant here:
2017/01/09 13:51:20 packer: panic: runtime error: invalid memory address or nil pointer dereference
2017/01/09 13:51:20 packer: [signal SIGSEGV: segmentation violation code=0x1 addr=0x58 pc=0xe82b99]
The same problem (underlying problem with the builder) resulted in the same error message and the same signal being caught by Packer across two platforms, two different builders, and two versions. In both cases, it seems clear to me that because the underlying builder has failed - in the OP's case, digitalocean with an unexpected EOF, and in mine, virtualbox protesting about the VM session still being locked, has caused Packer to implode rather than handle the situation gracefully and point fingers at the root cause effectively. It shouldn't be causing a SIGSEGV when this kind of problem happens, which is why I reported it as well - though the root cause is a different problem, the behaviour from packer is the same, and is a bug.
@Xyon That is a nil pointer dereference
it's not the same issue, it's the same class of bug see Null pointer. Please open a new issue for problem with all info needed and logs from 0.12.1.
possibly related to #4363
which also complains of
2017/01/05 17:07:30 packer: 2017/01/05 17:07:30 ssh session open error: 'ssh: unexpected packet in response to channel open: <nil>', attempting reconnect
but without the panic
I believe I have a related crash as well. The panic dump appears the same; however, I'm building on a WinSrv2012R2 host and attempting to create the image in AWS from the same WinSrv2012R2. This error appears transitory as I was later able to successfully build.
@jonathansd1 that doesn't appear to be related to this issue. Please open a new issue for problem with all info needed and logs from 0.12.1.
Apologies. I will open another issue.
Unfortunately I'm not able to reproduce this on windows 10 with the latest build of packer.
Does this happen consistently? Is it still happening with the latest version of packer?
@mwhooker I just had similar issue in my personal project. It was caused by opening of a new SSH session over existing connection after previous session was closed. Second session was failing with the same error. Hope it will help.
Closing this issue since we still don't have a repro case; if you are still experiencing this with latest packer, please reopen with details for us. Thanks!
I just a built a new Windows 2012 Server and all the files stored locally, using Packer 1.1.1 version and the json file details below. I am getting SSH error "hyperv-iso: waiting for ssh to become available"
I have set the ssh_timeout as 15 m, still i am getting error. Any one please help!!!
This is unlikely to be related to the original ticket.
Does your autounattend file configure SSH? SSH doesn't get turned on by default.
If you need help setting this up, please send your question and relevant files to our mailing list: https://groups.google.com/forum/#!forum/packer-tool
I'm getting an EOF error when trying to build this file:
Packer version: 0.12.1 on Windows 10
Error log: