SUMMARY: Perl related problem in INND

I have observed this problem in
8.1 to 9.0b2 upgrade,
on a 9.0b4 fresh install,
and now in 9.0RC1fresh install.

INND cannot be started as installed because a shared library cannot be
located.

Here is the command line dialog in which I start innd and then check its
status:

[root@jerryAthlon root]# /etc/rc.d/init.d/innd start
Starting INND system:                                           [  OK  ]
[root@jerryAthlon root]# /etc/rc.d/init.d/innd status
innd dead but subsys locked
[root@jerryAthlon root]#

I looked in the /var/log/syslog and found the following lines related to the
innd start:

Sep  3 16:27:01 athlon rc.news: Starting innd.
Sep  3 16:27:01 athlon inndstart: Reading config from /etc/news/inn.conf
Sep  3 16:27:01 athlon rc.news: /usr/bin/innd: error while loading shared
libraries: libperl.so: cannot open shared object file: No such file or
directory
Sep  3 16:27:01 athlon sh: rc.news startup succeeded

I figured that I could update the list of library file locations, this
problem might be solved so I did the following:
[root@jerryAthlon etc]# locate libperl.so
/usr/lib/perl5/5.8.0/i386-linux-thread-multi/CORE/libperl.so

So, I added this path to the end of the /etc/ld.so.conf file and executed
the command:
/sbin/ldconfig -v

Now when I try to start INND the results are different, the library is
located, but the system still is unusable. Here are the related lines from
the /var/log/syslog file:

Sep  3 16:48:34 athlon rc.news: Starting innd.
Sep  3 16:48:34 athlon inndstart: Reading config from /etc/news/inn.conf
Sep  3 16:48:34 athlon rc.news: /usr/bin/innd: relocation error:
/usr/bin/innd: undefined symbol: PL_markstack_ptr
Sep  3 16:48:34 athlon sh: rc.news startup succeeded

but the innd system is still not working:

[root@jerryAthlon etc]# /etc/rc.d/init.d/innd status
innd dead but subsys locked

--------------------------------------------------------------------

Has anyone else seen this problem, or a related issue?
Any suggestions ?
Did I do the right thing when the initial "libperl.so not found" error
occurred?

Jerry Whelan






Reply via email to