Sealyu

          --- 博客已遷移至: http://www.sealyu.com/blog

            BlogJava :: 首頁 :: 新隨筆 :: 聯系 :: 聚合  :: 管理 ::
            618 隨筆 :: 87 文章 :: 225 評論 :: 0 Trackbacks
          在Redhat AS4上安裝了MySQL后,重啟后屏幕彈出幾個錯誤對話框,而且整個UI環境為黑底,無菜單和按鈕,
          其中錯誤信息為:
          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)

          出現問題的原因可能是某些配置出問題了,也有可能是系統本身出現了問題從而導致配置出錯。

          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 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* 。

          2.刪除用戶主目錄下的.gnome 和 .gnome2兩個文件夾。 假設用戶名是root,就是這樣的#rm -R /root/.gnome 和#rm -R /root/.gnome2.

          3.重啟gnome環境,問題解決。

          posted on 2008-07-20 21:06 seal 閱讀(3309) 評論(1)  編輯  收藏 所屬分類: Linux

          評論

          # re: GNOME錯誤:Failed to contact configuration server; 2009-03-29 18:37 kev
          這個解決方法贊!!!  回復  更多評論
            

          主站蜘蛛池模板: 海伦市| 黄浦区| 郸城县| 宁明县| 阿拉善左旗| 怀柔区| 化州市| 海兴县| 米易县| 绵竹市| 汝城县| 台湾省| 临泽县| 都江堰市| 定结县| 孝昌县| 福建省| 宁海县| 东海县| 东乡| 榆林市| 巫山县| 嘉荫县| 庆阳市| 怀远县| 曲靖市| 颍上县| 禄丰县| 鸡泽县| 新田县| 千阳县| 太谷县| 东阳市| 苍梧县| 麦盖提县| 松潘县| 重庆市| 阿坝县| 江孜县| 丹棱县| 凯里市|