On Thu, Jul 3, 2008 at 09:31, Michael Alger <[EMAIL PROTECTED]> wrote: > On Thu, Jul 03, 2008 at 08:53:35AM +0200, Patrik Martinsson wrote: >> When i use cibadmin to update my cib, the actual cluster gets >> updated but the actual file, cib.xml, doesn't, which ofcourse >> means that, if i take down heartbeat and start it again it will >> read from the cib.xml which is the old one, meaning old settings. >> >> Wouldn't it be better if cibadmin actually wrote to the cib.xml ? >> Or as i stated above, am i missing something here ? > > It's definitely supposed to automatically update the on-disc copy > after any changes are made. Have you checked the logs to see if > there's any references to the file? > > When you're updating it, are you first replacing the one in the > /var/lib/heartbeat/crm location, and then loading that? I'm not sure > how heartbeat manages it precisely, but it does check the .sig files > to make sure it hasn't been modified. I'm not sure if modifying it > will prevent it from automatically writing it out;
it will or at least it will in older versions, i think newer versions move the modified file out of the way and keep writing. > or perhaps the > heartbeat user simply doesn't have permission to write to these > files if they've been created by your configuration management > system? > > On my system, it certainly writes any changes that I've imported > using cibadmin to disc right away, on both nodes. > _______________________________________________ > 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
