On Fri, Jul 17, 2009 at 12:56 AM, Ron Blizzard<rb4centos at gmail.com> wrote: > Interesting. I'll see what I can find in /var/log/messages and share > anything that might point to the problem. Thanks for writing. Here's what the logs show... Jul 17 00:31:51 localhost last message repeated 3 times Jul 17 00:32:01 localhost gconfd (ronb-2823): starting (version 2.14.0), pid 2823 user 'ronb' Jul 17 00:32:01 localhost gconfd (ronb-2823): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Jul 17 00:32:01 localhost gconfd (ronb-2823): Resolved address "xml:readwrite:/home/ronb/.gconf" to a writable configuration source at position 1 Jul 17 00:32:01 localhost gconfd (ronb-2823): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 Jul 17 00:32:04 localhost gconfd (ronb-2823): Resolved address "xml:readwrite:/home/ronb/.gconf" to a writable configuration source at position 0 Jul 17 00:32:05 localhost pcscd: winscard.c:304:SCardConnect() Reader E-Gate 0 0 Not Found Jul 17 00:32:05 localhost last message repeated 4 times Jul 17 00:32:06 localhost nm-system-settings: Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Jul 17 00:32:06 localhost nm-system-settings: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ... Jul 17 00:32:06 localhost nm-system-settings: ifcfg-rh: read connection 'System eth0' Jul 17 00:32:06 localhost nm-system-settings: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... Jul 17 00:32:06 localhost nm-system-settings: ifcfg-rh: error: Ignoring loopback device config. Jul 17 00:32:56 localhost kernel: e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex, Flow Control: None Jul 17 00:47:20 localhost gconfd (root-3405): starting (version 2.14.0), pid 3405 user 'root' Jul 17 00:47:20 localhost gconfd (root-3405): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Jul 17 00:47:20 localhost gconfd (root-3405): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1 Jul 17 00:47:20 localhost gconfd (root-3405): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 Jul 17 00:48:21 localhost gconfd (root-3405): GConf server is not in use, shutting down. Jul 17 00:48:21 localhost gconfd (root-3405): Exiting Jul 17 01:31:11 localhost gconfd (root-3889): starting (version 2.14.0), pid 3889 user 'root' Jul 17 01:31:11 localhost gconfd (root-3889): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Jul 17 01:31:11 localhost gconfd (root-3889): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1 Jul 17 01:31:11 localhost gconfd (root-3889): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 In this time period Xorg crashed twice. Earlier in the log (on July 15th and 14th) I have similar records (which correlate with the other crashes) but there is no "Exiting" line. These were times where I had to reboot to get the machine back into a working state. It looks like it has something to do with an XML lock? -- RonB -- Using CentOS 5.3