On Thu, 3 Mar 2005, Dan Gilbert wrote: > Any thoughts? My cursory scan of the list archives didn't find > anything, though I may not have seen everything, either. Below is > the gdb trace as prescribed on the cfwiki.org site (pruned to the > area just before the seg fault):
> > (gdb) bt > #0 LastSeen (hostname=0xbfff1460 "macgyver", role=cf_connect) > at ip.c:422 This looks like it's because something bogus got pulled from the last-seen berkeley db. I had a similar problem with the dynamic hosts database on a busy cf server, where some corruption had occured and subsequent reads from the bad area caused segfaults. Can you remove the cf_lastseen.db and see if the problem goes away? This db is not critical to functioning, so it should just be re-created without a problem. -- - Eric Sorenson - N37 17.255 W121 55.738 - http://eric.explosive.net - - Personal colo with a professional touch - http://www.explosive.net - _______________________________________________ Bug-cfengine mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-cfengine
