Got the verbose server output, and this seemed to be the error:
cf3 Received: [SAUTH y 256 37 c] on socket 5
cf3 Private decrypt failed = block type is not 02
cf3 Auth dialogue error
cf3 REFUSAL of request from connecting host: (SAUTH y 256 37 c)
I then regenerated the ppkeys for both the server
Hi
I was using cf-runagent under 3.0.4, but after upgrading to 3.0.5p1 I now
get the following error:
BAD: Unspecified server refusal (see verbose server output)
!! Authentication dialogue with 127.0.0.1 failed
Unable to establish connection with 127.0.0.1
I have been unable to find the verb
Hi
I just found out several of my purge copy promises have not been purging
due to an unexpected error:
cf3 !! Not purge local files /dir/to/be/purged - no contact with a source
I am copying files from local dir to local dir - no network source is used
at all.
I am using stock 3.0.4 - ha
It turns out a simple "grep -v grep" at the end of the shell command did
the trick:
"myarray[$(mykeys)]" string => execresult("/usr/bin/ps -f | grep
$(mylist[$(mykeys)]) | grep -v grep","useshell");
On May 14, 2010 8:05pm, Michael Potter wrote:
On Fri, May 14, 2010 at 4:58 PM, Сева Глущ
For me, the following bundle:
bundle agent atest {
vars:
"mylist[a]" string => "1";
"mylist[b]" string => "2";
"mylist[c]" string => "3";
"mykeys" slist => getindices("mylist");
"myarray[$(mykeys)]" string => execresult("/usr/bin/ps -f | grep
$(mylist[$(mykeys)])","useshell");
}
Produces
I have had exactly the same thoughts recently.
Basically what would be nice is the ability to define real functions that
accepts arguments and return values to vars.
Maybe something like:
vars:
"foo" function => bar("$(arg1)","$(arg2)");
...
body function bar(a,b)
{
return => execresult("
On Apr 6, 2010 8:51am, Bruce Carleton
wrote:
I have a problem where it appears that my schedule for running cf-agent
is being ignored. I'm trying to set it to run once an hour using this
schedule:
body executor control
{
splaytime => "5";
mailto => "bruce.carle...@jasperwi
I have been running cfengine3 (cf-execd and cf-serverd) under SMF for some
time now. My manifests are below.
One issue I have run into, is that SMF will put a service in maintenance
when either the service process dies, or one of it's child processes die.
As cf-agent run's as a child proces
I was doing something like this:
"localzone" string
=> execresult("/sbin/zonename","noshell");
"process_check[$(name)]" string
=> execresult("/usr/bin/pgrep -z$(checks.localzone) $(name)","noshell");
Although I have now switched to using Solaris SMF to manage services.
On Mar 29, 2010 9:54am,
On Mar 5, 2010 11:08am, Jessica Greer wrote:
Matt,
This is an interesting approach - food for thought. Do you find yourself
standing up test classes in the alpha/beta versions of your files and
removing them when you're ready to tag them as prod?
Maybe I'm not approaching the problem t
* site.cf
I use this to set global classes that control what actions needs to be
taken in a particular environment/server. I also set global vars in here,
such as the slist which is passed to bundlesequence - that way all the
stuff that varies depending on what classes are defined is consoli
11 matches
Mail list logo
