Re: Strange error from cfexecd

[Vince Giambalvo]

> >>>>> "Allen" == Allen Bettilyon <allen@about-inc.com> writes:
> 
>     Allen> I've got a cluster of about 80 machines managed with
>     Allen> cfengine.  Works great, but I routinely get errors like the
>     Allen> following: cfengine:w17: Received signal 13 while doing
>     Allen> [no_active_lock] cfengine:w17: Logical start time Tue Oct
>     Allen> 22 04:22:32 2002 cfengine:w17: This sub-task started really
>     Allen> at Tue Oct 22 04:22:43 2002 cfengine:w17: Received signal
>     Allen> 13 while doing [no_active_lock] cfengine:w17: Logical start
>     Allen> time Tue Oct 22 04:22:32 2002 cfengine:w17: This sub-task
>     Allen> started really at Tue Oct 22 04:22:43 2002 cfengine:w17:
>     Allen> Received signal 13 while doing [no_active_lock]
>     Allen> cfengine:w17: Logical start time Tue Oct 22 04:22:32 2002
>     Allen> cfengine:w17: This sub-task started really at Tue Oct 22
>     Allen> 04:22:43 2002 cfengine:w17: Key-authentication for w17.fs
>     Allen> failed cfengine:w17: Unable to establish connection with
>     Allen> 1.2.3.4
> 
> Version ?
Well, we are running 2.04, which I thought was supposed to correct
those errors, but they still occur.
I am glad to hear we are not the only ones.
     Vince Giambalvo