Dejan Muhamedagic wrote:
> Perhaps to cleanup/restart a resource. Try:
>
> crm_resource -C -r db-sql1-shooter
> crm_resource -C -r db-sql3-shooter
>
> If everything fails, you may file a bugzilla with hb_report.
Hi, Dejan.
It didn't worked.
Following your suggestion, I prepared to run hb_report and file a
bug-report on this.
Before running hb_report, I executed this preparation steps:
1. Stop the cfengine process (which monitors the existence of a
heartbeat process and tries to start one up in case of absence);
2. Generate ssh keys for the root user on both machines, and make sure
that the ~root/.ssh/authorized_keys had the appropriated keys and
configuration to allow a root login from the other host;
3. Take the heartbeat to a full halt;
4. Poke logrotate with --force and rotate all the log files;
5. Take the heartbeat process up again;
At this point, I noticed that there was no errors anymore.
I am really confused. Can someone here please explain to me what did I
do wrong to start with?
It's been a stressful process for too long already. I would like to know
from the others if it also toke them up to one year before they had a
working cluster, or if - for some reason - my case was an exceptional one.
If you consider this an interesting case, I can still send you the
report generated by hb_report. I still have another cluster to go
through the same process, so it's quite possible that I can reproduce
the error at least once more. Please let me know about your interest on
this.
Thank you very much for your support and tips, Dejan. You were a
life-saver. I own you a pornographically big quantity of
${YOUR_FAVOURITE_DRINK}. Please let me know where to deliver it. :)
Kind regards.
--
Luis Motta Campos is a software engineer,
Perl Programmer, foodie and photographer.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
