跳至主要内容

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit

因为有人用root用户启动了UCM，再用Oracle用户就没法启动，把/tmp目录权限改成777后可以正常启动。
没想到再次启动Redhat时，出现黑屏，并出现以下提示：
“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)”

看起来还是目录权限设置引起，重新把/tmp/gconfd/root权限设置成700，重新启动系统，一切正常。
标签：

评论

发表评论

此博客中的热门博文

Installing RHEL EPEL Repo on Centos 5.x or 6.x

习惯了用yum来安装东西，试了下这篇文章提到的做法workable，再做一次搬运工。 原文出处： http://www.rackspace.com/knowledge_center/article/installing-rhel-epel-repo-on-centos-5x-or-6x Authored by: Rackspace Support How to install RHEL EPEL repository on Centos 5.x or 6.x The following article will describe how to configure a CentOS 5.x-based or Centos 6.x-based system to use Fedora Epel repos and third party remi package repos. These package repositories are not officially supported by CentOS, but they provide much more current versions of popular applications like PHP or MYSQL. Install the extra repositories The first step requires downloading some RPM files that contain the additional YUM repository definitions. The instructions below point to the 64-bit versions that work with our Cloud Server instances. Centos 5.x wget http://dl.fedoraproject.org/pub/epel/5/x86_64/epel-release-5-4.noarch.rpm wget http://rpms.famillecollet.com/enterprise/remi-release-5.rpm sudo rpm -Uvh remi-release-5*.rpm epel...
发表评论
阅读全文

64位OEL 6安装Oracle RCU报“libXext.so.6: cannot open shared object file: No such file or directory”的解决方法

在64位的Oracle Enterprise Linux 6上时报“ libXext.so.6: cannot open shared object file: No such file or directory ”的错误，已经装了64位x11相关的包，可见是缺少32位的包引起的。 1.libXext.so.6错误信息如下： 无法使用位置 /home/ecm/oinstall/rcuHome/rcu/log/logdir.2011-12-26_09-54/rcu.log 初始化日志记录程序 使用以下位置初始化日志记录程序: /tmp/logdir.2011-12-26_09-54/rcu.log Exception in thread "main" java.lang.UnsatisfiedLinkError: /home/ecm/oinstall/rcuHome/jdk/jre/lib/i386/xawt/libmawt.so: libXext.so.6: cannot open shared object file: No such file or directory     at java.lang.ClassLoader$NativeLibrary.load(Native Method)     at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1806)     at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1702)     at java.lang.Runtime.load0(Runtime.java:770)     at java.lang.System.load(System.java:1003)     at java.lang.ClassLoader$NativeLibrary.load(Native Method)     at java.lang.ClassLoader.loadLibrar...
发表评论
阅读全文

How to Convert a VMware Pre-allocated Virtual Disk to a Growable Virtual Disk

受不了动辄几百G的虚机，记给自己看，只是在网络上搬运，来源在这里： http://www.virtuatopia.com/index.php/How_to_Convert_a_VMware_Pre-allocated_Virtual_Disk_to_a_Growable_Virtual_Disk 。 he vmware-vdiskmanager tool The VMware Disk Management Tool is a command line tool which is installed by default with VMware Server. The executable file is named   vmware-vdiskmanager   and is located in   \Program Files\VMware\VMware Server   on Windows hosts, and   /usr/bin   on Linux systems. The tool accepts a number of command-line arguments, a full listing of which can be obtained by running vmware-vdiskmanager with no options. vmware-vdiskmanager Virtual Disk Types The type to which a virtual disk is to be converted is specified using the -t flag, together with the target disk type. This is represented by a number as outlined in the following table: Type Identifier Description 0 Growable (single .vmdk file) 1 Growable (multiple 2GB files) 2 Pre-allocated (single file) 3 Pre...
发表评论
阅读全文