Hi, Andrew Beekhof <[EMAIL PROTECTED]> wrote: > > On Jan 21, 2008, at 12:52 PM, Sebastian Reitenbach wrote: > > > Hi, > > > > Sebastian Reitenbach <[EMAIL PROTECTED]>,General Linux-HA > > mailing list <[email protected]> wrote: > >> Hi, > >> Andrew Beekhof <[EMAIL PROTECTED]> wrote: > >>> > >>> On Jan 10, 2008, at 6:16 PM, Sebastian Reitenbach wrote: > >>> > >>>> Hi, > >>>> > >>>> on the download area, there are the pointers to the suse build > >>>> service, > >>>> providing rpms for opensuse versions and others. But there is still > >>>> only > >>>> heartbeat-2.1.2- sth. > >>>> Is this intentional or is there sth. wrong? > >>> > >>> they're pretty close to what ended up in 2.1.3 > >>> i'll update them shortly when I do the first pacemaker release > >>> > >> ah, ok, that's fine. > > I just wanted use the rpm packages for heartbeat 2.1.3 on SLES10SP1. > > > > I installed these rpm packets: > > heartbeat-2.1.3-3.1.x86_64.rpm > > heartbeat-ldirectord-2.1.3-3.1.x86_64.rpm > > heartbeat-common-2.1.3-3.1.x86_64.rpm > > heartbeat-resources-2.1.3-3.1.x86_64.rpm > > > > and had to find out, that the heartbeat-gui and the crm stuff, and > > maybe > > more, seems to be missing. Is that intentionally left out, as the > > rpm names > > also changed a bit? I thought the heartbeat 2.1.3 version is the > > last one > > where the crm is still in heartbeat? > > Now that Pacemaker 0.6.0 is out, the built-in CRM is no longer > supported (all bugs will be fixed in Pacemaker). > Thus the Heartbeat packages on the build service are built without the > built-in CRM. > Check the changelog in the Heartbeat package for exactly what is no > longer included. yeah, my fault to not read that file ;)
> > One thing I like about .deb is that you can recommend other packages > to install. > This would have alerted to you that something was missing - alas there > is no such mechanism for rpm. > > > Do I have to install the pacemaker-* and openais* rpm's to get the > > functionality back? How well is the pacemaker-* stuff tested, is > > that ready > > for production systems, or should I better stay with a heartbeat > > 2.1.2 or > > the versions that install with SLES10SP1? > > If you only wish to use the heartbeat stack, you only need one extra > rpm: pacemaker-heartbeat yeah, just basically the same functionality as with 2.1.2 is wanted. > > It contains essentially the same CRM code that was in 2.1.3 and is no > more/less production ready than what was in 2.1.3. > You can see the testing criteria for releases at: > http://www.clusterlabs.org/mw/Release_Testing > > For the GUI, you'll need the pacemaker-pygui package. > > The list of packages is described at: > http://www.clusterlabs.org/mw/Install#Package_List > > hope that helps yes, that helped, I installed both rpm's, but now, when I want to start the hb_gui, I get the following error: Traceback (most recent call last): File "/usr/bin/hb_gui", line 35, in ? from pymgmt import * ImportError: No module named pymgmt These files are installed: find /usr/ -name "*pymgmt*" /usr/lib64/heartbeat-gui/pymgmt.pyc /usr/lib64/heartbeat-gui/_pymgmt.so.0 /usr/lib64/heartbeat-gui/_pymgmt.so.0.0.0 /usr/lib64/heartbeat-gui/pymgmt.py I also created a symbolic link from _pymgmt.so.0 to _pymgmt.so, because I found a _pymgmt.so file in the same directory, that was installed on another SLES box with heartbeat 2.1.2, but that did not helped. so I removed the 2.1.3 rpm's and installed the 2.1.2, and the hb_gui is working on that box, so at least no basic python stuff seems to be missing. So there must still sth. missing to get the GUI working again, any more idea? cheers Sebastian _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
