Bug 7589 - Ganglia gmond service - Module python_module failed to initialize
Summary: Ganglia gmond service - Module python_module failed to initialize
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Johnny A. Solbu
QA Contact:
URL:
Whiteboard: NEEDHELP
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-26 16:34 CEST by claire robinson
Modified: 2013-11-23 16:13 CET (History)
4 users (show)

See Also:
Source RPM: ganglia
CVE:
Status comment:


Attachments
ganglia 32 bit config.h (8.29 KB, text/plain)
2012-12-27 15:57 CET, Johnny A. Solbu
Details

Description claire robinson 2012-09-26 16:34:51 CEST
Created to allow a security update to be pushed. 

(See also bug 6874 - No response from packager)

Seems only on Mga2

# systemctl status gmond.service

/usr/sbin/gmond[14492]: [PYTHON] Can't open the python module path
/usr/lib64/ganglia/python_modules.
/usr/sbin/gmond[14492]: Module python_module failed to initialize.
gmond[14459]: Starting GANGLIA gmond: [  OK  ]
Manuel Hiebel 2012-10-07 11:37:27 CEST

CC: (none) => ennael1, guillomovitch

Comment 1 Johnny A. Solbu 2012-12-21 00:34:37 CET
I can't reproduce it. Is it still valid?

CC: (none) => johnny

Johnny A. Solbu 2012-12-21 00:39:47 CET

Status: NEW => ASSIGNED
Assignee: bugsquad => johnny

Guillaume Rousse 2012-12-21 09:28:02 CET

CC: guillomovitch => (none)

Comment 2 Johnny A. Solbu 2012-12-21 15:33:10 CET
I can finally reproduce in on my new mga2 32 bit VM. and I have no idea what causes it.
I don't know what to change to fix it.
Comment 3 Joseph Wang 2012-12-21 17:50:18 CET
It looks like a problem in the configure script that figures out whether to search /usr/lib or /usr/lib64 for the python modules, which is a problem if you are doing a 
cross-compile.  Something you might try is looking at the configure commands and making sure that everything is being set to /usr/lib rather than /usr/lib64

CC: (none) => joequant

Comment 4 Joseph Wang 2012-12-23 04:48:15 CET
Looking over the code.  I see the issue

Ganglia gets it's moduledir from the symbol GANGLIA_MODULE_DIR config.h and that is being set by the configure symbol moduledir.

Try this

change the configure line to

%configure2_5x --with-gmetad --enable-status --with-moduledir=%{_libdir}/ganglia

Build it and then once you have that look at the config.h that is generated in the directory, you should see

/* GANGLIA_MODULE_DIR */
#define GANGLIA_MODULE_DIR "/usr/lib64/ganglia"

Defined correctly
Comment 5 Johnny A. Solbu 2012-12-23 05:50:20 CET
The configure line change does Nothing.
(Note that this error Only happens on 32 bit install, Not 64 bit).

Ergo it isn't installing libs into the wrong place. As far as I can see, the current ganglia release (3.1.7-7.1) packaged and install the libs in the correct dir.
Comment 6 Joseph Wang 2012-12-23 07:19:50 CET
Can you upload the config.h file that gets generated by the configure.

The modules are getting installed in the right place.  The problem is that there is an
internal symbol that is pointing gmond to the wrong directory.

I'll try a compile with iurt to see if I can reproduce.
Comment 7 Johnny A. Solbu 2012-12-27 15:57:27 CET
Created attachment 3296 [details]
ganglia 32 bit config.h
Comment 8 Marc Lattemann 2013-02-05 22:59:11 CET
after update to ganglia-3.1.7-7.2mga2 (refering to https://bugs.mageia.org/show_bug.cgi?id=7586) still got the same error message:

[root@MGA2_32BIT test]# systemctl status gmond.service
gmond.service - LSB: gmond startup script
	  Loaded: loaded (/etc/rc.d/init.d/gmond)
	  Active: active (running) since Tue, 05 Feb 2013 22:46:37 +0100; 11min ago
	  CGroup: name=systemd:/system/gmond.service
		  รข 3058 /usr/sbin/gmond

Feb 05 22:46:37 MGA2_32BIT /usr/sbin/gmond[3058]: [PYTHON] Can't open the python module path /usr/lib/ganglia/python_modules.
Feb 05 22:46:37 MGA2_32BIT /usr/sbin/gmond[3058]: Module python_module failed to initialize.
Feb 05 22:46:37 MGA2_32BIT gmond[3024]: Starting GANGLIA gmond: [  OK  ]

CC: (none) => marc.lattemann

Comment 9 Johnny A. Solbu 2013-02-21 12:04:48 CET
I can't figure this out, so if anyone know how to fix it, be my guest.

Status: ASSIGNED => NEW
Whiteboard: (none) => NEEDHELP

Comment 10 Manuel Hiebel 2013-10-22 12:10:31 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 11 Manuel Hiebel 2013-11-23 16:13:58 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.