[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
SIGPIPE errors with 2.1.6
From: |
Wil Cooley |
Subject: |
SIGPIPE errors with 2.1.6 |
Date: |
Thu, 03 Jun 2004 09:59:40 -0700 |
I don't seem to be the first to see this, but I have an inkling of
what's causing it--I have followed the tutorial stuff and have cfengine
ensure that cfexecd was running hourly out of cron, at XX:00. I also
have cfexecd running in daemon mode, scheduled at Min00_05 and Min30_35,
with no splay time. As I look at the times the errors occurred, they
were always at XX:00, which leads me to believe the locking problem is
exactly that--two cfagents are being run simultaneously. I'll post a
follow-up if this fixes the problem, since it seems that other newbies
have run into this and will likely run into it in the future.
cfengine:: Received signal 13 (SIGPIPE) while doing [pre-lock-state]
cfengine:: Logical start time Thu Jun 3 09:00:05 2004
cfengine:: This sub-task started really at Thu Jun 3 09:00:05 2004
cfengine:: Received signal 13 (SIGPIPE) while doing [pre-lock-state]
cfengine:: Logical start time Thu Jun 3 09:00:05 2004
cfengine:: This sub-task started really at Thu Jun 3 09:00:05 2004
cfengine:: Received signal 13 (SIGPIPE) while doing [pre-lock-state]
cfengine:: Logical start time Thu Jun 3 09:00:05 2004
cfengine:: This sub-task started really at Thu Jun 3 09:00:05 2004
cfengine:: Challenge response from server rheingold.nakedape.priv/192.168.1.1
was incorrect!
cfengine:: Authentication dialogue with rheingold.nakedape.priv failed
http://lists.gnu.org/archive/html/help-cfengine/2003-11/msg00149.html
Wil
--
Wil Cooley wcooley@nakedape.cc
Naked Ape Consulting http://nakedape.cc
* Naked Ape Business Server http://nakedape.cc/r/smb *
signature.asc
Description: This is a digitally signed message part
- SIGPIPE errors with 2.1.6,
Wil Cooley <=