Version of Solr would help here. Solr 4+ will log where it find the collections if enabled (not sure about earlier version). The most likely problem is related to path. Perhaps you are hardcoding '\' separator somewhere on Windows and that messes up the path on Unix. Or you have different Solr version on dev/prod.
I would probably look for path being mentioned in the logs and, if that fails, using truss/strace (http://docstore.mik.ua/orelly/unix2.1/unixnut/c02_236.htm) and just check where solrconfig.xml is being looked for in reality. It is a hammer ('when you have a hammer....') for sure, but it is often a faster way to get ground-truth this way and then figure out what's causing it. Regards, Alex. Personal blog: http://blog.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Mon, Apr 29, 2013 at 10:15 AM, <jack.drysdale....@ustranscom.mil> wrote: > Hello, everyone. > > I have a really bizarre Solr issue that I hope someone can help me resolve. > > Production environment is *nix running CF 9.0.0, with both Verity and Solr > collections. > > Trying to list collections is breaking - one collection in particular is > breaking the CFCOLLECTION action="list": Error message states that the > solrconfig.xml file cannot be found. > > I unregistered this collection via CFAdmin, then went into the file system > and deleted the folders for this collection and restarted both Application > and Solr services. Ran the script, again, and still getting the same error > message for the collection that we just completely removed. It's NOT being > cached in the browser. > > This is working fine in development (Windows environment, CF9.0.1). > > Thoughts/suggestions greatly appreciated.
