FAQ
Hi all,

I have trouble installing puppet open source 3.2.3 from the msi package on
Windows 7 Home Basic.
The error message is "Service 'Puppet Agent' (puppet) failed to start.
Verify that you have sufficient privileges to start system services."

I am pretty sure it's not a privileges problem.
If (without closing the installer, as that would roll back everything) I
open Services and try to start Puppet Agent manually it fails to start with
"Error 1053: The service did not respond to the start or control request in
a timely fashion."

This may be a timeout problem (the hardware is a netbook), but I doubt it.

1) Is there a way to install Puppet without installing or auto-starting the
service? A checkbox in the installer would be nice.
2) Is there a way to avoid rolling back the whole installation if the
service failed to start? A yes/no dialog would be nice. "Yes, I will start
the service later manually, after I figure out what's wrong, thank you"
3) What could be causing this, what can I do to work around this?
I have tried adding registry key
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServicesPipeTimeout =
120000 (googling error 1053 led me to believe it might help, but it did not)

Then I tried to run Puppet directly (still without closing the installer):

C:\Program Files\Puppet Labs\Puppet\bin>puppet.bat
C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-dir-
0.3.7/lib/win32/dir.rb:54:in `strip': invalid byte sequence in US-ASCII
(Argumen
tError)
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
ms/win32-dir-0.3.7/lib/win32/dir.rb:54:in `block in <class:Dir>'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
ms/win32-dir-0.3.7/lib/win32/dir.rb:36:in `each'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
ms/win32-dir-0.3.7/lib/win32/dir.rb:36:in `<class:Dir>'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
ms/win32-dir-0.3.7/lib/win32/dir.rb:13:in `<top (required)>'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
.1/rubygems/custom_require.rb:60:in `require'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
.1/rubygems/custom_require.rb:60:in `rescue in require'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
.1/rubygems/custom_require.rb:35:in `require'
         from C:/Program Files/Puppet
Labs/Puppet/facter/lib/facter/util/config.r
b:44:in `<top (required)>'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
.1/rubygems/custom_require.rb:36:in `require'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
.1/rubygems/custom_require.rb:36:in `require'
         from C:/Program Files/Puppet
Labs/Puppet/facter/lib/facter/util/resoluti
on.rb:7:in `<top (required)>'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
.1/rubygems/custom_require.rb:36:in `require'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
.1/rubygems/custom_require.rb:36:in `require'
         from C:/Program Files/Puppet
Labs/Puppet/facter/lib/facter/util/fact.rb:
2:in `<top (required)>'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
.1/rubygems/custom_require.rb:36:in `require'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
.1/rubygems/custom_require.rb:36:in `require'
         from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter.rb:23:in
`<mo
dule:Facter>'
         from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter.rb:19:in
`<to
p (required)>'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
.1/rubygems/custom_require.rb:36:in `require'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
.1/rubygems/custom_require.rb:36:in `require'
         from C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet.rb:6:in
`<top
  (required)>'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
.1/rubygems/custom_require.rb:36:in `require'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
.1/rubygems/custom_require.rb:36:in `require'
         from C:/Program Files/Puppet
Labs/Puppet/puppet/lib/puppet/util/command_
line.rb:12:in `<top (required)>'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
.1/rubygems/custom_require.rb:36:in `require'
         from C:/Program Files/Puppet
Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
.1/rubygems/custom_require.rb:36:in `require'
         from C:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:3:in
`<main>'
I have no ruby experience so any help interpreting that would be welcome.

Ivan

--
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.

