On Wed, Apr 30, 2008 at 9:32 PM, Doug Knight <[EMAIL PROTECTED]> wrote: > Hi, > I am performing a rolling upgrade on a RHEL5 system. Old HA was 2.0.8, > upgrading to 2.1.3, Primary is 2.0.8 and up, secondary was the one being > upgraded. During the startup I encountered some issues with my OCF > scripts for our applications, which I have now corrected (mainly the > relocation of the ocf-shellfuncs, etc). The upgraded node did come up > and connect to the primary server (though it decided to try restarting > postgres locally when it wasn't supposed to, more in a later email, > maybe). There are two things that concern me. First, I saw a warning as > follows: > > WARN: crm_peer_init: Set these options via openais.conf
Did I not remove that line already? Ooops. Sorry, that was a "note-to-self" and is safe to ignore. > > I did not install AIS, I stayed with the heartbeat-only stack > (heartbeat, common, resource, heartbeat-pacemaker, etc). Should I be > concerned about this warning, and if so what should I do about it? > > Second, once I let the systems settle out and the logs got quiet, I > checked status on my resources. As noted previously, pgsql had problems. > I attempted to clean pgsql (crm_resource -C -r pgsql_5432, which stated > I needed to use -H, which I did), and I got an emergency condition in > heartbeat and it rebooted my server! So aside from the pgsql issue, how > can I prevent heartbeat from doing a reboot? There are other things > running on this server which a reboot plays havoc with, so I would like > to avoid a repeat if possible. need more logs - looks like the crmd is having trouble talking to the lrmd also, try "crm respawn" instead of "crm yes" Alan changed the default behavior to reboot the machine whenever a heartbeat process died :-/ _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
