Hi All,
For some reason, I''m unable to manage cron resources on my CentOS5
server:
manifest:
cron { "test":
command => ''/bin/true'',
user => ''root'',
hour => ''1'',
}
And when I try to run this via puppetmasterd:
info: Caching catalog for ny-dev84.domain.com
err: Could not prefetch package provider ''yum'': Execution of
''/usr/
local/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/
yumhelper.py'' returned 1: <type
''exceptions.AttributeError''>
info: Applying configuration version ''1264214417''
notice: //crontab::puppet_runner/Cron[test]/ensure: created
"-":5: bad command
errors in crontab file, can''t install.
notice: Finished catalog run in 3.69 seconds
There are two things here that confuse me. 1: what''s the deal with the
''could not prefetch package provider'' and 2: why does
"/bin/true"
result in "bad command"?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
robbyt wrote:> For some reason, I''m unable to manage cron resources on my CentOS5 > server: > > manifest: > > cron { "test": > command => ''/bin/true'', > user => ''root'', > hour => ''1'', > } > > And when I try to run this via puppetmasterd: > > info: Caching catalog for ny-dev84.domain.com > err: Could not prefetch package provider ''yum'': Execution of ''/usr/ > local/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/ > yumhelper.py'' returned 1: <type ''exceptions.AttributeError''> > > info: Applying configuration version ''1264214417'' > notice: //crontab::puppet_runner/Cron[test]/ensure: created > "-":5: bad command > errors in crontab file, can''t install. > notice: Finished catalog run in 3.69 seconds > > > There are two things here that confuse me. 1: what''s the deal with the > ''could not prefetch package provider'' and 2: why does "/bin/true" > result in "bad command"?The fact that the error points at /usr/local/bin/python makes me wonder if you''ve got some non-packaged version of python in your path. The cron error sounds like the problem with 0.25.3, though I can''t recall if that''s the output that bug causes or not. What version of puppet are you running? If you''re using EPEL packages of 0.25.x from epel-testing, then update, as we have pushed 0.25.3 packages with the problematic cron changes reverted. -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I got nasty habits. I take tea at 3.
On Fri, Jan 22, 2010 at 6:52 PM, robbyt <robbyt@robbyt.net> wrote:> Hi All, > > For some reason, I''m unable to manage cron resources on my CentOS5 > server: > > manifest: > > cron { "test": > command => ''/bin/true'', > user => ''root'', > hour => ''1'', > } > > And when I try to run this via puppetmasterd: > > info: Caching catalog for ny-dev84.domain.com > err: Could not prefetch package provider ''yum'': Execution of ''/usr/ > local/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/ > yumhelper.py'' returned 1: <type ''exceptions.AttributeError''> > > info: Applying configuration version ''1264214417'' > notice: //crontab::puppet_runner/Cron[test]/ensure: created > "-":5: bad command >this is a known issue with .25.3. It will be fixed in .25.4> errors in crontab file, can''t install. > notice: Finished catalog run in 3.69 seconds > > > There are two things here that confuse me. 1: what''s the deal with the > ''could not prefetch package provider'' and 2: why does "/bin/true" > result in "bad command"? > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Jan 22, 10:45 pm, Todd Zullinger <t...@pobox.com> wrote:> robbyt wrote: > > For some reason, I''m unable to manage cron resources on my CentOS5 > > server: > > > manifest: > > > cron { "test": > > command => ''/bin/true'', > > user => ''root'', > > hour => ''1'', > > } > > > And when I try to run this via puppetmasterd: > > > info: Caching catalog for ny-dev84.domain.com > > err: Could not prefetch package provider ''yum'': Execution of ''/usr/ > > local/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/ > > yumhelper.py'' returned 1: <type ''exceptions.AttributeError''> > > > info: Applying configuration version ''1264214417'' > > notice: //crontab::puppet_runner/Cron[test]/ensure: created > > "-":5: bad command > > errors in crontab file, can''t install. > > notice: Finished catalog run in 3.69 seconds > > > There are two things here that confuse me. 1: what''s the deal with the > > ''could not prefetch package provider'' and 2: why does "/bin/true" > > result in "bad command"? > > The fact that the error points at /usr/local/bin/python makes me > wonder if you''ve got some non-packaged version of python in your path. > > The cron error sounds like the problem with 0.25.3, though I can''t > recall if that''s the output that bug causes or not. What version of > puppet are you running? If you''re using EPEL packages of 0.25.x from > epel-testing, then update, as we have pushed 0.25.3 packages with the > problematic cron changes reverted. >Hi Todd, You are correct 2x :) There is a custom python that I didn''t catch in /usr/local/bin. I just upgraded the epel testing package that you suggested and the cron problem has gone away! Thank you for your help! Dan: Thanks! looking forward to 0.25.4 :) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.