在Redhat AS4上安装了MySQL后,重启后屏幕弹出几个错误对话框,而且整个UI环境为黑底,无菜单和按钮,<br />
其中错误信息为:
Failed to contact configuration server; some possible causes are that
you need to enable TCP/IP networking for ORBit, or you have stale NFS
locks due to a system crash. See http://www.gnome.org/projects/gconf/
for information. (Details – 1: IOR file ‘/tmp/gconfd-root/lock/ior’ not
opened successfully, no gconfd located: No such file or directory 2:
IOR file ‘/tmp/gconfd-root/lock/ior’ not opened successfully, no gconfd
located: No such file or directory)

出现问题的原因可能是某些配置出问题了,也有可能是系统本身出现了问题从而导致配置出错。<br />

到<a href=”http://www.gnome.org/projects/gconf/” target=”_blank”>http://www.gnome.org/projects/gconf/上看了一下,官方解释为:

I’m having a lock file problem. What do I do?

Usually a problem here involves either NFS, or a kernel bug.

The per-user daemon locks two files in the default configuration:

The first lock is to ensure that only one gconfd is
running. The second lock is to ensure only one program accesses the XML
config source at a time.

If you have an NFS-mounted home
directory, you must be running an rpc.statd/rpc.lockd setup on both NFS
client and NFS server, so that file locking works. On Red Hat Linux,
this means the “nfslock” service must be running. Enable it permanently
with the chkconfig tool – see its manual page. Turn it on or off at any given time with service nfslock start or service nfslock stop. You must be root to do this.

If
the kernel crashes (or the power cord gets pulled) on an NFS client
machine, theoretically when you reboot the client machine it will
notify the NFS server that it has rebooted and all previously-held
locks should be released. However, many operating systems including Red
Hat Linux 7.2 do not properly do this; so you will have stale locks
after a crash. If no gconfd is running, these locks may safely be
removed. If gconfd is running though, DO NOT remove them; if
you have two gconfd processes for a single user, bad things may happen
to that user’s preferences once in a while.

没有发现解决问题的方法,后来发现,有为仁兄也碰到过类似问题,

解决方法为:

1.删除当前用户在/tmp下的相关文件:
假设用户名是root,就是这样的#rm -R *root* 。</p>

2.删除用户主目录下的.gnome 和 .gnome2两个文件夹。 假设用户名是root,就是这样的#rm -R /root/.gnome 和#rm -R /root/.gnome2.

3.重启gnome环境,问题解决。<br />

Leave a Reply

电子邮件地址不会被公开。 必填项已用*标注