GConf error:Failed to contact configuration server

简介:

Linux系统运行一直正常,但是图形界面使用root账号登录时遇到下面错误,第一次遇到这么怪异的状况

clip_image001

具体错误信息如下所示:

GConf error:Failed to contact configuration server;some possible cause are that you 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' not opened successfully;no gconfd located;no such file or directory2;IOR file '/tmp/gconfd-root/lock/ior' not opened successfully;no gconfd located;no such file or directory)

 

原因分析:

出现这个问题,有时候是因为在root账号下执行了 chmod -R 777 /tmp,我这边是因为chown –R oracle:oinstall /tmp误操作所导致。官方文档资料显示如下所示,不过水平还没有到那个级别,理解起来也是非常吃力:

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 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 startor 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.

See also the next question.

解决方法:

登录oracle用户,检查/tmp目录,如下所示,删除gconfd-root目录,重启gnome环境(重启主机也行),问题解决。

[oracle@db-server tmp]$ ls
 
 
0igYi60r4P              glibc.txt            LinuxVendor_output.txt  pZfW5Q9nxO      tmpFileKernelParms.txt
 
 
cpuinfo.txt             hs_err_pid17281.log  mapping-root            ssh-EOTPVp5471  virtual-root.TIjJMH
 
 
EM_TARGET_INSTALLER.lk  keyring-MgIEnU       orbit-root              ssh-UuyYiJ3942  virtual-root.zzPdWF
 
 
gconfd-root             keyring-uwsUZW       pkginfo.txt             swapinfo.txt
 
 
[oracle@db-server tmp]$ rm -R /tmp/gconfd-root/
 
 
[oracle@db-server tmp]$
相关文章
|
13天前
|
Nacos 开发者
nacos报错 Server check fail, please check server 127.0.0.1 ,port 9848 is available , error ={}
在配置文件中指定的Nacos服务器地址未被项目使用,程序仍尝试连接到127.0.0.1。开发者寻求帮助排查问题,已花费多天未果。
|
5月前
Error from server error dialing backend remote error tls internal error
Error from server error dialing backend remote error tls internal error
43 0
|
XML 应用服务中间件 数据格式
控制台报错: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting proper
控制台报错: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting proper
78 0
控制台报错: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting proper
|
Kubernetes 容器
k8s报错:Error from server (NotFound): the server could not find the requested resource (get services h
k8s报错:Error from server (NotFound): the server could not find the requested resource (get services h
|
NoSQL MongoDB
运行 mongo 出现 Error: couldn‘t connect to server 127.0.0.1:27017, connection attempt failed
运行 mongo 出现 Error: couldn‘t connect to server 127.0.0.1:27017, connection attempt failed
505 0
运行 mongo 出现 Error: couldn‘t connect to server 127.0.0.1:27017, connection attempt failed
|
数据安全/隐私保护

热门文章

最新文章