I am running Coldfusion 10 (10,0,9,284568) on Win7 64bit developer instance. Initially we had no need for SOLR, so we did not include it in the original ColdFusion install. However, we now have need, so I downloaded ColdFusion_10_Jetty_Solr_win.exe from adobe, and installed using default values, and received no errors. However, when I open CF Admin to add a collection, I receive the cannot create collection error.
What is the SOLR home directory supposed to be set to in ColdFusion Admin? I tried several values, (coldfusionjetty\solr, and coldfusionjetty\multicore\), and they all appear to work. But when I go to create a collection I always receive the cannot create error. I have uninstalled and reinstalled the ColdFusion 10 SOLR multiple times, but no improvement. Adobe has no documentation on this that I can find. Any ideas?
Edit:
--- nevermind, I was finally able to get it to work. For anyone else who wonders where the Coldfusion SOLR Home should be, I set the SOLR host to localhost and the SOLR home to C:/ColdFusionJetty/multicore/ using CF admin, saved, then created a collection and it worked. I swear I tried the multicore directory earlier, but perhaps not.
For anyone else who wonders where the Coldfusion SOLR Home should be, I set the SOLR host to localhost and the SOLR home to C:/ColdFusionJetty/multicore/ using CF admin, saved, then created a collection and it worked. I swear I tried the multicore directory earlier, but perhaps not.
References
Jetspeed Deployers Guide - Apache Tomcat Overview
Solr Tomcat
Apache Tomcat 7 (7.0.78) - Security Considerations
Solr Wiki: Why no WAR
Related
I have a problem with an old TYPO3 installation (TYPO3 site 7 LTS [7.6.9]).
The site is using Apache Solr as the search engine, but it's not working. When a user tries to search, the system shows a message telling that the search engine is not available now.
In the administration panel, if I go to the Search option, I see this message:
Unable to contact your Apache Solr server.
Hosts missing:http://localhost:8080/solr/core_es/
http://localhost:8080/solr/core_eu/
http://localhost:8080/solr/core_en/
Of course, I have checked that Solr is running and listening on the port 8080. The Solr server is on the same machine than TYPO3.
I found this link about the Apache Solr configuration, but I cannot find these administration pages. I would like to test with the machine's public IP. In fact, I changed all the records regarding Solr in the cf_tx_solr_configuration table, and cleared all the cache tables manually, with no effect.
I have a couple of questions here:
Is it possible to change the configuration of the Solr server in TYPO3? If so, how can I do that?
Is TYPO3 shipped with an out-of-the-box search feature? If so, how can I disable Apache Solr and use the default search engine?
Thanks so much in advance!
please consume appropriate documentation Version of installed Extension.
So I assume(see Version Matix) you are using EXT:Solr version 6.5, therefore you must use the documentation for EXT:Solr v. 6.5.
--
QA
Is it possible to change the configuration of the Solr server in TYPO3? If so, how can I do that?
Yes, it is. You can set it via TypoScript path "plugin.tx_solr.solr.scheme|host|port|..."
Is TYPO3 shipped with an out-of-the-box search feature? If so, how can I disable Apache Solr and use the default search engine?
Yes, TYPO3 has build in search feature. Its name is indexed_search.
PS: You know, there are much more modern versions of TYPO3 available? Please upgrade at least to the newer major release.
NOTE: I've tried everything in the comments below and everything else I can think of. At this point I have to assume there's a bug of some kind and that a restart will NOT bring SOLR up in cloud mode unless you roll your own init.d stuff.
==================================================
I have 3 SOLR nodes and 3 Zookeeper nodes.
The SOLR Nodes are SOLR 5.4 on Ubuntu 14 and were installed based on the instructions here:
https://cwiki.apache.org/confluence/display/solr/Taking+Solr+to+Production
If I issue this command to start or restart SOLR on the command line, everything looks fine in the SOLR Admin UI and all my nodes are green in the UI
sudo /opt/solr/bin/solr restart -c -z 192.168.56.5,192.168.56.6,192.168.56.7/solr5_4
However, even though I have a ZK_HOST entry in my solr.in.sh I cannot get the nodes to show up in the SOLR Admin console correctly if I try:
service solr restart
Or if I reboot the VM.
My ZK_HOST entry in solr.in.sh looks like this:
ZK_HOST="192.168.56.5,192.168.56.6,192.168.56.7/solr5_4"
I also tried it this way (no quotes, just in case) because that's how it looks on the Apache wiki page I was reading:
ZK_HOST=192.168.56.5,192.168.56.6,192.168.56.7/solr5_4
I always have to run the command line to get the SOLR instances to show up correctly in the Admin UI. It would be preferrable to have this "just happen" when rebooting the VM.
If I run service solr restart on any of them, they show as "down" in the Admin UI and the core I am using disappears from the Admin UI for the one IP address I'm looking at.
Why is this and what settings are required to get SOLR to start on boot into "Cloud Mode" with the correct Zookeeper settings?
Until a recent change, the docs for setting SOLR up for Prod had a slight misdirection. The bottom line here is that /etc/default/solr.in.sh was what controlled the SOLR configs on startup. NOT the one mentioned in the docs (which was somewhere else anyway /opt/solr/bin)
Once I added the ZKHOST setting in /etc/default/solr.in.sh and restarted the service (or rebooted the server) SOLR came up in "Cloud" mode every time.
Solr 4 stopped immediately on trying to add document and commit. I'm working on a Solr 4 with Tomcat 8 on Windows 7, and the Solr has only one core that I use. On trying to commit the document from SolrNet, however the Solr and Tomcat both goes down. I noticed few documents commited, but didn't find any error in Solr log.
Note that this is a new Tomcat & Solr installation.
On application side using SolrNet on adding document, I get following error:
System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.
Update
I have tried with uninstalling Tomcat 8 and installed Tomcat 7 with Solr4 but the issue is still the same.
Any help is highly appreciated on what could be wrong? What to check? Where to find errors has caused this?
Also let me know if you need more details.
Thanks
Tomcat 8 does not have a stable release yet and Solr has not been tested with it. There may be some incompatibilities. Please try with Tomcat 7 to rule out issues with Tomcat 8.
Moreover, the last release of SolrNet was made about 2 years ago - I am not sure if it will work well with the latest release of Solr. I think you should use SolrJ if possible. Otherwise, just post the Solr docs as XML.
Currently, I have developed a web application. In my web application, I used embedded solr server to make indexing. After that I deployed onto the Tomcat 6 on window xp. Everything is ok. Next, I have tried my web application to deploy on Amazon AWS. My platform is linux + mysql. When I deployed, I got the exception related with embedded solr.
[ WARN] 19:50:55 SolrCore - [] Solr index directory 'solrhome/./data/index' doesn't exist. Creating new index...
[ERROR] 19:50:55 CoreContainer - java.lang.RuntimeException: java.io.IOException: Cannot create directory: /usr/share/tomcat6/solrhome/./data/index
at org.apache.solr.core.SolrCore.initIndex(SolrCore.java:403)
at org.apache.solr.core.SolrCore.<init>(SolrCore.java:552)
at org.apache.solr.core.CoreContainer.create(CoreContainer.java:480)
So how to fix my problem. I am novie to linux.
My guess is that the user you are running Solr under does not have permission to access that directory.
Also, which version of Solr are you using? Looks like 3+. The latest version is 4, so it may make sense to try using that from the start. Probably a bit more troubleshooting to start, but a much better pay off that starting with legacy configuration.
I got solution. That is because of permission affair on Amazon Linux with ec2-user. So , I changed permission by following.
sudo chmod -R ugo+rw /usr/share/tomcat6
http://wiki.apache.org/solr/SolrOnAmazonEC2strong text
t should allow access to ports 22 and 8983 for the IP you're working from, with routing prefix /32 (e.g., 4.2.2.1/32). This will limit access to your current machine. If you want wider access to the instance available to collaborate with others, you can specify that, but make sure you only allow as much access as needed. A Solr instance should not be exposed to general Internet traffic. If you need help figuring out what your IP is, you can always use whatismyip.com. Please note that production security on AWS is a wide ranging topic and is beyond the scope of this tutorial.
I am new to Solr.
I have created two cores from the admin page, let's call them "books" and "libraries", and imported some data there. Everything works without a hitch until I restart the server. When I do so, one of these cores disappears, and the logging screen in the admin page contains:
SEVERE CoreContainer null:java.lang.NoClassDefFoundError: net/arnx/jsonic/JSONException
SEVERE SolrCore REFCOUNT ERROR: unreferenced org.apache.solr.core.SolrCore#454055ac (papers) has a reference count of 1
I was testing my query in the admin interface; when I refreshed it, the "libraries" core was gone, even though I could normally query it just a minute earlier. The contents of solr.xml are intact. Even if I restart Tomcat, it remains gone.
Additionally, I was trying to build a query similar to this: "Find books matching 'war peace' in libraries in Atlanta or New York". So given cores "books" and "libraries", I would issue "books" the following query (which might be wrong, if it is please correct me):
(title:(war peace) blurb:(war peace))
AND _query_:"{!join
fromIndex=libraries from=libraryid to=libraryid
v='city:(new york) city:(atlanta)'}"
When I do so, the query fails with "libraries" core disappears, with the above symptoms. If I re-add it, I can continue working (as long as I don't restart the server or issue another join query).
I am using Solr 4.0; if anyone has a clue what is happening, I would be very grateful. I could not find out anything about the meaning of the error message, so if anyone could suggest where to look for that, or how go about debugging this, it would be really great. I can't even find where the log file itself is located...
I would avoid the Debian package which may be misconfigured and quirky. And it contains (a very early build of?) solr 4.0, which itself may have lingering issues; being the first release in a new major version. The package maintainer may not have incorporated the latest and safest Solr release into his package.
A better way is to download Solr 4.1 yourself and set it up yourself with Tomcat or another servlet container.
In case you are looking to install SOLR 4.0 and configure, you can following the installation procedure from here
Update the solr config for the cores to be persistent.
In your solr.xml, update <solr> or <solr persistent="false"> to <solr persistent="true">