[greenstone-users] Importing problem

From t.janssen@tesco.net
DateTue, 16 Dec 2003 12:11:17 +0000
Subject [greenstone-users] Importing problem
Hi all

Bit of a problem doing an import of collection of HTML files that worked fine in 2.40a. As I'm fairly new to GS I'd appreciate any pointers.

Basically, when 2.41 became available I uninstalled 2.40, installed 2.41 and copied over the old collect directory as mentioned by John McP in a previous post. This seemed to work fine and have been able to work with it with no problems.

That is, until I had to rebuild the collection. When I tried to run:

import -removeold <my collection name>

from the command line, I get the following error:

Uncaught exception from user code:
Can't load '/home/httpd/gsdl/perllib/cpan/auto/XML/Parser/Expat/Expat.so' for module XML::Parser::Expat: /home/httpd/gsdl/perllib/cpan/auto/XML/Parser/Expat/Expat.so: undefined symbol: PL_sv_undef at /usr/lib/perl5/5.8.0/i386-linux-thread-multi/DynaLoader.pm line 229.
at /home/httpd/gsdl/perllib/cpan/XML/Parser.pm line 14
Compilation failed in require at /home/httpd/gsdl/perllib/cpan/XML/Parser.pm line 14.
BEGIN failed--compilation aborted at /home/httpd/gsdl/perllib/cpan/XML/Parser.pm line 18.
Compilation failed in require at /home/httpd/gsdl/perllib/plugins/XMLPlug.pm line 36.
BEGIN failed--compilation aborted at /home/httpd/gsdl/perllib/plugins/XMLPlug.pm line 36.
Compilation failed in require at /home/httpd/gsdl/perllib/plugins/GAPlug.pm line 35.
BEGIN failed--compilation aborted at /home/httpd/gsdl/perllib/plugins/GAPlug.pm line 35.
Compilation failed in require at /home/httpd/gsdl/perllib/plugin.pm line 63.
plugin::load_plugins('ARRAY(0x822eabc)',2,'STDERR','import::FAILLOG') called at /home/httpd/gsdl/bin/script/import.pl line 403
import::main() called at /home/httpd/gsdl/bin/script/import.pl line 237

I then deleted the collection and tried creating the collection from scratch but with the same error.

The Collector also fails when I try to build the collection, presumably from the same reason.

error.txt contains no indication as to the problem.

I presume this is a problem with my OS distribution.
I am running 2.41 on Red Hat 9.
Any ideas, anyone?

Thanks kindly.

Tom Janssen