cfsearch on ubuntu

I finally got vspider working on Ubuntu, and thought my problems were over. However, now that I've successfully spidered, it turns out that I can't cfsearch (see error, below). What's strange is that I can run vspider, and I can telnet to localhost:9950 and localhost:9960, but not localhost:9920 (connection refused), which is I guess the port that cfsearch uses. Here are the ports as shown in the advanced K2 Server Admin from the CF admin: Verity Host Name      K2 Admin Port 9950 K2 Server Port 9920 K2 Index Port 9960 Does anybody know how I might be able to kickstart listening on the "server" port? (Assuming that's the problem.) Otherwise, any other relevant ideas would be appreciated. Thanks, Jamie ================= Unable to connect to the ColdFusion MX Search service. On Windows you may need to start the ColdFusion MX Search Server from the services control panel. On Unix, you may need to run the 'cfmxsearch' script in the ColdFusion MX bin directory. Error: ------ com.verity.resource.PoolingException: cannot make connection to server at: k2://localhost:9920 ... ==================

----- Excess quoted text cut - see Original Post for more ----- Did you run this script? My guess is that the service simply isn't running. Does the user assigned to this service have a shell? I recall a weird problem where not having a shell for this service's user account caused a problem. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information!

----- Excess quoted text cut - see Original Post for more ----- Hey Dave, thanks for the reply. Yeah, the service was running. I did get the problem sorted out, though. I followed these instructions http://www.alagad.com/go/blog-entry/verity-nightmare, and reinstalled Verity. Unfortunately, I'm not sure which of the two fixed it, but I'm all set. Thanks, Jamie