On the dev machine, it works either way. On the other two machines, it's not working, either way.
We can safely ignore the BitNami GUI, and focus on the URL I provided below. Our app needs to create them on the fly, so that's really the mechanism I am interested in resolving. I only mentioned the BitNami to help clarify that I didn't think it was a problem in our code, as the GUI on all three behaves exactly like our code; works on dev, not on the two QA machines. Make sense? How can I send a log entry, will this list accept an attachment? -----Original Message----- From: Joel Bernstein [mailto:joels...@gmail.com] Sent: January 8, 2014 15:00 To: solr-user@lucene.apache.org Subject: Re: Solr not creating core.properties file One quick clarification: "On our dev machine, this works as expected, it's just on the two other machines where we're having QA take a crack at it that it's not working." So: a) On the dev machine the core admin command is working. b) On the other two machines it's not working. On the two machines that it's not working, is it failing with the BitNami GUI and core admin command or just the BitNami GUI. Because if it's failing only with the BitNami GUI then we need to know what command the BitNami GUI is using. Does the log file capture the command being using by BitNami? Joel Joel Bernstein Search Engineer at Heliosearch On Wed, Jan 8, 2014 at 2:50 PM, Craig Longman <clong...@iconect.com> wrote: > > As mentioned, I'm using the BitNami installer, it has an admin GUI. > Creating it there results in not having a core.properties file created. > In our application, we issue this: > > dev-solr2/solr/admin/cores > ?action=CREATE > &loadOnStartup=true > &name=database_1_1 > &instanceDir=path/to/config/database_1_1 > &dataDir=/path/to/cores/database_1_1 > > On our dev machine, this works as expected, it's just on the two other > machines where we're having QA take a crack at it that it's not working. > All three have the same config, checked pretty thoroughly, although our > next step is for me to setup a fourth machine personally and see what > happens. > > -----Original Message----- > From: Joel Bernstein [mailto:joels...@gmail.com] > Sent: January 8, 2014 14:44 > To: solr-user@lucene.apache.org > Subject: Re: Solr not creating core.properties file > > Craig, > > Can you describe the steps you are using to create the core? > > Joel > > Joel Bernstein > Search Engineer at Heliosearch > > > On Wed, Jan 8, 2014 at 2:27 PM, Craig Longman <clong...@iconect.com> > wrote: > > > We're exploring using Solr as a search/faceting engine, and things > went > > quite well during the research phase. We've expanded it a bit, but > have > > run into something of a problem on the two latest machines we've > > installed Solr on: Solr is just quietly refusing to write out the > > core.properties file at all. I'm at a complete loss as to what's > going > > on. If I look in CorePropertiesLocator.java, in method > > writePropertiesFile(), it appears that it would log something if there > > was an IO error saving the properties file, but I get nothing in the > > logs indicating such. There is also nothing in the logs that > indicates > > there was anything especially wrong at all. The core is created, the > > solrconfig.xml file is found and read, the index directories are > created > > (a different directory to the config) and the core is loaded and can > be > > used just fine. It just seems to quietly skip the core.properties > > writing. Which kind of messes up the whole auto-discovery thing. > > > > > > > > Any ideas? Under what circumstances would that file not be written > out? > > It looks like only IOExceptions can be thrown, so I have to assume > that > > the writePropertiesFile() method isn't even being called, right? > > > > > > > > We're running Solr 4.6.0, installed via the BitNami install client. > > > > > > > > Any other information that could be helpful in figuring this one out? > > > > > > > > Thanks, > > > > > > > > Craig Longman > > > > > > > > This message and any attachments are intended only for the use of the > > addressee and may contain information that is privileged and > confidential. > > If the reader of the message is not the intended recipient or an > authorized > > representative of the intended recipient, you are hereby notified that > any > > dissemination of this communication is strictly prohibited. If you > have > > received this communication in error, notify the sender immediately by > > return email and delete the message and any attachments from your > system. > > > > >
