[greenstone-users] Re: [greenstone-devel] remote client authentication problem

From Anupama of Greenstone Team
DateWed Apr 21 16:02:34 2010
Subject [greenstone-users] Re: [greenstone-devel] remote client authentication problem
In-Reply-To (4BCE016F-9010302-bates-edu)
Hi Jim

1. The XML parse error is in all likelihood due to something happening
during the generation of the XML that describes the plugins. This would
cause the closing </PluginList> tag to be left out, and that would then
present you with the error message you see.

To find out more about the issue can you do the following:

a. Use a terminal to go into your Greenstone installation folder.

b. Type:
source setup.bash

c. Now type:
perl -S pluginfo.pl -listall

See if any of the XML it spews out is not properly terminated with
closing tags. If you don't know what to look for, can you send me the
output? You can write the output out to a file with the following (and
then send the file to me):
perl -S pluginfo.pl -listall > listall.txt

d. If the above didn't show up any glaring inconsistencies that you
could identify, could you type:
perl -S pluginfo.pl -describeall

Once again, can you tell me of any errors you can easily spot, or
otherwise send me the output by typing:
perl -S pluginfo.pl -describeall > describeall.txt

2. You wrote
> Now, there's a different problem. As part of downloading the
> configuration, there's a process that builds a .zip file. It's failing
> with a java exception. The germane part of the Apache log is attached.

AND you had written in your previous e-mail:

> The setup (setup.bash) in 2.83 for Linux doesn't include '/usr/lib'
in > LD_LIBRARY_PATH. This can cause problems with finding the standard
> libraries. I added it as 'local/setup.bash'.


I had a look at the Java exceptions that were showing up in your apache
log file. It complained of the following:

Tue Apr 20 15:10:21 2010] [error] [client 134.181.188.15]
java.lang.IllegalArgumentException: month out of range:350888
[Tue Apr 20 15:10:21 2010] [error] [client 134.181.188.15] at
gnu.java.util.ZoneInfo.getOffset(int, int, int, int, int, int)
(/usr/lib/libgcj.so.5.0.0)
[Tue Apr 20 15:10:21 2010] [error] [client 134.181.188.15] at
java.util.GregorianCalendar.computeFields() (/usr/lib/libgcj.so.5.0.0)
[Tue Apr 20 15:10:21 2010] [error] [client 134.181.188.15] at
java.util.Calendar.setTimeInMillis(long) (/usr/lib/libgcj.so.5.0.0)
[Tue Apr 20 15:10:21 2010] [error] [client 134.181.188.15] at
java.util.Calendar.setTime(java.util.Date) (/usr/lib/libgcj.so.5.0.0)
[Tue Apr 20 15:10:21 2010] [error] [client 134.181.188.15] at
java.util.zip.ZipEntry.setTime(long) (/usr/lib/libgcj.so.5.0.0)
[Tue Apr 20 15:10:21 2010] [error] [client 134.181.188.15] at
java.util.zip.ZipOutputStream.putNextEn
[Tue Apr 20 15:10:21 2010] [error] [client 134.181.188.15]
try(java.util.zip.ZipEntry) (/usr/lib/libgcj.so.5.0.0)

I googled the topmost exception and a number of people seem to have
encountered this issue and the specific exception does indeed look to
have to do with a number conversion problem.

However, as you can see above, the code is using the library
usr/lib/libgcj.so.5.0.0. I've just been told that libgcj is the GNU
Compiler for Java. But Greenstone is made to support only the Sun
version of Java. And we include their JRE in the Greenstone release.
However, because you have include /usr/lib in your LD_LIBRARY_PATH (I'm
guessing you prefixed the /usr/lib to it?), it could at times be
overriding the Java that Greenstone included and using your GNU libraries.

Therefore, could you try the following:

a) In a fresh terminal, remove the /usr/lib from your LD_LIBRARY_PATH
and see if there are still problems finding the standard libraries that
didn't get solved when you fixed the remote authentication problem.

b) If the above didn't work, then you could perhaps try adding /usr/lib
to the end of the LD_LIBRARY_PATH instead of pre-fixing it.

See if the Java exceptions are no longer being thrown when zipping.

Tell me how the above went, what works/doesn't work and where things go
wrong. Anything interesting you note (and which I haven't asked for)
would also be useful, I'm guessing. Thanks for your error reporting so
far, it's been helpful and makes the issues you're facing less cryptic
for me.

Regards,
Anupama