Issue #7542 has been updated by Robin Powell.
On Thu, May 19, 2011 at 12:03:35PM -0700, [email protected] wrote: > > Issue #7542 has been updated by Ben Hughes. > > Status changed from Unreviewed to Investigating > Assignee set to Ben Hughes > Affected Puppet version deleted (2.6.4) > > I've been completely unable to reproduce this here I'm afraid. I'm totally unsurprised; a random selection of my machines has it, and they all have the same version of puppet; I strongly suspect some ancillary library or system configuration issue. > Could you please see if using the 2.6.x series fixes this problem? 2.6.8 on the client does seem to fix it right up, yep. Sorry I didn't try that myself; that was dumb. :( -Robin ---------------------------------------- Bug #7542: Cron has too many fields https://projects.puppetlabs.com/issues/7542 Author: Robin Powell Status: Investigating Priority: Normal Assignee: Ben Hughes Category: Target version: Affected Puppet version: Keywords: Branch: On some of my CentOS 5.5 machines, but not others, puppet is trying to install cron entries with too many fields. This means puppet cannot succeed on these hosts. I would be very happy to help debug this, but I really don't know what information to give. The only way I even figured out the problem was strace. Some details: <pre> [root@beta01 /]# sudo puppetd -tv info: Caching catalog for beta01.c44031.blueboxgrid.com info: /Stage[main]/Ruby/Tidy[/etc/profile.d/rvm.sh]: File does not exist info: Applying configuration version '1305353595' notice: /Stage[main]/Puppet/Cron[puppet run cron]/ensure: created "-":6: bad hour errors in crontab file, can't install. </pre> Which is odd. They're both running centos packages for puppet 0.25.5-1.el5 I couldn't figure it out, so I ran strace, and found this: <pre> [pid 1872] write(3, "# HEADER: This file was autogenerated at Fri May 13 22:50:02 -0700 2011 by puppet.\n# HEADER: While it can +still be managed manually, it is definitely not recommended.\n# HEADER: Note particularly that the comments starting with 'Puppet +Name' should\n# HEADER: not be deleted, as doing so could cause duplicate cron jobs.\n# Puppet Name: puppet run cron\n* 1 1 * * * +foo\n", 366) = 366 </pre> Which is equivalent to: <pre> # HEADER: This file was autogenerated at Fri May 13 22:50:02 -0700 2011 by puppet. # HEADER: While it can still be managed manually, it is definitely not recommended. # HEADER: Note particularly that the comments starting with 'Puppet Name' should # HEADER: not be deleted, as doing so could cause duplicate cron jobs. # Puppet Name: puppet run cron * 1 1 * * * foo </pre> That's one too many fields. Not that it should matter, but the cron was *very* simple by that time: cron { 'puppet run cron': command => "foo", user => root, hour => 1, minute => 1, } -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
