GConf error: Failed to contact configuration server, gconffailed

GConf error: Failed to contact configuration server, gconffailed

The Linux system has been running normally, but the following error occurs when you log on to the GUI using the root account. This is the first time you encounter such a strange situation.

The error message is as follows:

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)

Cause analysis:

This problem occurs sometimes because chmod-R 777/tmp is executed under the root account, which is caused by the misoperation of chown-R oracle: oinstall/tmp. The official documents are shown as follows, but the level is not at that level, which is hard to understand:

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 handle y the NFS server that it has rebooted and all previusly-held locks shoshould be released. however, 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.

Solution:

Log on to the oracle user and check the/tmp directory, as shown in the following figure. Delete the gconfd-root directory and restart the gnome Environment (restart the host as well). The problem is solved.

[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]$

References:

Http://gdcsy.blog.163.com/blog/static/127343609201061334949543/

In the ubuntu904 graphic interface, permissions are insufficient, and "users and groups" cannot be enabled, while command lines seem to have root permissions.

This command is terrible, and the landlord has hurt me too!
However, I can also use the root user to open users-admin.

Su: Authentication failure
Lsj @ lsj-ubuntu :~ $ Su
Password :*******
To run a command as administrator (user "root"), use "sudo <command> ".
See "man sudo_root" for details.

Root @ lsj-ubuntu:/home/lsj # users-admin

** (Users-Administrator: 5740): CRITICAL **: Cannot create session bus: Did not receive a reply. possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: 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 projects.gnome.org/gconf/ for information. (Details-1: Failed to get connection to session: Did not receive a reply. possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken .)
 
Server error: Failed to boot server 'wjun _ BS 'Task failed: boot the Backup Server

This is obviously because the network is disconnected or the port is not connected.
Use root:
Ping the target server first,
Telnet the target server port.
If both are OK, use root to start the program. If it is a private machine, disable the firewall and selinux first.