Personally I cannot stand Verity. It's expensive, inaccurate and a pain to configure properly. If you need search, do yourself a favor and buy a Google Appliance. Ask yourself why Adobe¹ doesn't use it on their own website (they use Google). If you absolutely must use it, here are a few problems you may encounter during the installation.

Common Problems

Failed to retrieve style path

I've had this happen on a few Linux servers; for some unknown (and unlogged) reason Verity is not installed properly during the ColdFusion installation and you receive the following error when you try and create a new collection:

Unable to create collection [collection name].
An error occurred while creating the collection: com.verity.api.administration.ConfigurationException: Failed to retrieve style path. (-6044)

This happens all the time. Adobe has a TechNote, KB400683, and Doug Hughes has a long writeup on this exact issue. Both are helpful, and the important things to remember are:

• Don't run it as any user without a shell of /bin/bash (see the RUNTIME_USER variable in verity-install.sh).
• Make sure the Verity installation directory (eg, /opt/coldfusionmx7/verity) is owned by the user you specified in RUNTIME_USER.
• Make sure there aren't any leftover k2server processes running from a previous failed install:
  ps -aux | grep k2
• You must uninstall (verity-uninstall.sh) before you reinstall (verity-install.sh).

rcadmin will not run

This usually suggests an issue with your installation, but if you are sure that is not the case the following command will work (make sure you use the correct path for the Verity installation directory):

$ cd /opt/coldfusionmx7/verity/k2/_ilnx21/bin/
$ LD_LIBRARY_PATH=. ldd ./rcadmin

Remember – you can see which shared libraries a binary uses with the ldd command, for example:

$ ldd ./rcadmin
        linux-gate.so.1 =>  (0x00f38000)
        libvi18n.so => not found
        libdl.so.2 => /lib/libdl.so.2 (0x00868000)
        libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x008b6000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x00897000)
        libm.so.6 => /lib/libm.so.6 (0x0086e000)
        libc.so.6 => /lib/libc.so.6 (0x00729000)
        /lib/ld-linux.so.2 (0x00707000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x0098e000)

Bad Interpreter

Another error that I ran into today was:

/opt/coldfusionmx7/verity/k2/_ilnx21/bin/vdiag.sh: /bin/sh^M: bad interpreter: No such file or directory

Fortunately it is an easy problem to fix:
dos2unix /opt/coldfusionmx7/verity/k2/_ilnx21/bin/vdiag.sh

Both bash and sh choke on carriage returns, the dos2unix command simply removes the carriage returns from the file.

FIN

Happy searching, and enjoy your sub-par results!

1. And Macromedia before they were bought [back]

Posted on Wednesday, September 12th, 2007 at 3:13 pm | Filed under Development, Software, Technology
You can follow any responses to this entry through the Comments feed.
Post a Comment | Trackback URL | Permalink URL