The file should be located in /etc/cluster and is called cluster.conf. You can create it using system-config-cluster or by using the luci web-based management tool.
ya that sounds gud, i can find the cluster.conf file in the /etc/cluster path.. but i still get the error . . as shown in the attachment
Hi experts, I have some custom application which I need to make Highly Available using red hat cluster service. How do I do it? i know in /usr/share/cluster i shall find HA agents for well known services like Apache or Sybase but I want to write HA agent for my own. I tried looking up on... (4 Replies)
Hello everyone,
I'm setting up a cluster with 2 nodes using Red Hat enterprise 6.2 x86_64, 1 luci and 1 ricci for education purpose.
Ricci is installed and already running and luci is installed and running but at the time of add and create the cluster through the web gui it give me a error... (1 Reply)
Hi Experts,
I have question regarding linux cluster managment on Red Hat 5.x server. When I try to install 'luci' or 'ricci' in one of our linux servers it is giving me below error:-
yum install luci
Loaded plugins: katello, product-id, rhnplugin, security, subscription-manager
Updating... (0 Replies)
How can we implement a service in HA, which in not available in HA.
like sldap or customize application.
Requirement Details.
NODE1 service slapd is running.(Require)
NODE2 service slapd is running.(Require)
on both the node replication is happening.
Now here requirement is need... (2 Replies)
Discussion started by: Priy
2 Replies
LEARN ABOUT DEBIAN
confdb2ldif
confdb2ldif(8) System Manager's Manual confdb2ldif(8)NAME
confdb2ldif - Create an LDIF file from a cluster configuration
SYNOPSIS
confdb2ldap <basedn> [<config object base>]
DESCRIPTION
confdb2ldif reads the cluster configuration from the openais object database and generates an LDIF file suitable for importing into an LDAP
database. The LDIF file is written to standard output.
OPTIONS
<basedn>
This is the base DN of the LDAP server into which the configuration will be imported. confdb2ldif will create a "cn=cluster" object
below this to contain the cluster configuration. The base DN is usually derived from the host's domain name. So if the host is
ldapsrv.mycorp.com then the base DN could be dc=mycorp,dc=com.
[<config object base>]
Configuration object in the objdb to start from. This defaults to "cluster" and there should rarely be any need to change it.
COMMENTS
confdb2ldif uses the openais libconfdb to read the configuration. The default way to do this is run against a running aisexec to read the
live configuration. It is possible to generate an LDIF file from a non-running system by using the standalone feature of openais's lib-
confdb.
eg to read the configuration from /etc/cluster/cluster.conf, use the following command:
OPENAIS_DEFAULT_CONFIG_IFACE=xmlconfig:cmanpreconfig confdb2ldif dc=mycompany,dc=com
or to do it from CCS
OPENAIS_DEFAULT_CONFIG_IFACE=ccsconfig:cmanpreconfig confdb2ldif dc=mycompany,dc=com
The LDIF file is written to stdout and so can be saved or piped straight into ldapmodify if required.
It's important that the 99cluster.ldif schema file has been loaded into the LDAP server before adding the contents of this generated LDIF
file.
EXAMPLE
confdb2ldif dc=mycorp,dc=com | ldapmodify -x -a -D"cn=Directory Manager" -c -v -W
BUGS
confdb2ldif parses the cluster configuration without checking it against the loaded schema. So if there are attributes in the config file
that are not known to the schema, parts of the load will fail. It is important to check the results of feeding the output into ldapmodify.
In particular aisexec logging operations will not convert into LDIF because they rely on duplicate keys.
SEE ALSO libconfdb(3), openais(8), cluster.conf(5)confdb2ldif(8)