[Fwd: RE: cannot open shared object file]

Christian <[email protected]> Wed, 20 Jul 2005 21:03:58 +0200
Newsgroups gmane.comp.sysutils.modular-log-analyzer
Message-ID <[email protected]>
...and since all replies were made off-list, i forward this mail so that 
it'll find its place in the archive of this high-traffic mailinglist ;)

--------snip-----------


Christian,

I know about this "WARNING: ModLogAn is running as user 'root'." but thanks
for reminding me. :) I need to take the -r out when I make it a cron job.

I didn't try your suggesting because the ldconfig command Thomas suggested
worked.

Thanks for the reply though, :)

Terre

-----Original Message-----
From: Christian [mailto:[email protected]]
Sent: Wednesday, July 20, 2005 9:54 AM
To: [email protected]
Cc: Terre Porter
Subject: Re: [modlogan] cannot open shared object file


Terre Porter schrieb:
> Hi,
>
> I'm trying to get modlogan setup on my server and i've run in to a
problem.
>
> Could anyone point me in the right direction?
>
> # /home/tbnweek/modlogrun.pl /home/tbnweek/public_html/modlogan/logs/
> Processing 2005/07/access.log-2005.07.18...
> modlogan 0.8.13
> WARNING: ModLogAn is running as user 'root'.

uh, please *don't*.

> mplugins.c.135: libgd.so.2: cannot open shared object file: No such file
or
> directory -> /usr/local/lib/libmla_output_modlogan.so
> main.c.689: reading configfile failed - going down hard
>
> I've looked and the file libgd.so.2 is located in /usr/local/lib, and the
> libmla_output_modlogan.so is also in that same directory. So i'm kinda
lost
> on what is missing.

but where does your modlogan binary expects libgd.so.2?
did you compile modlogan yourself or did you just install a (binary)
package? the (linux?) distributions should take care of proper linking.

try this:

% su -c "strace modlogan -c modlogan.conf 2>&1 | grep libgd" www-data
open("/usr/lib/libgd.so.2", O_RDONLY)   = 5
---------------^
   this is, what it get. and /usr/lib/libgd.so.2 does exist here.

Christian.
--
BOFH excuse #111:

The salesman drove over the CPU board.



-- 
BOFH excuse #45:

virus attack, luser responsible