On Fri, 5 Sep 2008, Morten Werner Forsbring wrote:
Sure, but not until Tuesday ... the home machines seem to be doing
ok after the last round of updates - and the office is powered down
this 3day weekdend
Hi, have you been able to test the new package on your other machines?
Or any other results from your home machines?
Thanks for the prod !
With the current packages (in Debian), I still see the failures
on *all* 32bit systems, but none on the amd64 system (which are
also the cfengine servers). All (32&64bit) are running cfservd
and cron scheduled cfagent (every 30min).
I've just installed your updated package on the 32bit systems -
fortunately my problem & your build match :)
I'll let it run a while and watch the logs...
In case it helps, here's what I have been seeing with the
stock packages (I'm not sure exactly what the kernel segfault message is
telling me) - but there are some unique patterns:
$zgrep -e 'cfagent.* segfault' /var/log/syslog* | grep -v 'error 4'
/var/log/syslog.5.gz:Aug 30 16:39:27 sparks-ave kernel: cfagent[14488]:
segfault at dbdbdbdb ip dbdbdbdb sp bfaa0a7c error 15
/var/log/syslog.3.gz:Aug 27 16:32:22 bandit-hall kernel: cfagent[21515]:
segfault at dbdbdbdb ip dbdbdbdb sp bfb1994c error 5
/var/log/syslog.2.gz:Aug 28 21:31:49 corkscrew kernel: cfagent[30815]:
segfault at 1166c548 ip 08b3561e sp bfb169ac error 6
This error, however is ~ 99% of them - and should be trackable
to the actual source (with linkmap & listings):
$zgrep -e 'cfagent.* segfault' /var/log/syslog*
/var/log/syslog.3.gz:Aug 27 07:31:52 bandit-hall kernel: cfagent[21610]:
segfault at 1e03e ip 0001e03e sp bfc3e26c error 4 in cfagent[8048000+a3000]
/var/log/syslog:Sep 4 07:01:46 corkscrew kernel: cfagent[1523]:
segfault at 0 ip 00000000 sp bfed556c error 4 in cfagent[8048000+a3000]
/var/log/syslog:Sep 4 07:01:35 gothic-ave kernel: cfagent[15879]:
segfault at 1f201 ip 0001f201 sp bfea7d2c error 4 in cfagent[8048000+a3000]
--
Rick Nelson
* Dry-ice can't code his way out of a paper bag
<Coderjoe> dry-ice: int main() { ExitPaperBag(); return 0; }
<Knghtbrd> Is that how that's done then? *takes notes*
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
