>>> On 11/7/2007 at 7:51 PM, in message <[EMAIL PROTECTED]>, "Dan Hushon" <[EMAIL PROTECTED]> wrote: > Trying to compile current trunk (860) against SUSE 10.1 SP1 on multi-core.... > > anyways, I am able to build everything including the rpms.... but > after installing the rpms I am getting the following message on gmond > startup: > > # ./gmond > Cannot load /usr/lib/ganglia/modmulticpu.so metric module: > /usr/lib/ganglia/modmulticpu.so: cannot open shared object file: No > such file or directory > > Cannot load /usr/lib/ganglia/modpython.so metric module: > /usr/lib/ganglia/modpython.so: cannot open shared object file: No such > file or directory > > it's right, there are no /usr/lib/ganglia files, but these modules do > exist in /usr/lib64/ganglia... a simple logical link ln -s > /usr/lib64/ganglia /usr/lib/ganglia fixes things.... > > thanks for the great work on multicore... Bernard et al. >
This is just a pathing problem in the .conf file. On a 64-bit machine the library files (ie. the .so's) are written to a lib64 directory rather than lib. Each of the module .conf files contain a path to where gmond can find the .so file. The path in the .conf files just needs to be changed. We should probably write a small awk script that fixes up the .conf files for 64-bit machines during the RPM build. Brad ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
