Hello, I''ve been testing puppet on windows 8.1 to distribute packages across our network. Unfortunately, it appears to crash intermittently. I run the puppet help command from the command line and it works about a quarter of the time. Other times it simply gives no output, which I assume is it crashing. Unfortunately I have been unable to find anything in any logs and the ruby verbose parameter gives exactly the same output for times when it crashes and times when it doesn''t. Any thoughts? Jason Bray -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Jason, Can you provide details? What version of puppet? MSI or gem? If gem, what version of ruby? Also, can you run something known to fail with --trace --debug --verbose and post the output here? On Thu, Oct 17, 2013 at 11:11 AM, Jason Bray <jbray.1982@gmail.com> wrote:> Hello, > > I''ve been testing puppet on windows 8.1 to distribute packages across our > network. Unfortunately, it appears to crash intermittently. I run the > puppet help command from the command line and it works about a quarter of > the time. Other times it simply gives no output, which I assume is it > crashing. Unfortunately I have been unable to find anything in any logs and > the ruby verbose parameter gives exactly the same output for times when it > crashes and times when it doesn''t. > > Any thoughts? > > Jason Bray > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscribe@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out. >-- Rob Reynolds Developer, Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Of course, sorry. Puppet 3.3.1 installed from an MSI, I believe the ruby version is 1.9.2, but I''m not 100% on that. As for the output, literally it has no output at all. For example C:\Scratch> puppet help --verbose --debug --trace C:\Scratch> With only a moment''s delay between the two. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Jason, Sorry, I meant applying a catalog or running something that causes puppet to crash in a visible way. Apologies for the miscommunication. On Thu, Oct 17, 2013 at 12:58 PM, Jason Bray <jbray.1982@gmail.com> wrote:> Of course, sorry. > > Puppet 3.3.1 installed from an MSI, I believe the ruby version is 1.9.2, > but I''m not 100% on that. > > As for the output, literally it has no output at all. > > For example > > C:\Scratch> puppet help --verbose --debug --trace > > C:\Scratch> > > With only a moment''s delay between the two. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscribe@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out. >-- Rob Reynolds Developer, Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Well, that is exactly the issue. It doesn''t appear to crash in a
visible
way, there is simply no output for any command I give it. Although, every
once in a while, it appears to work normally and shows output as expected.
90% of the time, the command hangs for a second or two then returns me to
the command prompt with no output whatsoever.
For example
C:\Scratch> puppet apply test.pp --debug --verbose --trace
C:\Scratch>
Actually to make it even weirder, I think I might have been wrong about it
crashing. For example when I run a simple manifest,
file { ''C:\Scratch\foo.txt'':
ensure => present,
content => ''bar,
}
The command prompt looks like this:
C:\Scratch> puppet apply test.pp --debug --verbose --trace
C:\Scratch>
However, when I do a dir, I see that the file has indeed been created.
On Thursday, October 17, 2013 3:48:41 PM UTC-4, Rob Reynolds
wrote:>
> Jason,
> Sorry, I meant applying a catalog or running something that causes puppet
> to crash in a visible way. Apologies for the miscommunication.
>
>
> On Thu, Oct 17, 2013 at 12:58 PM, Jason Bray
<jbray...@gmail.com<javascript:>
> > wrote:
>
>> Of course, sorry.
>>
>> Puppet 3.3.1 installed from an MSI, I believe the ruby version is
1.9.2,
>> but I''m not 100% on that.
>>
>> As for the output, literally it has no output at all.
>>
>> For example
>>
>> C:\Scratch> puppet help --verbose --debug --trace
>>
>> C:\Scratch>
>>
>> With only a moment''s delay between the two.
>>
>> --
>> You received this message because you are subscribed to the Google
Groups
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send
an
>> email to puppet-users...@googlegroups.com <javascript:>.
>> To post to this group, send email to
puppet...@googlegroups.com<javascript:>
>> .
>> Visit this group at http://groups.google.com/group/puppet-users.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> --
> Rob Reynolds
> Developer, Puppet Labs
>
> Join us at PuppetConf 2014, September 23-24 in San Francisco
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
That is interesting. It appears that the log output is not showing up on your console. What console are you using? Can you verify this is happening on more than one machine? On Fri, Oct 18, 2013 at 7:27 AM, Jason Bray <jbray.1982@gmail.com> wrote:> Well, that is exactly the issue. It doesn''t appear to crash in a visible > way, there is simply no output for any command I give it. Although, every > once in a while, it appears to work normally and shows output as expected. > 90% of the time, the command hangs for a second or two then returns me to > the command prompt with no output whatsoever. > > For example > > C:\Scratch> puppet apply test.pp --debug --verbose --trace > > C:\Scratch> > > > Actually to make it even weirder, I think I might have been wrong about it > crashing. For example when I run a simple manifest, > > file { ''C:\Scratch\foo.txt'': > ensure => present, > content => ''bar, > } > > The command prompt looks like this: > > C:\Scratch> puppet apply test.pp --debug --verbose --trace > > C:\Scratch> > > However, when I do a dir, I see that the file has indeed been created. > > > On Thursday, October 17, 2013 3:48:41 PM UTC-4, Rob Reynolds wrote: > >> Jason, >> Sorry, I meant applying a catalog or running something that causes >> puppet to crash in a visible way. Apologies for the miscommunication. >> >> >> On Thu, Oct 17, 2013 at 12:58 PM, Jason Bray <jbray...@gmail.com> wrote: >> >>> Of course, sorry. >>> >>> Puppet 3.3.1 installed from an MSI, I believe the ruby version is 1.9.2, >>> but I''m not 100% on that. >>> >>> As for the output, literally it has no output at all. >>> >>> For example >>> >>> C:\Scratch> puppet help --verbose --debug --trace >>> >>> C:\Scratch> >>> >>> With only a moment''s delay between the two. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Puppet Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to puppet-users...@**googlegroups.com. >>> To post to this group, send email to puppet...@googlegroups.com. >>> >>> Visit this group at http://groups.google.com/**group/puppet-users<http://groups.google.com/group/puppet-users> >>> . >>> For more options, visit https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >> >> >> >> -- >> Rob Reynolds >> Developer, Puppet Labs >> >> Join us at PuppetConf 2014, September 23-24 in San Francisco >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscribe@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out. >-- Rob Reynolds Developer, Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
I am using the "start command prompt with puppet" command. I was able to verify this happening on both a physical machine and on a vm. However, after my initial question, we obtained and installed the release version of windows 8.1 and this seems to no longer be an issue. Perhaps something funky was happening with Windows 8.1 preview. Thanks for your time. Jason On Friday, October 18, 2013 1:24:24 PM UTC-4, Rob Reynolds wrote:> > That is interesting. It appears that the log output is not showing up on > your console. What console are you using? Can you verify this is happening > on more than one machine? > > > On Fri, Oct 18, 2013 at 7:27 AM, Jason Bray <jbray...@gmail.com<javascript:> > > wrote: > >> Well, that is exactly the issue. It doesn''t appear to crash in a visible >> way, there is simply no output for any command I give it. Although, every >> once in a while, it appears to work normally and shows output as expected. >> 90% of the time, the command hangs for a second or two then returns me to >> the command prompt with no output whatsoever. >> >> For example >> >> C:\Scratch> puppet apply test.pp --debug --verbose --trace >> >> C:\Scratch> >> >> >> Actually to make it even weirder, I think I might have been wrong about >> it crashing. For example when I run a simple manifest, >> >> file { ''C:\Scratch\foo.txt'': >> ensure => present, >> content => ''bar, >> } >> >> The command prompt looks like this: >> >> C:\Scratch> puppet apply test.pp --debug --verbose --trace >> >> C:\Scratch> >> >> However, when I do a dir, I see that the file has indeed been created. >> >> >> On Thursday, October 17, 2013 3:48:41 PM UTC-4, Rob Reynolds wrote: >> >>> Jason, >>> Sorry, I meant applying a catalog or running something that causes >>> puppet to crash in a visible way. Apologies for the miscommunication. >>> >>> >>> On Thu, Oct 17, 2013 at 12:58 PM, Jason Bray <jbray...@gmail.com> wrote: >>> >>>> Of course, sorry. >>>> >>>> Puppet 3.3.1 installed from an MSI, I believe the ruby version is >>>> 1.9.2, but I''m not 100% on that. >>>> >>>> As for the output, literally it has no output at all. >>>> >>>> For example >>>> >>>> C:\Scratch> puppet help --verbose --debug --trace >>>> >>>> C:\Scratch> >>>> >>>> With only a moment''s delay between the two. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Puppet Users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to puppet-users...@**googlegroups.com. >>>> To post to this group, send email to puppet...@googlegroups.com. >>>> >>>> Visit this group at http://groups.google.com/**group/puppet-users<http://groups.google.com/group/puppet-users> >>>> . >>>> For more options, visit https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>> . >>>> >>> >>> >>> >>> -- >>> Rob Reynolds >>> Developer, Puppet Labs >>> >>> Join us at PuppetConf 2014, September 23-24 in San Francisco >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users...@googlegroups.com <javascript:>. >> To post to this group, send email to puppet...@googlegroups.com<javascript:> >> . >> Visit this group at http://groups.google.com/group/puppet-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Rob Reynolds > Developer, Puppet Labs > > Join us at PuppetConf 2014, September 23-24 in San Francisco >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Good to hear that it was resolved with the RTM. :) On Mon, Oct 21, 2013 at 2:13 PM, Jason Bray <jbray.1982@gmail.com> wrote:> I am using the "start command prompt with puppet" command. I was able to > verify this happening on both a physical machine and on a vm. > > However, after my initial question, we obtained and installed the release > version of windows 8.1 and this seems to no longer be an issue. Perhaps > something funky was happening with Windows 8.1 preview. > > Thanks for your time. > > Jason > > > On Friday, October 18, 2013 1:24:24 PM UTC-4, Rob Reynolds wrote: > >> That is interesting. It appears that the log output is not showing up on >> your console. What console are you using? Can you verify this is happening >> on more than one machine? >> >> >> On Fri, Oct 18, 2013 at 7:27 AM, Jason Bray <jbray...@gmail.com> wrote: >> >>> Well, that is exactly the issue. It doesn''t appear to crash in a visible >>> way, there is simply no output for any command I give it. Although, every >>> once in a while, it appears to work normally and shows output as expected. >>> 90% of the time, the command hangs for a second or two then returns me to >>> the command prompt with no output whatsoever. >>> >>> For example >>> >>> C:\Scratch> puppet apply test.pp --debug --verbose --trace >>> >>> C:\Scratch> >>> >>> >>> Actually to make it even weirder, I think I might have been wrong about >>> it crashing. For example when I run a simple manifest, >>> >>> file { ''C:\Scratch\foo.txt'': >>> ensure => present, >>> content => ''bar, >>> } >>> >>> The command prompt looks like this: >>> >>> C:\Scratch> puppet apply test.pp --debug --verbose --trace >>> >>> C:\Scratch> >>> >>> However, when I do a dir, I see that the file has indeed been created. >>> >>> >>> On Thursday, October 17, 2013 3:48:41 PM UTC-4, Rob Reynolds wrote: >>> >>>> Jason, >>>> Sorry, I meant applying a catalog or running something that causes >>>> puppet to crash in a visible way. Apologies for the miscommunication. >>>> >>>> >>>> On Thu, Oct 17, 2013 at 12:58 PM, Jason Bray <jbray...@gmail.com>wrote: >>>> >>>>> Of course, sorry. >>>>> >>>>> Puppet 3.3.1 installed from an MSI, I believe the ruby version is >>>>> 1.9.2, but I''m not 100% on that. >>>>> >>>>> As for the output, literally it has no output at all. >>>>> >>>>> For example >>>>> >>>>> C:\Scratch> puppet help --verbose --debug --trace >>>>> >>>>> C:\Scratch> >>>>> >>>>> With only a moment''s delay between the two. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Puppet Users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to puppet-users...@**googlegroups.**com. >>>>> To post to this group, send email to puppet...@googlegroups.com. >>>>> >>>>> Visit this group at http://groups.google.com/**group**/puppet-users<http://groups.google.com/group/puppet-users> >>>>> . >>>>> For more options, visit https://groups.google.com/**grou**ps/opt_out<https://groups.google.com/groups/opt_out> >>>>> . >>>>> >>>> >>>> >>>> >>>> -- >>>> Rob Reynolds >>>> Developer, Puppet Labs >>>> >>>> Join us at PuppetConf 2014, September 23-24 in San Francisco >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Puppet Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to puppet-users...@**googlegroups.com. >>> To post to this group, send email to puppet...@googlegroups.com. >>> Visit this group at http://groups.google.com/**group/puppet-users<http://groups.google.com/group/puppet-users> >>> . >>> For more options, visit https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >> >> >> >> -- >> Rob Reynolds >> Developer, Puppet Labs >> >> Join us at PuppetConf 2014, September 23-24 in San Francisco >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscribe@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out. >-- Rob Reynolds Developer, Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.