On Tue, 2009-01-20 at 22:41 +0100, J. Friedrich wrote: > Hi everyone, > > at the moment I use heartbeat 2.0.8 on an aged RHEL 3 installation. I > built the packages myself and used the following configure parameters > for the build process: > > ./configure '--prefix=/usr' '--sysconfdir=/etc' '--localstatedir=/var' > '--libexecdir=/usr/lib' '--libdir=/usr/lib' '--enable-mgmt' > '--enable-ltdl-convenience' > > Unfortunately the pymgmt.py is not included in the built when > python2.2 is intalled. Also tried it directly from source, it also > lacks the pymgmgt.py file. When I use the same version and the same > parameters on a RedHat machine with python 2.3 or python 2.4 (i.e. > RHEL 4) it works flawlessly and like a charm. Am I right that at least > version 2.3 is needed to correctly build and install the HB gui? Never tested it with python < 2.3. But I think so.
> > I tried other RPMs of heartbeat from different sources, but everytime > I installed them and tried to run the GUI, I receive the following > error message (on the RHEL3, with Python 2.2) > > File "/usr/local/bin/hb_gui", line 34, in ? > from pymgmt import * > File "/usr/lib/heartbeat-gui/pymgmt.py", line 5, in ? > import _pymgmt > ImportError: dynamic module does not define init function (init_pymgmt) Were the RPMs built on the distribution you are using? > > I do not know much about Python, but it seems that the initialisation > has changed from Python 2.2 to Python 2.3/2.4. Am I correct? Is there > a way to get the GUI up and running with this rather old version of > Python? I don't think there's any easy way to do this. Besides, it requires pygtk > 2.4 > > I also tried to use the GUI from an Ubuntu system with heartbeat 2.1.3 > and python 2.5.2, and connect from there to the RHEL machine, but it > did not work. After inserting the credentials and clicking OK on the > Ubuntu machine, only a new dialogbox without any text but an OK button > appears, and on the RHEL machine the line > > mgmtd[14470]: 2009/01/20_21:30:04 ERROR: on_listen receive login msg failed > > is printed to the HA log and debug log file. No connect possible. Do I > have to use exavtly the same version on both, the server and the > client side? Yes > > Unfortunately, we can update the distribution because only this basis > is officially accepted and supported. It would take quite a long time > to explain why we can not update or change this, so lets just say that > it is not possible to upgrade the distribution to a (much more > favoured) RHEL4 or even RHEL5. We have several other machines based on > the same RHEL version, all of the in productive environments. So it > would be very nice (... and comfortable) to get this GUI up and > running on the RHEL server. You still can run the front-end of the GUI on a newer distribution, and connect to the back-end on the RHEL3, but the both sides should be the same version. > > Last but not least some of the installed packages on the machine: > > python-tools-2.2.3-6.6 > python-devel-2.2.3-6.6 > python-2.2.3-6.6 > heartbeat-2.0.8-1 > heartbeat-gui-2.0.8-1 > heartbeat-pils-2.0.8-1 > heartbeat-debuginfo-2.0.8-1 > heartbeat-ldirectord-2.0.8-1 > heartbeat-stonith-2.0.8-1 > swig-1.1p5-22 > > and the contents of the ha.cf file: > > debugfile /var/log/ha-debug > autojoin none > ucast eth0 1.2.3.4 > ucast eth1 1.3.5.6 > logfacility daemon > keepalive 2 > warntime 10 > deadtime 30 > initdead 60 > udpport 694 > auto_failback on > node nodename.mycompany.com > crm yes > > Thanks in advance for your help and your answers. Hope you can shed > some light on this issue. > -- Regards, Yan Gao China R&D Software Engineer [email protected] Novell, Inc. Making IT Work As One?6?4 _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
