Xmanager连接RedHat GNOME错误:Failed to contact configuration server;
2014-06-25 08:37
363 查看
在Redhat AS4上安装了MySQL后(我是在用xmanager连接RedHat时出现的这个错误),重启后屏幕弹出几个错误对话框,而且整个UI环境为黑底,无菜单和按钮,
其中错误信息为:
Failed to contact configuration server; some possible causes are thatyou need to enable TCP/IP networking for ORBit, or you have stale NFSlocks due to a system crash. See
http://www.gnome.org/projects/gconf/for information. (Details - 1: IOR file '/tmp/gconfd-root/lock/ior' notopened successfully, no gconfd located: No such file or directory 2:IOR
file '/tmp/gconfd-root/lock/ior' not opened successfully, no gconfdlocated: No such file or directory)
出现问题的原因可能是某些配置出问题了,也有可能是系统本身出现了问题从而导致配置出错。
到http://www.gnome.org/projects/gconf/上看了一下,官方解释为:
The per-user daemon locks two files in the default configuration:
The first lock is to ensure that only one gconfd isrunning. The second lock is to ensure only one program accesses the XMLconfig source at a time.
If you have an NFS-mounted homedirectory, you must be running an rpc.statd/rpc.lockd setup on both NFSclient and NFS server, so that file locking works. On Red Hat Linux,this means the "nfslock" service must be running. Enable it permanentlywith 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.
Ifthe kernel crashes (or the power cord gets pulled) on an NFS clientmachine, theoretically when you reboot the client machine it willnotify the NFS server that it has rebooted and all previously-heldlocks should be released. However, many operating systems
including RedHat Linux 7.2 do not properly do this; so you will have stale locksafter a crash. If no gconfd is running, these locks may safely beremoved. If gconfd is running though,
DO NOT remove them; ifyou have two gconfd processes for a single user, bad things may happento that user's preferences once in a while.
没有发现解决问题的方法,后来发现,有为仁兄也碰到过类似问题,
解决方法为:
1.删除当前用户在/tmp下的相关文件:假设用户名是root,就是这样的#rm -R *root* 。
2.删除用户主目录下的.gnome 和 .gnome2两个文件夹。 假设用户名是root,就是这样的#rm -R /root/.gnome 和#rm -R /root/.gnome2.
3.重启gnome环境,问题解决。
其中错误信息为:
Failed to contact configuration server; some possible causes are thatyou need to enable TCP/IP networking for ORBit, or you have stale NFSlocks due to a system crash. See
http://www.gnome.org/projects/gconf/for information. (Details - 1: IOR file '/tmp/gconfd-root/lock/ior' notopened successfully, no gconfd located: No such file or directory 2:IOR
file '/tmp/gconfd-root/lock/ior' not opened successfully, no gconfdlocated: No such file or directory)
出现问题的原因可能是某些配置出问题了,也有可能是系统本身出现了问题从而导致配置出错。
到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:
~/.gconfd/lock/ior ~/.gconf/%gconf-xml-backend.lock/ior
The first lock is to ensure that only one gconfd isrunning. The second lock is to ensure only one program accesses the XMLconfig source at a time.
If you have an NFS-mounted homedirectory, you must be running an rpc.statd/rpc.lockd setup on both NFSclient and NFS server, so that file locking works. On Red Hat Linux,this means the "nfslock" service must be running. Enable it permanentlywith 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.
Ifthe kernel crashes (or the power cord gets pulled) on an NFS clientmachine, theoretically when you reboot the client machine it willnotify the NFS server that it has rebooted and all previously-heldlocks should be released. However, many operating systems
including RedHat Linux 7.2 do not properly do this; so you will have stale locksafter a crash. If no gconfd is running, these locks may safely beremoved. If gconfd is running though,
DO NOT remove them; ifyou have two gconfd processes for a single user, bad things may happento that user's preferences once in a while.
没有发现解决问题的方法,后来发现,有为仁兄也碰到过类似问题,
解决方法为:
1.删除当前用户在/tmp下的相关文件:假设用户名是root,就是这样的#rm -R *root* 。
2.删除用户主目录下的.gnome 和 .gnome2两个文件夹。 假设用户名是root,就是这样的#rm -R /root/.gnome 和#rm -R /root/.gnome2.
3.重启gnome环境,问题解决。
相关文章推荐
- GNOME错误:Failed to contact configuration server
- navicat连接oracle数据库报ORA-28547: connection to server failed, probable Oracle Net admin error错误的解决方法
- navicat连接oracle数据库报ORA-28547: connection to server failed, probable Oracle Net admin error错误的解决方法
- navicat连接oracle数据库ORA-28547:connection to server failed, probable Oracle Net admin error错误,解决方法
- mount 错误 “RPC: failed to contact local rpcbind server (errno 5)
- navicat连接oracle数据库报ORA-28547: connection to server failed, probable Oracle Net admin error错误的解决方法
- mount 错误 “RPC: failed to contact local rpcbind server (errno 5).”解决方法
- gconf Failed to contact configuration server
- navicat连接oracle数据库报ORA-28547: connection to server failed, probable Oracle Net admin error错误的解决方法
- Navicat 连接oracle 11g突然蹦出了一个错误“ORA-28547:connection to server failed,probable Oracle Net admin error”
- navicat连接oracle数据库报ORA-28547: connection to server failed, probable Oracle Net admin error错误的解决方法
- navicat连接oracle数据库报ORA-28547: connection to server failed, probable Oracle Net admin error错误的解决方法
- navicat连接oracle数据库ORA-28547:connection to server failed, probable Oracle Net admin error错误,解决方法
- mount 错误 “RPC: failed to contact local rpcbind server (errno 5).”解决方法
- vm manager failed to contact configuration server
- Oracle学习笔记4 使用Navicat for Oracle 连接Oracle时出现错误:ORA-28547: connection to server failed, probable Oracle Net admin error
- GConf Error: Failed to contact configuration server解决方法
- GConf error:Failed to contact configuration server
- mount 错误 “RPC: failed to contact local rpcbind server (errno 5).”解决方法
- fedora16 MYSQL登录错误:mysqladmin: connect to server at ‘localhost’ failed