From owner-freebsd-gnome@FreeBSD.ORG Thu Jul 27 23:40:13 2006 Return-Path: X-Original-To: gnome@FreeBSD.org Delivered-To: freebsd-gnome@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03BBA16A4DD for ; Thu, 27 Jul 2006 23:40:12 +0000 (UTC) (envelope-from marcus@FreeBSD.org) Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 741A443D46 for ; Thu, 27 Jul 2006 23:40:12 +0000 (GMT) (envelope-from marcus@FreeBSD.org) X-TACSUNS: Virus Scanned Received: from rooster.cisco.com (localhost [127.0.0.1]) by av-tac-rtp.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id k6RNeBk24226; Thu, 27 Jul 2006 19:40:11 -0400 (EDT) Received: from [172.18.173.61] (dhcp-172-18-173-61.cisco.com [172.18.173.61]) by rooster.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id k6RNeAB19065; Thu, 27 Jul 2006 19:40:11 -0400 (EDT) Message-ID: <44C94EDA.1080607@FreeBSD.org> Date: Thu, 27 Jul 2006 19:40:10 -0400 From: Joe Marcus Clarke Organization: FreeBSD, Inc. User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530) MIME-Version: 1.0 To: Mike Harding References: <20060727232818.0E15D170A5@bsd.mvh> In-Reply-To: <20060727232818.0E15D170A5@bsd.mvh> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: gnome@FreeBSD.org Subject: Re: gconfd crashes... X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 23:40:13 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mike Harding wrote: > I have had gconfd-2 crashing lately, which freezes up evolution. Blah. > > Anyway - has this happened to anyone else? No. > > Also, could this be caused by having a tinderbox building away on my > desktop machine (Marcus)? Not directly. > > I did see this in /var/log/messages... Looks like you're running out of memory. This could be due to corrupt gconf files, or legitimate resource problems. You should try to get a backtrace with debugging symbols to find out what's trying to be allocated. Joe > > Jul 27 14:59:04 bsd kernel: pid 55827 (gconfd-2), uid 1001: exited on signal 6 > Jul 27 15:18:52 bsd gconfd (mvh-25589): gmem.c:172: failed to allocate 134217728 bytes > Jul 27 15:18:52 bsd kernel: pid 25589 (gconfd-2), uid 1001: exited on signal 6 > Jul 27 15:44:20 bsd gconfd (mvh-5149): gmem.c:172: failed to allocate 134217728 bytes > Jul 27 15:44:20 bsd kernel: pid 5149 (gconfd-2), uid 1001: exited on signal 6 > Jul 27 15:44:22 bsd gconfd (mvh-77369): Failed to get lock for daemon, exiting: Failed to lock '/var/tmp/gconfd-mvh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) > Jul 27 15:46:56 bsd gconfd (mvh-77367): gmem.c:172: failed to allocate 8388608 bytes > Jul 27 15:46:56 bsd kernel: pid 77367 (gconfd-2), uid 1001: exited on signal 6 > Jul 27 15:47:50 bsd Jul 27 15:47:50 bsd kernel: pid 80875 (gconfd-2), uid 1001: exited on signal 6 > Jul 27 15:48:17 bsd Jul 27 15:48:17 bsd kernel: pid 81150 (gconfd-2), uid 1001: exited on signal 6 > Jul 27 15:48:58 bsd Jul 27 15:48:59 bsd kernel: pid 81425 (gconfd-2), uid 1001: exited on signal 6 > Jul 27 15:49:41 bsd Jul 27 15:49:41 bsd kernel: pid 81567 (gconfd-2), uid 1001: exited on signal 6 > Jul 27 15:52:16 bsd Jul 27 15:52:16 bsd kernel: pid 82195 (gconfd-2), uid 1001: exited on signal 6 > Jul 27 15:52:18 bsd gconfd (mvh-84451): Failed to get lock for daemon, exiting: Failed to lock '/var/tmp/gconfd-mvh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) > Jul 27 16:07:22 bsd kernel: pid 84452 (gconfd-2), uid 1001: exited on signal 6 > Jul 27 16:07:22 bsd gconfd (mvh-84452): Received signal 11, dumping core. Please report a GConf bug. > Jul 27 16:16:46 bsd kernel: pid 46225 (gconfd-2), uid 1001: exited o > Jul 27 16:16:46 bsd kernel: n signal 6 > Jul 27 16:16:46 bsd gconfd (mvh-46225): Received signal 11, dumping core. Please report a GConf bug. > > - Mike H. > > _______________________________________________ > freebsd-gnome@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-gnome > To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.org" > - -- Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEyU7ab2iPiv4Uz4cRAkscAJ9slKp3eWNl+seyNmiLIf5ikkd8jQCbBwBy 53BTQN4p58hTaeUJVDP5kNs= =mrWF -----END PGP SIGNATURE-----