Search Discussions

  • Josh Cooper at Jul 17, 2013 at 4:52 pm

    On Wednesday, July 17, 2013 9:27:05 AM UTC-7, Иван Кадочников wrote:
    Hi all,

    I have trouble installing puppet open source 3.2.3 from the msi package on
    Windows 7 Home Basic.
    The error message is "Service 'Puppet Agent' (puppet) failed to start.
    Verify that you have sufficient privileges to start system services."

    I am pretty sure it's not a privileges problem.
    If (without closing the installer, as that would roll back everything) I
    open Services and try to start Puppet Agent manually it fails to start with
    "Error 1053: The service did not respond to the start or control request
    in a timely fashion."

    This may be a timeout problem (the hardware is a netbook), but I doubt it.

    1) Is there a way to install Puppet without installing or auto-starting
    the service? A checkbox in the installer would be nice.
    This is http://projects.puppetlabs.com/issues/18268

    2) Is there a way to avoid rolling back the whole installation if the
    service failed to start? A yes/no dialog would be nice. "Yes, I will start
    the service later manually, after I figure out what's wrong, thank you"
    We're using WiX to build our MSI. I'm not sure if there is an option to do
    this?

    3) What could be causing this, what can I do to work around this?
    I have tried adding registry key
    \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServicesPipeTimeout =
    120000 (googling error 1053 led me to believe it might help, but it did not)

    Then I tried to run Puppet directly (still without closing the installer):

    C:\Program Files\Puppet Labs\Puppet\bin>puppet.bat
    C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-dir-
    0.3.7/lib/win32/dir.rb:54:in `strip': invalid byte sequence in US-ASCII
    (Argumen
    tError)
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/dir.rb:54:in `block in <class:Dir>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/dir.rb:36:in `each'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/dir.rb:36:in `<class:Dir>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/dir.rb:13:in `<top (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:60:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:60:in `rescue in require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:35:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/config.r
    b:44:in `<top (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/resoluti
    on.rb:7:in `<top (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/fact.rb:
    2:in `<top (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter.rb:23:in `<mo
    dule:Facter>'
    from C:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter.rb:19:in `<to
    p (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet.rb:6:in
    `<top
    (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/puppet/lib/puppet/util/command_
    line.rb:12:in `<top (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:3:in
    `<main>'
    I have no ruby experience so any help interpreting that would be welcome.

    Ivan
    The error in win32-dir gem is related to
    https://projects.puppetlabs.com/issues/17010. The version of win32-dir gem
    we are using (0.3.7) uses the ANSI win32 apis, e.g. SHGetFolderLocationA
    and does not work correctly on locales whose paths are not ascii compatible.

    The newer win32-dir gems 0.4.x correctly use the wide versions, e.g.
    SHGetFolderLocationW, but there was still an issue preventing us from
    resolving #17010. I filed an upstream PR, which was recently merged
    https://github.com/djberg96/win32-dir/blob/7664900064cce9e606bfb67842fb98f66cc60ae2/lib/win32/dir.rb.

    As soo as Dan releases 0.4.3, we will move to that version, as currently
    this issue prevents facter and puppet from working in many non-ascii based
    locales. In the meantime, you might want to try cloning the latest
    win32-dir gem (from the ffi branch) and installing that.

    Josh

    --
    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.
  • Иван Кадочников at Jul 22, 2013 at 8:05 am
    Thanks for the information, I somehow managed to not notice your response
    for several days.
    On Wednesday, July 17, 2013 6:52:43 PM UTC+2, Josh Cooper wrote:


    On Wednesday, July 17, 2013 9:27:05 AM UTC-7, Иван Кадочников wrote:

    Hi all,

    I have trouble installing puppet open source 3.2.3 from the msi package
    on Windows 7 Home Basic.
    The error message is "Service 'Puppet Agent' (puppet) failed to start.
    Verify that you have sufficient privileges to start system services."

    I am pretty sure it's not a privileges problem.
    If (without closing the installer, as that would roll back everything) I
    open Services and try to start Puppet Agent manually it fails to start with
    "Error 1053: The service did not respond to the start or control request
    in a timely fashion."

    This may be a timeout problem (the hardware is a netbook), but I doubt it.

    1) Is there a way to install Puppet without installing or auto-starting
    the service? A checkbox in the installer would be nice.
    This is http://projects.puppetlabs.com/issues/18268

    2) Is there a way to avoid rolling back the whole installation if the
    service failed to start? A yes/no dialog would be nice. "Yes, I will start
    the service later manually, after I figure out what's wrong, thank you"
    We're using WiX to build our MSI. I'm not sure if there is an option to do
    this?
    A search lead me to the ServiceInstall component parameter Vital, which
    controls if failing to start the service fails the whole install. On the
    other hand, changing this would surprise people doing automated setup. And
    now that I know there's a reason for the service not working I don't care
    about preventing rollback that much...

    3) What could be causing this, what can I do to work around this?
    I have tried adding registry key
    \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServicesPipeTimeout =
    120000 (googling error 1053 led me to believe it might help, but it did not)

    Then I tried to run Puppet directly (still without closing the installer):

    C:\Program Files\Puppet Labs\Puppet\bin>puppet.bat
    C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-dir-
    0.3.7/lib/win32/dir.rb:54:in `strip': invalid byte sequence in US-ASCII
    (Argumen
    tError)
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/dir.rb:54:in `block in <class:Dir>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/dir.rb:36:in `each'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/dir.rb:36:in `<class:Dir>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/dir.rb:13:in `<top (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:60:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:60:in `rescue in require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:35:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/config.r
    b:44:in `<top (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/resoluti
    on.rb:7:in `<top (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/fact.rb:
    2:in `<top (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter.rb:23:in `<mo
    dule:Facter>'
    from C:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter.rb:19:in `<to
    p (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/puppet/lib/puppet.rb:6:in `<top
    (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/puppet/lib/puppet/util/command_
    line.rb:12:in `<top (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:3:in
    `<main>'
    I have no ruby experience so any help interpreting that would be welcome.

    Ivan
    The error in win32-dir gem is related to
    https://projects.puppetlabs.com/issues/17010. The version of win32-dir
    gem we are using (0.3.7) uses the ANSI win32 apis, e.g.
    SHGetFolderLocationA and does not work correctly on locales whose paths are
    not ascii compatible.

    The newer win32-dir gems 0.4.x correctly use the wide versions, e.g.
    SHGetFolderLocationW, but there was still an issue preventing us from
    resolving #17010. I filed an upstream PR, which was recently merged
    https://github.com/djberg96/win32-dir/blob/7664900064cce9e606bfb67842fb98f66cc60ae2/lib/win32/dir.rb
    .

    As soo as Dan releases 0.4.3, we will move to that version, as currently
    this issue prevents facter and puppet from working in many non-ascii based
    locales. In the meantime, you might want to try cloning the latest
    win32-dir gem (from the ffi branch) and installing that.

    Josh
    So I should wait for win32-dir 0.4.3 to be released and for the
    corresponding Puppet update?
    Good enough for me, more time to play with the linux version.

    Ivan

    --
    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.
  • Josh Cooper at Aug 1, 2013 at 4:42 am
    Hi Ivan,

    On Mon, Jul 22, 2013 at 1:05 AM, Иван Кадочников wrote:

    Thanks for the information, I somehow managed to not notice your response
    for several days.

    On Wednesday, July 17, 2013 6:52:43 PM UTC+2, Josh Cooper wrote:


    On Wednesday, July 17, 2013 9:27:05 AM UTC-7, Иван Кадочников wrote:

    Hi all,

    I have trouble installing puppet open source 3.2.3 from the msi package
    on Windows 7 Home Basic.
    The error message is "Service 'Puppet Agent' (puppet) failed to start.
    Verify that you have sufficient privileges to start system services."

    I am pretty sure it's not a privileges problem.
    If (without closing the installer, as that would roll back everything) I
    open Services and try to start Puppet Agent manually it fails to start with
    "Error 1053: The service did not respond to the start or control request
    in a timely fashion."

    This may be a timeout problem (the hardware is a netbook), but I doubt
    it.

    1) Is there a way to install Puppet without installing or auto-starting
    the service? A checkbox in the installer would be nice.
    This is http://projects.puppetlabs.**com/issues/18268<http://projects.puppetlabs.com/issues/18268>

    2) Is there a way to avoid rolling back the whole installation if the
    service failed to start? A yes/no dialog would be nice. "Yes, I will start
    the service later manually, after I figure out what's wrong, thank you"
    We're using WiX to build our MSI. I'm not sure if there is an option to
    do this?
    A search lead me to the ServiceInstall component parameter Vital, which
    controls if failing to start the service fails the whole install. On the
    other hand, changing this would surprise people doing automated setup. And
    now that I know there's a reason for the service not working I don't care
    about preventing rollback that much...

    3) What could be causing this, what can I do to work around this?
    I have tried adding registry key \HKEY_LOCAL_MACHINE\SYSTEM\**
    CurrentControlSet\Control\**ServicesPipeTimeout = 120000 (googling
    error 1053 led me to believe it might help, but it did not)

    Then I tried to run Puppet directly (still without closing the
    installer):

    C:\Program Files\Puppet Labs\Puppet\bin>puppet.bat
    C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/gems/win32-dir-
    0.3.7/lib/win32/dir.rb:54:in `strip': invalid byte sequence in US-ASCII
    (Argumen
    tError)
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:54:in `block in <class:Dir>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:36:in `each'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:36:in `<class:Dir>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:13:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**60:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**60:in `rescue in require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**35:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter/**
    util/config.r
    b:44:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter/**
    util/resoluti
    on.rb:7:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter/**
    util/fact.rb:
    2:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter.**rb:23:in
    `<mo
    dule:Facter>'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter.**rb:19:in
    `<to
    p (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet.**rb:6:in
    `<top
    (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/**
    util/command_
    line.rb:12:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:**3:in
    `<main>'
    I have no ruby experience so any help interpreting that would be welcome.

    Ivan
    The error in win32-dir gem is related to https://projects.puppetlabs.**
    com/issues/17010 <https://projects.puppetlabs.com/issues/17010>. The
    version of win32-dir gem we are using (0.3.7) uses the ANSI win32 apis,
    e.g. SHGetFolderLocationA and does not work correctly on locales whose
    paths are not ascii compatible.

    The newer win32-dir gems 0.4.x correctly use the wide versions, e.g.
    SHGetFolderLocationW, but there was still an issue preventing us from
    resolving #17010. I filed an upstream PR, which was recently merged
    https://github.com/djberg96/**win32-dir/blob/**
    7664900064cce9e606bfb67842fb98**f66cc60ae2/lib/win32/dir.rb<https://github.com/djberg96/win32-dir/blob/7664900064cce9e606bfb67842fb98f66cc60ae2/lib/win32/dir.rb>
    .

    As soo as Dan releases 0.4.3, we will move to that version, as currently
    this issue prevents facter and puppet from working in many non-ascii based
    locales. In the meantime, you might want to try cloning the latest
    win32-dir gem (from the ffi branch) and installing that.

    Josh
    So I should wait for win32-dir 0.4.3 to be released and for the
    corresponding Puppet update?
    Good enough for me, more time to play with the linux version.
    Dan Berger has released an updated win32-dir gem with my patch in it. You
    can just run `gem update win32-dir` and you should be good. Alternatively,
    you can wait for the next puppet release (3.2.4 or 3.3.0 whichever comes
    first).

    Josh

    --
    Josh Cooper
    Developer, Puppet Labs

    *Join us at PuppetConf 2013, August 22-23 in San Francisco - *
    http://bit.ly/pupconf13*
    **Register now and take advantage of the Final Countdown discount - save
    15%!*

    --
    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.
  • Иван Кадочников at Aug 4, 2013 at 5:28 pm
    Thanks for the tip, I just tried it, now I get a different error, which is
    usually a good sign:

    c:\Program Files\Puppet Labs\Puppet\bin>puppet.bat
    c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-dir-
    0.4.3/lib/win32/dir.rb:95:in `encode': "\xC8" to UTF-8 in conversion from
    ASCII-
    8BIT to UTF-8 to IBM866 (Encoding::UndefinedConversionError)
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.4.3/lib/win32/dir.rb:95:in `block in <class:Dir>'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.4.3/lib/win32/dir.rb:74:in `each'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.4.3/lib/win32/dir.rb:74:in `<class:Dir>'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.4.3/lib/win32/dir.rb:5:in `<top (required)>'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:60:in `require'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:60:in `rescue in require'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:35:in `require'
             from c:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/config.r
    b:44:in `<top (required)>'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
             from c:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/resoluti
    on.rb:7:in `<top (required)>'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
             from c:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/fact.rb:
    2:in `<top (required)>'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
             from c:/Program Files/Puppet Labs/Puppet/facter/lib/facter.rb:23:in
    `<mo
    dule:Facter>'
             from c:/Program Files/Puppet Labs/Puppet/facter/lib/facter.rb:19:in
    `<to
    p (required)>'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
             from c:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet.rb:6:in
    `<top
      (required)>'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
             from c:/Program Files/Puppet
    Labs/Puppet/puppet/lib/puppet/util/command_
    line.rb:12:in `<top (required)>'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
             from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
             from c:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:3:in
    `<main>'

    Regards,
    Ivan
    On Thursday, August 1, 2013 6:42:16 AM UTC+2, Josh Cooper wrote:

    Hi Ivan,


    On Mon, Jul 22, 2013 at 1:05 AM, Иван Кадочников <fizma...@gmail.com<javascript:>
    wrote:
    Thanks for the information, I somehow managed to not notice your response
    for several days.

    On Wednesday, July 17, 2013 6:52:43 PM UTC+2, Josh Cooper wrote:


    On Wednesday, July 17, 2013 9:27:05 AM UTC-7, Иван Кадочников wrote:

    Hi all,

    I have trouble installing puppet open source 3.2.3 from the msi package
    on Windows 7 Home Basic.
    The error message is "Service 'Puppet Agent' (puppet) failed to start.
    Verify that you have sufficient privileges to start system services."

    I am pretty sure it's not a privileges problem.
    If (without closing the installer, as that would roll back everything)
    I open Services and try to start Puppet Agent manually it fails to start
    with
    "Error 1053: The service did not respond to the start or control
    request in a timely fashion."

    This may be a timeout problem (the hardware is a netbook), but I doubt
    it.

    1) Is there a way to install Puppet without installing or auto-starting
    the service? A checkbox in the installer would be nice.
    This is http://projects.puppetlabs.**com/issues/18268<http://projects.puppetlabs.com/issues/18268>

    2) Is there a way to avoid rolling back the whole installation if the
    service failed to start? A yes/no dialog would be nice. "Yes, I will start
    the service later manually, after I figure out what's wrong, thank you"
    We're using WiX to build our MSI. I'm not sure if there is an option to
    do this?
    A search lead me to the ServiceInstall component parameter Vital, which
    controls if failing to start the service fails the whole install. On the
    other hand, changing this would surprise people doing automated setup. And
    now that I know there's a reason for the service not working I don't care
    about preventing rollback that much...

    3) What could be causing this, what can I do to work around this?
    I have tried adding registry key \HKEY_LOCAL_MACHINE\SYSTEM\**
    CurrentControlSet\Control\**ServicesPipeTimeout = 120000 (googling
    error 1053 led me to believe it might help, but it did not)

    Then I tried to run Puppet directly (still without closing the
    installer):

    C:\Program Files\Puppet Labs\Puppet\bin>puppet.bat
    C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/gems/win32-dir-
    0.3.7/lib/win32/dir.rb:54:in `strip': invalid byte sequence in US-ASCII
    (Argumen
    tError)
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:54:in `block in <class:Dir>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:36:in `each'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:36:in `<class:Dir>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:13:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**60:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**60:in `rescue in require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**35:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter/**
    util/config.r
    b:44:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter/**
    util/resoluti
    on.rb:7:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter/**
    util/fact.rb:
    2:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter.**rb:23:in
    `<mo
    dule:Facter>'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter.**rb:19:in
    `<to
    p (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet.**rb:6:in
    `<top
    (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/**
    util/command_
    line.rb:12:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:**3:in
    `<main>'
    I have no ruby experience so any help interpreting that would be
    welcome.

    Ivan
    The error in win32-dir gem is related to https://projects.puppetlabs.**
    com/issues/17010 <https://projects.puppetlabs.com/issues/17010>. The
    version of win32-dir gem we are using (0.3.7) uses the ANSI win32 apis,
    e.g. SHGetFolderLocationA and does not work correctly on locales whose
    paths are not ascii compatible.

    The newer win32-dir gems 0.4.x correctly use the wide versions, e.g.
    SHGetFolderLocationW, but there was still an issue preventing us from
    resolving #17010. I filed an upstream PR, which was recently merged
    https://github.com/djberg96/**win32-dir/blob/**
    7664900064cce9e606bfb67842fb98**f66cc60ae2/lib/win32/dir.rb<https://github.com/djberg96/win32-dir/blob/7664900064cce9e606bfb67842fb98f66cc60ae2/lib/win32/dir.rb>
    .

    As soo as Dan releases 0.4.3, we will move to that version, as currently
    this issue prevents facter and puppet from working in many non-ascii based
    locales. In the meantime, you might want to try cloning the latest
    win32-dir gem (from the ffi branch) and installing that.

    Josh
    So I should wait for win32-dir 0.4.3 to be released and for the
    corresponding Puppet update?
    Good enough for me, more time to play with the linux version.
    Dan Berger has released an updated win32-dir gem with my patch in it. You
    can just run `gem update win32-dir` and you should be good. Alternatively,
    you can wait for the next puppet release (3.2.4 or 3.3.0 whichever comes
    first).

    Josh

    --
    Josh Cooper
    Developer, Puppet Labs

    *Join us at PuppetConf 2013, August 22-23 in San Francisco - *
    http://bit.ly/pupconf13*
    **Register now and take advantage of the Final Countdown discount - save
    15%!*
    --
    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.
  • Tinnycloud at Aug 26, 2013 at 2:39 pm
    I met exactly the same error when installing puppet 3.2.4 with win32-dir
    0.4.3

    Is their a workable version?


    在 2013年8月5日星期一UTC+8上午1时27分59秒,Иван Кадочников写道:
    Thanks for the tip, I just tried it, now I get a different error, which is
    usually a good sign:

    c:\Program Files\Puppet Labs\Puppet\bin>puppet.bat
    c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-dir-
    0.4.3/lib/win32/dir.rb:95:in `encode': "\xC8" to UTF-8 in conversion from
    ASCII-
    8BIT to UTF-8 to IBM866 (Encoding::UndefinedConversionError)
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.4.3/lib/win32/dir.rb:95:in `block in <class:Dir>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.4.3/lib/win32/dir.rb:74:in `each'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.4.3/lib/win32/dir.rb:74:in `<class:Dir>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.4.3/lib/win32/dir.rb:5:in `<top (required)>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:60:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:60:in `rescue in require'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:35:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/config.r
    b:44:in `<top (required)>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/resoluti
    on.rb:7:in `<top (required)>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/fact.rb:
    2:in `<top (required)>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter.rb:23:in `<mo
    dule:Facter>'
    from c:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter.rb:19:in `<to
    p (required)>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet.rb:6:in
    `<top
    (required)>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/puppet/lib/puppet/util/command_
    line.rb:12:in `<top (required)>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:3:in
    `<main>'

    Regards,
    Ivan
    On Thursday, August 1, 2013 6:42:16 AM UTC+2, Josh Cooper wrote:

    Hi Ivan,

    On Mon, Jul 22, 2013 at 1:05 AM, Иван Кадочников wrote:

    Thanks for the information, I somehow managed to not notice your
    response for several days.

    On Wednesday, July 17, 2013 6:52:43 PM UTC+2, Josh Cooper wrote:


    On Wednesday, July 17, 2013 9:27:05 AM UTC-7, Иван Кадочников wrote:

    Hi all,

    I have trouble installing puppet open source 3.2.3 from the msi
    package on Windows 7 Home Basic.
    The error message is "Service 'Puppet Agent' (puppet) failed to start.
    Verify that you have sufficient privileges to start system services."

    I am pretty sure it's not a privileges problem.
    If (without closing the installer, as that would roll back everything)
    I open Services and try to start Puppet Agent manually it fails to start
    with
    "Error 1053: The service did not respond to the start or control
    request in a timely fashion."

    This may be a timeout problem (the hardware is a netbook), but I doubt
    it.

    1) Is there a way to install Puppet without installing or
    auto-starting the service? A checkbox in the installer would be nice.
    This is http://projects.puppetlabs.**com/issues/18268<http://projects.puppetlabs.com/issues/18268>

    2) Is there a way to avoid rolling back the whole installation if the
    service failed to start? A yes/no dialog would be nice. "Yes, I will start
    the service later manually, after I figure out what's wrong, thank you"
    We're using WiX to build our MSI. I'm not sure if there is an option to
    do this?
    A search lead me to the ServiceInstall component parameter Vital, which
    controls if failing to start the service fails the whole install. On the
    other hand, changing this would surprise people doing automated setup. And
    now that I know there's a reason for the service not working I don't care
    about preventing rollback that much...

    3) What could be causing this, what can I do to work around this?
    I have tried adding registry key \HKEY_LOCAL_MACHINE\SYSTEM\**
    CurrentControlSet\Control\**ServicesPipeTimeout = 120000 (googling
    error 1053 led me to believe it might help, but it did not)

    Then I tried to run Puppet directly (still without closing the
    installer):

    C:\Program Files\Puppet Labs\Puppet\bin>puppet.bat
    C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/gems/win32-dir-
    0.3.7/lib/win32/dir.rb:54:in `strip': invalid byte sequence in
    US-ASCII (Argumen
    tError)
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:54:in `block in <class:Dir>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:36:in `each'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:36:in `<class:Dir>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:13:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**60:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**60:in `rescue in require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**35:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter/**
    util/config.r
    b:44:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter/**
    util/resoluti
    on.rb:7:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter/**
    util/fact.rb:
    2:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter.**rb:23:in
    `<mo
    dule:Facter>'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter.**rb:19:in
    `<to
    p (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet.**rb:6:in
    `<top
    (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/**
    util/command_
    line.rb:12:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:**3:in
    `<main>'
    I have no ruby experience so any help interpreting that would be
    welcome.

    Ivan
    The error in win32-dir gem is related to https://projects.puppetlabs.**
    com/issues/17010 <https://projects.puppetlabs.com/issues/17010>. The
    version of win32-dir gem we are using (0.3.7) uses the ANSI win32 apis,
    e.g. SHGetFolderLocationA and does not work correctly on locales whose
    paths are not ascii compatible.

    The newer win32-dir gems 0.4.x correctly use the wide versions, e.g.
    SHGetFolderLocationW, but there was still an issue preventing us from
    resolving #17010. I filed an upstream PR, which was recently merged
    https://github.com/djberg96/**win32-dir/blob/**
    7664900064cce9e606bfb67842fb98**f66cc60ae2/lib/win32/dir.rb<https://github.com/djberg96/win32-dir/blob/7664900064cce9e606bfb67842fb98f66cc60ae2/lib/win32/dir.rb>
    .

    As soo as Dan releases 0.4.3, we will move to that version, as
    currently this issue prevents facter and puppet from working in many
    non-ascii based locales. In the meantime, you might want to try cloning the
    latest win32-dir gem (from the ffi branch) and installing that.

    Josh
    So I should wait for win32-dir 0.4.3 to be released and for the
    corresponding Puppet update?
    Good enough for me, more time to play with the linux version.
    Dan Berger has released an updated win32-dir gem with my patch in it. You
    can just run `gem update win32-dir` and you should be good. Alternatively,
    you can wait for the next puppet release (3.2.4 or 3.3.0 whichever comes
    first).

    Josh

    --
    Josh Cooper
    Developer, Puppet Labs

    *Join us at PuppetConf 2013, August 22-23 in San Francisco - *
    http://bit.ly/pupconf13*
    **Register now and take advantage of the Final Countdown discount - save
    15%!*
    --
    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.
  • MunsterNet at Aug 28, 2013 at 12:19 pm
    Hi,

    Same here, I'm trying to run the agent on a Windows machine installed in
    French:

    C:/Program Files (x86)/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-dir-0.4.3/lib/win32/dir.rb:95:in `enco
    de': "\xE9" to UTF-8 in conversion from ASCII-8BIT to UTF-8 to CP850 (Encoding::UndefinedConversionError)
             from C:/Program Files (x86)/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-dir-0.4.3/lib/win32/dir.r
    b:95:in `block in <class:Dir>'
             from C:/Program Files (x86)/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-dir-0.4.3/lib/win32/dir.r
    b:74:in `each'
             from C:/Program Files (x86)/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-dir-0.4.3/lib/win32/dir.r
    b:74:in `<class:Dir>'
             from C:/Program Files (x86)/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-dir-0.4.3/lib/win32/dir.r
    b:5:in `<top (required)>'
             from C:/Program Files (x86)/Puppet Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:60:i
    n `require'
             from C:/Program Files (x86)/Puppet Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:60:i
    n `rescue in require'
             from C:/Program Files (x86)/Puppet Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:35:i
    n `require'
             from C:/Program Files (x86)/Puppet Labs/Puppet/service/daemon.rb:5:in `<main>'


    I am also running 3.2.4 and win32-dir 0.4.3...

    On Monday, August 26, 2013 2:22:27 PM UTC+2, tinny...@gmail.com wrote:

    I met exactly the same error when installing puppet 3.2.4 with win32-dir
    0.4.3

    Is their a workable version?


    在 2013年8月5日星期一UTC+8上午1时27分59秒,Иван Кадочников写道:
    Thanks for the tip, I just tried it, now I get a different error, which
    is usually a good sign:

    c:\Program Files\Puppet Labs\Puppet\bin>puppet.bat
    c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-dir-
    0.4.3/lib/win32/dir.rb:95:in `encode': "\xC8" to UTF-8 in conversion from
    ASCII-
    8BIT to UTF-8 to IBM866 (Encoding::UndefinedConversionError)
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.4.3/lib/win32/dir.rb:95:in `block in <class:Dir>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.4.3/lib/win32/dir.rb:74:in `each'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.4.3/lib/win32/dir.rb:74:in `<class:Dir>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.4.3/lib/win32/dir.rb:5:in `<top (required)>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:60:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:60:in `rescue in require'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:35:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/config.r
    b:44:in `<top (required)>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/resoluti
    on.rb:7:in `<top (required)>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/fact.rb:
    2:in `<top (required)>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter.rb:23:in `<mo
    dule:Facter>'
    from c:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter.rb:19:in `<to
    p (required)>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/puppet/lib/puppet.rb:6:in `<top
    (required)>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/puppet/lib/puppet/util/command_
    line.rb:12:in `<top (required)>'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from c:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:3:in
    `<main>'

    Regards,
    Ivan
    On Thursday, August 1, 2013 6:42:16 AM UTC+2, Josh Cooper wrote:

    Hi Ivan,

    On Mon, Jul 22, 2013 at 1:05 AM, Иван Кадочников wrote:

    Thanks for the information, I somehow managed to not notice your
    response for several days.

    On Wednesday, July 17, 2013 6:52:43 PM UTC+2, Josh Cooper wrote:


    On Wednesday, July 17, 2013 9:27:05 AM UTC-7, Иван Кадочников wrote:

    Hi all,

    I have trouble installing puppet open source 3.2.3 from the msi
    package on Windows 7 Home Basic.
    The error message is "Service 'Puppet Agent' (puppet) failed to
    start. Verify that you have sufficient privileges to start system services."

    I am pretty sure it's not a privileges problem.
    If (without closing the installer, as that would roll back
    everything) I open Services and try to start Puppet Agent manually it fails
    to start with
    "Error 1053: The service did not respond to the start or control
    request in a timely fashion."

    This may be a timeout problem (the hardware is a netbook), but I
    doubt it.

    1) Is there a way to install Puppet without installing or
    auto-starting the service? A checkbox in the installer would be nice.
    This is http://projects.puppetlabs.**com/issues/18268<http://projects.puppetlabs.com/issues/18268>

    2) Is there a way to avoid rolling back the whole installation if the
    service failed to start? A yes/no dialog would be nice. "Yes, I will start
    the service later manually, after I figure out what's wrong, thank you"
    We're using WiX to build our MSI. I'm not sure if there is an option
    to do this?
    A search lead me to the ServiceInstall component parameter Vital, which
    controls if failing to start the service fails the whole install. On the
    other hand, changing this would surprise people doing automated setup. And
    now that I know there's a reason for the service not working I don't care
    about preventing rollback that much...

    3) What could be causing this, what can I do to work around this?
    I have tried adding registry key \HKEY_LOCAL_MACHINE\SYSTEM\**
    CurrentControlSet\Control\**ServicesPipeTimeout = 120000 (googling
    error 1053 led me to believe it might help, but it did not)

    Then I tried to run Puppet directly (still without closing the
    installer):

    C:\Program Files\Puppet Labs\Puppet\bin>puppet.bat
    C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/gems/win32-dir-
    0.3.7/lib/win32/dir.rb:54:in `strip': invalid byte sequence in
    US-ASCII (Argumen
    tError)
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:54:in `block in <class:Dir>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:36:in `each'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:36:in `<class:Dir>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:13:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**60:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**60:in `rescue in require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**35:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter/**
    util/config.r
    b:44:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter/**
    util/resoluti
    on.rb:7:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter/**
    util/fact.rb:
    2:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter.**rb:23:in
    `<mo
    dule:Facter>'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter.**rb:19:in
    `<to
    p (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet.**rb:6:in
    `<top
    (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/**
    util/command_
    line.rb:12:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:**3:in
    `<main>'
    I have no ruby experience so any help interpreting that would be
    welcome.

    Ivan
    The error in win32-dir gem is related to https://projects.puppetlabs.*
    *com/issues/17010 <https://projects.puppetlabs.com/issues/17010>. The
    version of win32-dir gem we are using (0.3.7) uses the ANSI win32 apis,
    e.g. SHGetFolderLocationA and does not work correctly on locales whose
    paths are not ascii compatible.

    The newer win32-dir gems 0.4.x correctly use the wide versions, e.g.
    SHGetFolderLocationW, but there was still an issue preventing us from
    resolving #17010. I filed an upstream PR, which was recently merged
    https://github.com/djberg96/**win32-dir/blob/**
    7664900064cce9e606bfb67842fb98**f66cc60ae2/lib/win32/dir.rb<https://github.com/djberg96/win32-dir/blob/7664900064cce9e606bfb67842fb98f66cc60ae2/lib/win32/dir.rb>
    .

    As soo as Dan releases 0.4.3, we will move to that version, as
    currently this issue prevents facter and puppet from working in many
    non-ascii based locales. In the meantime, you might want to try cloning the
    latest win32-dir gem (from the ffi branch) and installing that.

    Josh
    So I should wait for win32-dir 0.4.3 to be released and for the
    corresponding Puppet update?
    Good enough for me, more time to play with the linux version.
    Dan Berger has released an updated win32-dir gem with my patch in it.
    You can just run `gem update win32-dir` and you should be good.
    Alternatively, you can wait for the next puppet release (3.2.4 or 3.3.0
    whichever comes first).

    Josh

    --
    Josh Cooper
    Developer, Puppet Labs

    *Join us at PuppetConf 2013, August 22-23 in San Francisco - *
    http://bit.ly/pupconf13*
    **Register now and take advantage of the Final Countdown discount -
    save 15%!*
    --
    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.
  • Eugen at Oct 6, 2013 at 4:05 pm
    Same stuff for russian windows
    Please help us )

    среда, 17 июля 2013 г., 20:27:05 UTC+4 пользователь Иван Кадочников написал:
    Hi all,

    I have trouble installing puppet open source 3.2.3 from the msi package on
    Windows 7 Home Basic.
    The error message is "Service 'Puppet Agent' (puppet) failed to start.
    Verify that you have sufficient privileges to start system services."

    I am pretty sure it's not a privileges problem.
    If (without closing the installer, as that would roll back everything) I
    open Services and try to start Puppet Agent manually it fails to start with
    "Error 1053: The service did not respond to the start or control request
    in a timely fashion."

    This may be a timeout problem (the hardware is a netbook), but I doubt it.

    1) Is there a way to install Puppet without installing or auto-starting
    the service? A checkbox in the installer would be nice.
    2) Is there a way to avoid rolling back the whole installation if the
    service failed to start? A yes/no dialog would be nice. "Yes, I will start
    the service later manually, after I figure out what's wrong, thank you"
    3) What could be causing this, what can I do to work around this?
    I have tried adding registry key
    \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServicesPipeTimeout =
    120000 (googling error 1053 led me to believe it might help, but it did not)

    Then I tried to run Puppet directly (still without closing the installer):

    C:\Program Files\Puppet Labs\Puppet\bin>puppet.bat
    C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-dir-
    0.3.7/lib/win32/dir.rb:54:in `strip': invalid byte sequence in US-ASCII
    (Argumen
    tError)
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/dir.rb:54:in `block in <class:Dir>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/dir.rb:36:in `each'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/dir.rb:36:in `<class:Dir>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/dir.rb:13:in `<top (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:60:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:60:in `rescue in require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:35:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/config.r
    b:44:in `<top (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/resoluti
    on.rb:7:in `<top (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter/util/fact.rb:
    2:in `<top (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter.rb:23:in `<mo
    dule:Facter>'
    from C:/Program Files/Puppet
    Labs/Puppet/facter/lib/facter.rb:19:in `<to
    p (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet.rb:6:in
    `<top
    (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/puppet/lib/puppet/util/command_
    line.rb:12:in `<top (required)>'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet
    Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
    .1/rubygems/custom_require.rb:36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:3:in
    `<main>'
    I have no ruby experience so any help interpreting that would be welcome.

    Ivan
    --
    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 at Oct 7, 2013 at 6:32 pm
    We believe we have fixed these issues with the installer in the version
    that is coming out soon. Here was the issue -
    https://projects.puppetlabs.com/issues/22493

    Thanks!

    On Sun, Oct 6, 2013 at 9:04 AM, eugen wrote:

    Same stuff for russian windows
    Please help us )

    среда, 17 июля 2013 г., 20:27:05 UTC+4 пользователь Иван Кадочников
    написал:
    Hi all,

    I have trouble installing puppet open source 3.2.3 from the msi package
    on Windows 7 Home Basic.
    The error message is "Service 'Puppet Agent' (puppet) failed to start.
    Verify that you have sufficient privileges to start system services."

    I am pretty sure it's not a privileges problem.
    If (without closing the installer, as that would roll back everything) I
    open Services and try to start Puppet Agent manually it fails to start with
    "Error 1053: The service did not respond to the start or control request
    in a timely fashion."

    This may be a timeout problem (the hardware is a netbook), but I doubt it.

    1) Is there a way to install Puppet without installing or auto-starting
    the service? A checkbox in the installer would be nice.
    2) Is there a way to avoid rolling back the whole installation if the
    service failed to start? A yes/no dialog would be nice. "Yes, I will start
    the service later manually, after I figure out what's wrong, thank you"
    3) What could be causing this, what can I do to work around this?
    I have tried adding registry key \HKEY_LOCAL_MACHINE\SYSTEM\**
    CurrentControlSet\Control\**ServicesPipeTimeout = 120000 (googling error
    1053 led me to believe it might help, but it did not)

    Then I tried to run Puppet directly (still without closing the installer):

    C:\Program Files\Puppet Labs\Puppet\bin>puppet.bat
    C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/gems/win32-dir-
    0.3.7/lib/win32/dir.rb:54:in `strip': invalid byte sequence in US-ASCII
    (Argumen
    tError)
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:54:in `block in <class:Dir>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:36:in `each'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:36:in `<class:Dir>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    gems/1.9.1/ge
    ms/win32-dir-0.3.7/lib/win32/**dir.rb:13:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**60:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**60:in `rescue in require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**35:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter/**
    util/config.r
    b:44:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter/**
    util/resoluti
    on.rb:7:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter/**
    util/fact.rb:
    2:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter.**rb:23:in
    `<mo
    dule:Facter>'
    from C:/Program Files/Puppet Labs/Puppet/facter/lib/facter.**rb:19:in
    `<to
    p (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet.**rb:6:in
    `<top
    (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/**
    util/command_
    line.rb:12:in `<top (required)>'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/**
    site_ruby/1.9
    .1/rubygems/custom_require.rb:**36:in `require'
    from C:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:**3:in
    `<main>'
    I have no ruby experience so any help interpreting that would be welcome.

    Ivan
    --
    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.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppuppet-users @
categoriespuppet
postedJul 17, '13 at 4:29p
activeOct 7, '13 at 6:32p
posts9
users6
websitepuppetlabs.com

People

Translate

site design / logo © 2022 Grokbase