In addition to the below mentioned issue, it seems that since I executed the cibadmin --cib_erase, I am now getting the following error in my log files:
cib[16212]: 2007/04/13_11:24:16 WARN: do_cib_notify: cib_modify of <cluster_property_set > FAILED: The object/attribute does not exist cib[16212]: 2007/04/13_11:24:16 ERROR: cib_process_request: cib_modify operation failed: The object/attribute does not exist cib[16212]: 2007/04/13_11:24:16 info: crm_log_message_adv: #========= Input message message start ==========# cib[16212]: 2007/04/13_11:24:16 info: MSG: Dumping message with 8 fields cib[16212]: 2007/04/13_11:24:16 info: MSG[0] : [t=cib] cib[16212]: 2007/04/13_11:24:16 info: MSG[1] : [cib_op=cib_modify] cib[16212]: 2007/04/13_11:24:16 info: MSG[2] : [cib_section=crm_config] cib[16212]: 2007/04/13_11:24:16 info: MSG[3] : [cib_callid=65] cib[16212]: 2007/04/13_11:24:16 info: MSG[4] : [cib_callopt=1052672] cib[16212]: 2007/04/13_11:24:16 info: MSG[5] : [(5)cib_calldata=0x6fb8b8(242 288)] cib[16212]: 2007/04/13_11:24:16 info: <cluster_property_set id="cib-bootstrap-options"> cib[16212]: 2007/04/13_11:24:16 info: <attributes> cib[16212]: 2007/04/13_11:24:16 info: <nvpair id="cib-bootstrap-options-last-lrm-refresh" name="last-lrm-refresh" value="1176477851"/> cib[16212]: 2007/04/13_11:24:16 info: </attributes> cib[16212]: 2007/04/13_11:24:16 info: </cluster_property_set> cib[16212]: 2007/04/13_11:24:16 info: MSG[6] : [cib_clientid=83a68273-8460-4ea5-be45-dc1d7e2916e2] cib[16212]: 2007/04/13_11:24:16 info: MSG[7] : [cib_clientname=16218] cib[16212]: 2007/04/13_11:24:16 WARN: cib_process_request: Request not broadcast: call failed: The object/attribute does not exist mgmtd[16218]: 2007/04/13_11:24:16 ERROR: cib_native_perform_op: Call failed: The object/attribute does not exist mgmtd[16218]: 2007/04/13_11:24:16 ERROR: update_attr: Error setting last-lrm-refresh=1176477851 (section=crm_config, set=cib-bootstrap-options): The object/attribute does not exist To top it off, I've configured a drbd OCF resource, using the provided OCF script, and when I start it up the processes only come up on one node. The replication node has its processes stopped when I click the start or default buttons on the GUI. Doug On Fri, 2007-04-13 at 09:15 -0400, Knight, Doug wrote: > I am trying to configure HB to monitor a drbd/postgreSQL configuration, > using the HB GUI. I have manually verified that drbd can be failed back > and forth between the two nodes in the HA cluster. I have also verified > that postgreSQL can run on either node, dependent upon the drbd device > being colocated and mounted with it. However, when I try to create a > group containing the drbd resource, I get an "activation failed" > response from the GUI and it won't create it. I started by executing a > cibadmin --cib_erase, so I started with a completely clean cib.xml. Then > I used the GUI to add a group, call it grp_pgsql_mirror. The first > resource I define is the drbd, call it rsc_drbd_7788, using the drbd > ocf/heartbeat-supplied script. Master/Slave ID is ms_drbd_7788. Once > I've entered all the info, clicking Add puts a small window up on the > screen with "Activation Failed" in it and an OK button. I'm trying to > use a group so I can fix the ordering of the resources I need to handle > the drbd/postgreSQL resource (i.e. drbd, filesystem, IP address, and > postgreSQL resources). I'm about ready to manually write the cib.xml, > but my XML writing skills aren't the best, and I would really prefer to > use a tool to create or make changes to the cib.xml. Any ideas or help > would be great. If anyone has a cib.xml with a similar configuration > they'd be willing to share, that would be great too. > > Thanks, > Doug Knight > WSI, Inc. > > _______________________________________________ > Linux-HA mailing list > [EMAIL PROTECTED] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [EMAIL PROTECTED] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
