More info I found a far more revealing error message related to this issue in convertd.log:
2007-08-02 08:06:54,632 FATAL [Convertd-256] [] system - Fatal error occurred while handling connection
java.lang.UnsatisfiedLinkError: /opt/zimbra/verity/FilterSDK/bin/libKeyViewFilter.so: /opt/zimbra/verity/FilterSDK/bin/libKeyViewFilter.so: cannot open shared object file: No such file or directory
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.jav a:1751)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java :1676)
at java.lang.Runtime.loadLibrary0(Runtime.java:822)
at java.lang.System.loadLibrary(System.java:993)
at com.verity.api.filter.Filter.(Unknown Source)
at com.zimbra.cs.convertd.VerityEngine.extract(Verity Engine.java:239)
at com.zimbra.cs.convertd.TransformationHandler.doTex tExtraction(TransformationHandler.java:203)
at com.zimbra.cs.convertd.TransformationHandler.proce ssCommand(TransformationHandler.java:116)
at com.zimbra.cs.tcpserver.ProtocolHandler.processCon nection(ProtocolHandler.java:231)
at com.zimbra.cs.tcpserver.ProtocolHandler.run(Protoc olHandler.java:198)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
This appears to be a Verity issue. The pre-compiled shared libraries that come with Zimbra for Verity seem to have a problem with my system. This could be because of my kernel or something else.
I realize that the timestamp is different, but I reproduced the problem multiple times. This exact same error occurred at "2007-08-01 17:10:36", matching the above error log.
Is there another location to obtain Verity shared libraries for different platforms or with different compile options?
Thanks,
Cory
Last edited by Myrddin; 08-02-2007 at 08:47 AM..
Reason: Added explanation for mismatched times
|