-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"-":6: bad command when setting up an agent #25
Comments
I did a little more experimenting and found that the following run by itself does work even though the above doesn't $at_boot_ensure = present cron { 'puppet_agent_once_at_boot': after running this separately class { 'puppet::agent': ... } works |
This issue eventually went away. I'm not sure what the cause actually was but suspect it was not due to this module so I'm closing the issue. |
On a new RHEL 6.4 system this error is occurring for Class { 'puppet::agent': } Since I'm using default parameters $run_method = 'service' and thus $my_cron_command = undef A quick work around is to set $run_at_boot => false whenever $run_method = 'service' |
I am hoping that #37 will resolve this issue. |
Thanks! Closing this and we can discuss in PR #37 |
When creating Cron[puppet_agent_at_boot] I get the following error
"-":6: bad command
errors in crontab file, can't install.
I get this when I try to apply
class { 'puppet::agent': env => 'dev', puppet_server => "puppet.$::domain", }
I confirmed that I can create a cron resource since the following works
cron { 'foo': command => 'echo foo', }
I am using the following modules on RHEL 6.4
ghoneycutt-common-1.0.2
ghoneycutt-puppet-2.1.2
leinaddm-htpasswd-0.0.1
puppetlabs-apache-0.8.1
puppetlabs-firewall-0.4.1
puppetlabs-mysql-0.9.0
puppetlabs-passenger-0.1.0
puppetlabs-stdlib-4.1.0
Any suggestions on what I may be doing wrong, what I can try or how I can be of assistance in resolving this issue would be appreciated.
The text was updated successfully, but these errors were encountered: