Good to hear that it was resolved with the RTM. :)
On Mon, Oct 21, 2013 at 2:13 PM, Jason Bray jbray.1...@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,
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
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
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.1...@gmail.com wrote:
Well, that is exactly the issue. It doesn't
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
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.1...@gmail.com wrote:
Hello,
I've been
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.
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.1...@gmail.com wrote:
Of course, sorry.
Puppet 3.3.1 installed from an MSI, I believe the ruby
