Description of problem: Configuration of PostgreSQL Server 8 resource type via system config cluster reflects different values at /etc/cluster/cluster.conf and the service doesn't start at all. Version-Release number of selected component (if applicable): Kernel Version : 2.6.18-92.el5xen #1 SMP Tue Apr 29 13:45:57 EDT 2008 i686 i686 i386 GNU/Linux cman-2.0.84-2.el5 rgmanager-2.0.38-2.el5_2.1 How reproducible: Configure the postgreSQL server 8 resource and check cluster.conf file. Steps to Reproduce: 1.Install Cluster packages. 2. Configure postgreSQL Server 8 Resource type for the postgresql service via system-config-cluster 3. Start the service and it will fail. Check Cluster.conf for umached values. Actual results: Service Postgresql Failed. Expected results: Service Postgresql should start automatically Additional info: If the postgresql service configured via script then it works fine.
Created attachment 312418 [details] Deatils of cluster.conf attached
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Done - ready for commit.
I'm getting an improperly written cluster.conf. Here's the line: <postgres-8 config_file="" name="90" postmaster_options="foobar.conf" postmaster_user="postmaster" shutdown_wait="foobarname"/> in system-config-cluster I set config_file == foobar.conf postmaster options == <empty> shutdown_wait == 90
This will need to be moved out. A release note would be a good interim strategy. Release Note Draft: A problem exists when using system-config-cluster to configure a Postgres 8 resource agant. To include a Postgres resource agent in your cluster, please check the man page for the agent, and edit the cluster.conf file in an editor, then update the cluster with the new configuration file using the appropriate cman_tool command.
system-config-cluster-1.0.55-1.0 fails QA testing
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: A problem exists when using system-config-cluster to configure a Postgres 8 resource agent. To include a Postgres resource agent in your cluster, please check the man page for the agent, and edit the cluster.conf file in an editor, then update the cluster with the new configuration file using the appropriate cman_tool command.
Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,5 +1 @@ -A problem exists when using system-config-cluster to configure a Postgres 8 +An issue may be encountered when using system-config-cluster to configure a Postgres 8 resource agent, resulting in the postgresql service failing to start. To include a Postgres resource agent in your cluster, please check the man page for the agent, and edit the cluster.conf file in an editor, then update the cluster with the new configuration file using the appropriate cman_tool command.-resource agent. To include a Postgres resource agent in your cluster, please -check the man page for the agent, and edit the cluster.conf file in an editor, -then update the cluster with the new configuration file using the appropriate -cman_tool command.
All set now.
fix verified in luci-0.12.2-6.el5 previous cluster.conf errors that I noted above are no longer present.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1401.html