Hi Alan, Interesting. This entry in the cib was completely created from the GUI. I modified the Transition Timeout from the GUI to get around the timeout of my notify function call. So if I understand what you're saying, I should remove the tags from the op definition and create nvpairs to replace them.
By the way, I checked out the link you sent with the GUI information. Unfortunately the system I use for the web and email is also the server on which we run our apps, and it has no sound ability at all (I'm probably lucky its not headless ;) I'll check your page out over the weekend from my laptop. Doug On Thu, 2007-04-05 at 12:36 -0600, Alan Robertson wrote: > Doug Knight wrote: > > Here's another thing I'm seeing with the notify function. It keeps > > timing out on my slave startup (post-promote-notify and > > post-start-notify). I'm triggering the start by using the cleanup > > resources button on the GUI for the slave's resource: > > > > crmd[13681]: 2007/04/05_13:16:47 ERROR: process_lrm_event: LRM operation > > rsc_pgsql_wal_5556:0_notify_0 (74) Timed Out (timeout=5000ms) > > > > Yet I have the timeout value for the notify function bumped up to 120: > > > > <op id="1e9ebbb8-a370-4d1e-8815-43d6f0fdcfd6" name="notify" > > timeout="120" start_delay="0" disabled="false" role=" > > Started"/> > > I believe this is incorrect. > The timeout, start_delay and role are meta-attributes which need > nvpairs. (The gui is confused about role - it thinks its a parameter). > > >
_______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
