On Wed, Jun 25, 2008 at 13:44, Junko IKEDA <[EMAIL PROTECTED]> wrote: >> > > Ah ok, sorry just wanted to make sure the intended functionality was >> > clear. >> > > I had a look at the report and analysis.txt highlights the problem > quite >> > well: >> > > >> > > pengine[20727]: 2008/06/23_11:02:40 ERROR: unpack_rsc_op: Hard error: >> > > prmApPostgreSQLDB_fail_60000 failed with rc=2. >> > > pengine[20727]: 2008/06/23_11:02:40 ERROR: unpack_rsc_op: Preventing >> > > prmApPostgreSQLDB from re-starting anywhere in the cluster >> > > >> > > It looks like the RA (incorrectly) returned 2 (invalid parameter), >> > > instead of 3 (unimplemented function). >> > > rc=2 tells the cluster that the configuration is invalid and not to >> > > bother starting the resource elsewhere. >> > >> > !!! that means, there might be a problem at pgsql RA? >> >> hb_report-with-pgsql/x3650b/ha-log/txt >> line 1118: >> crmd[4109]: 2008/06/20_16:21:38 info: process_lrm_event: LRM operation >> prmApPostgreSQLDB_monitor_0 (call=6, rc=7, cib-update=30, confirmed=true) >> complete >> >> It seems that return code is "7" at this time. >> >> line 1200: >> crmd[4109]: 2008/06/20_16:24:40 info: process_graph_event: Action >> prmApPostgreSQLDB_fail_60000 (0:2;0:0:crm-resource-4265) initiated by a >> different transitioner >> >> line 1202: >> crmd[4109]: 2008/06/20_16:24:40 WARN: update_failcount: Updating failcount >> for prmApPostgreSQLDB on 6f0ddbd3-848d-483b-805e-42612af62e64 after failed >> fail: rc=2 (update=value++, time=1213946680) >> >> is this "rc" equal as "rc" in line 1118? > > Sorry, I went in the wrong direction... > In the case of without pgsql, > process_lrm_event() catch rc=7, and then > update_failcount() catch rc=2.
two different events :-) one is the probe (prmApPostgreSQLDB_monitor_0) and the other is the async failure (prmApPostgreSQLDB_fail_60000) _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems