On Thu, May 08, 2008 at 02:06:21PM +0200, Andrew Beekhof wrote:
> On Thu, May 8, 2008 at 1:52 PM, Madd Sauer <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > On Wed, Apr 30, 2008 at 07:34:30PM +0200, Andrew Beekhof wrote:
> >  > On Wed, Apr 30, 2008 at 2:59 PM, Madd Sauer <[EMAIL PROTECTED]> wrote:
> >
> > > >  On Wed, Apr 30, 2008 at 02:35:38PM +0200, Andrew Beekhof wrote:
> >  > >  > On Tue, Apr 29, 2008 at 6:31 PM, Madd Sauer <[EMAIL PROTECTED]> 
> > wrote:
> >  > >  > > Hello Maintainers,
> >  > >  > >
> >  > >  > >  I have some trouble with the id at rsc_location. I will show you 
> > that
> >  > >  > >  following example. I made a dump with cibadmin -Q > tmp.xml and 
> > paste
> >  > >  > >  these lines from the dump. (complete dump is attached on this 
> > mail.)
> >  > >  > >
> >  > >  > >  # This one DID NOT work
> >  > >  >
> >  > >  > Care to define "DID NOT work"?
> >  > >  sorry for to less information. that mean the resource will not startet
> >  > >  on node3 (or any other). It's an not-symmetric server. if no rule is
> >  > >  def. so the resource will not started.
> >  > >
> >  > > > >  -------8<-----------
> >  > >  > >   <rsc_location id="rscloc_sys01-ses" rsc="sys01-ses">
> >  > >  > >     <rule id="prefered_rscloc_sys01-ses" score="400">
> >  > >  > >       <expression attribute="#uname" id="444a.." operation="eq" 
> > value="node3"/>
> >  > >  > >     </rule>
> >  > >  > >   </rsc_location>
> >  > >  > >  -------8<-----------
> >  > >  > >
> >  > >  > >  #This one DID work! I changed id="" to another value
> >  > >  >
> >  > >  > and the score... which is likely what made the difference
> >  > >  not in this case. I tried several values (lower, equal, and "444" 
> > every
> >  > >  time with the same result.
> >  >
> >  > that behavior doesn't make any sense :-(
> >  > the id isn't used for anything except updating or removing it from the
> >  > configuration
> >  >
> >  > logs?
> >
> >  sorry, for late response. I haven't found anything helpfull in the logs. I 
> > update
> >  the heartbeat to 2.1.3 [1] and analyse again. The result is that the script
> >  generated xml works like expected. One problem solved and another raised
> >  up. I cannot start mgmtd and keep running. No hb_gui can connect.
> >  crm_mon shows all resources. May be I should open a new thread for this
> >  problem.
> 
> you installed the pygui package?

yes,
<screenshot>
msat1mm:~ # rug search pygui
S | Catalog         | Bundle | Name                      | Version |Arch
--+-----------------+--------+---------------------------+---------+-----
i | System packages |        | pacemaker-pygui           | 1.3-6.1 |i586
i | System packages |        | pacemaker-pygui-debuginfo | 1.3-6.1 |i586
</screenshot>
> 
> >
> >  [1] 
> > (http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/i586/)
> >
> >
> >
> >  > >
> >  > >
> >  > >
> >  > >  > >  -------8<-----------
> >  > >  > >   <rsc_location id="place_001" rsc="sys01-ses">
> >  > >  > >     <rule id="prefered_place_001" score="444">
> >  > >  > >       <expression attribute="#uname" id="c46b.." operation="eq" 
> > value="node3"/>
> >  > >  > >     </rule>
> >  > >  > >   <rsc_location>
> >  > >  > >  -------8<-----------
> >  > >  > >
> >  > >  > >  Did I made a mistake, or could that be a bug?
> >  > >
> >  > >  > >  OS: SLES10 SP1
> >  > >  > >  HB: 2.08
> >  > >  > >
> >  > >  > >  may be there are more importend informations in the tmp.xml.
> >  > >  > >
> >  > >  > >  best regards
> >  > >  > >
> >  > >  > >  Madd Sauer
> >  _______________________________________________
> >  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
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to