help-cfengine
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: shellcommands not executing - lock problem?


From: Mark . Burgess
Subject: Re: shellcommands not executing - lock problem?
Date: Tue, 24 Feb 2004 17:51:22 +0100 (MET)

If something caused the agent to crash while the shellcommand was running
the lock will have to wait until expiredafter time is reached before
it will be removed. You can always delete the lock database to check.
/var/cfengine/cfengine_lock_db

M

On 24 Feb, Kurt Lieber wrote:
> We're trying to use cfengine to run a series of rsync commands on our web
> nodes.  The relevant syntax is:
> 
> shellcommands:
>   _gweb.slave_webnode.slave_web_sync::
>     "/bin/su - gweb -l -c '/usr/bin/rsync -rltvv --delete 
> gweb@$(_master_node):$(web_stage_html)/ $(web_html)/'"
>     "/bin/su - gweb -l -c '/usr/bin/rsync -rltvv --delete 
> gweb@$(_master_node):$(web_stage_images)/ $(web_images)/'"
>     "/bin/su - gweb -l -c '$(web_scripts)/rsync-weblogs.sh'"
> 
> Of those three commands, the first and third get executed.  The second never 
> does.
> 
> It appears to be some sort of locking problem.  If I run:
> 
> cfagent -K -q -v -t -Dslave_web_sync
> 
> Everything works fine.  Change that to:
> 
> cfagent -q -v -t -Dslave_web_sync
> 
> And it doesn't work.  (-K is ignore locks)
> 
> Trolling through the debug output of the non-working command shows this
> line:
> 
> cfengine:nue: Nothing scheduled for shellcommand._gweb._bin_su___gweb__l__c___
> usr_bin_rsync__rltvv___delete_gweb_nue_gentoo_org__var_www_www_gentoo_org_stage
> _site_images___var_www_www_gentoo_org_images__ (0/1 minutes elapsed)
> 
> However, it *only* says that for that specific command.  As I mentioned,
> the first and third commands run fine.
> 
> Any suggestions/help?
> 
> --kurt
> 



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272            Email:  Mark.Burgess@iu.hio.no
Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~





reply via email to

[Prev in Thread] Current Thread [Next in Thread]