I installed solr using the Bitnami installation in windows. When i ping the server using solarium.
If use var_dump($result->getResponse()); then everything works fine but if i use var_dump($result->getdata()); I get a error saying JSON could not be encoded.
Similarly when i try to index data into the solr server i get this error.
Fatal error: Uncaught exception 'Solarium\Exception\HttpException' with message 'Solr HTTP error: OK (405) Error 405 HTTP method POST is not supported by this URL<br> HTTP ERROR 405<br> Problem accessing /solr/admin.html. Reason: <br> HTTP method POST is not supported by this URL<br> Powered by Jetty<br> in C:\xampp\htdocs\trial\search\vendor\solarium\solarium\library\Solarium\Core\Query\Result\Result.php on line 104</p> <p>What can be the possible issue?</p>
Bitnami developer here
It seems to be an issue related to Solarium, and not with Bitnami Solr. You can see the issue here:
https://github.com/solariumphp/solarium/issues/101
You could ask there.
I hope it helps
Related
I've installed Solr on my Ubuntu to this path
/opt/solr/solr-4.10.2
After installing I started Solr:
sudo bin/solr start from /opt/solr/solr-4.10.2 directory
As I can understand it started successfully
Waiting to see Solr listening on port 8983 [/]
Started Solr server on port 8983 (pid=8385). Happy searching!
But when I try to get to admin page
http://localhost:8983/solr
I got 404 error:
HTTP ERROR: 404
Problem accessing /solr. Reason:
Not Found
Powered by Jetty://
Do you have any suggestion what's going wrong and where to look in order to fix this problem?
Since this error can be caused by a lot of things, you need to access the log file and debug the execution.
First of all, open your Node log file, located in /opt/solr/solr-4.10.2/node1/log and look for something weird (Shift+F for Errors).
Generally, this error occurs when you have a mismatch between the Solr required Java JDK and your current Java JDK.
When I had this problem, I found in the log file the following error message java.lang.UnsupportedClassVersionError: org/apache/solr/servlet/SolrDispatchFilter : Unsupported major.minor version 51.0 and realized the problem was the java version.
To solve this, try to change the current JDK, using the command sudo update-alternatives --config javac.
If the error still occurs, try to uninstall all unused JDK's, because Solr is getting the wrong path.
The final solution to this issue is to open the file /opt/solr/solr-4.10.2/solar.in.sh and edit the SOLR_JAVA_HOME, writing the right JDK path (e.g /usr/lib/jvm/java-1.7.0)
Disclosure: the secret is look in the log file and figure out what is causing the issue.
Cheers.
try:
http://localhost:8983/solr/index.html
[solr's web.xml]
<servlet>
<servlet-name>LoadAdminUI</servlet-name>
<servlet-class>org.apache.solr.servlet.LoadAdminUiServlet</servlet-class>
Google compute engine console return 399 error code already asks my question but the solution is not as suggested there. Since the URL is little old starting a new thread.
I am trying to do a wget using:
wget https://console.developers.google.com/m/cloudstorage/b/m-lab/o/ndt/2012/05/23/20120523T000000Z-mlab1-ams01-ndt-0000.tgz
I see the error:
Resolving console.developers.google.com (console.developers.google.com)... 216.239.32.27
Connecting to console.developers.google.com (console.developers.google.com)|216.239.32.27|:443... connected.
HTTP request sent, awaiting response... 399 Internal Server Error
2014-08-26 20:02:18 ERROR 399: Internal Server Error.
I am new to Linux commands so wanted to know if am missing something obvious.
The address works when I use Chrome downloader but fails with wget with me as well
I have never seen this behaviour before
You can also use cURL to download files, I used the -v switch and got a dns error(no idea why)
curl -v http://console.developers.googlO.com/m/cloudstorage/b/m-lab/o/ndt/2012/05/23/20120523T000000Z-mlab1-ams01-ndt-0000.tgz
We cannot download with traditional tools we have to use gsutil utility provided by google, using which automation is possible.
You need to use the following URI pattern:
http://storage.googleapis.com/<bucket>/<object>
In this case, you can download that file using the command:
wget http://storage.googleapis.com/m-lab/ndt/2012/05/23/20120523T000000Z-mlab1-ams01-ndt-0000.tgz
I am getting an error when I uploaded the files online. Something is suddenly up with the debugkit.
Parse error: syntax error, unexpected T_FUNCTION in
/home3/beauface/public_html/cosmeticsurgeryph/inventory/app/Plugin/DebugKit/Controller/Component/ToolbarComponent.php
on line 179
Everything is working smoothly when I run it on localhost.
Please enlighten me :(
Change your PHP Version to 5.3 or greater.
Because ToolbarComponent.php uses Anonymous Functions which supports only from 5.3+
I have a problem using SOLR when add document via GET method :
http://localhost:8983/solr/update?stream.body=%3Cadd%3E%3Cdoc%3E%3Cfield%20name=%22office%22%3EBridgewater%3C/field%3E%3Cfield%20name=%22skills%22%3EPerl%3C/field%3E%3Cfield%20name=%22skills%22%3EJava%3C/field%3E%3C/doc%3E%3C/add%3E
The error I got is
HTTP ERROR 400
Problem accessing /solr/update. Reason:
ERROR: [doc=null] unknown field 'office'
Is there any prerequisite that I'd missed ?
Looks like in the schema.xml you don't have the definition for the office field. If you have it, maybe you're using the wrong case to refer to it?
I am getting this error on an existing server. No configuration change. Suddenly, it happened. The log shows nothing, except something similar to the following:
10.10.10.11 - - [28/Oct/2011:01:01:08 +0800] "POST /notexist HTTP/1.1" 500 50 "-" "PECL::HTTP/1.7.1 (PHP/5.3.8)"
Until now I figured out that it is occurring only while using HTTP POST, it does not seem to be related to any CGI or PHP script.
I've recompiled Apache but the problem still exists. I wrote a script to visit a none exist URI of the server by using GET and POST. While requesting a GET, apache response 404, but for a POST, its response is a 500 error immediately.
Can anyone let me know what can I do?
I am using FreeBSD and the Apache is compiled by using event MPM.
Thanks in advance for any help.
PS. I've found it is related to subversion 1.7.1, While I reinstalled subversion 1.6.17 port, Apache seems to be working again. I am sorry to post this question here, maybe I should report this problem to FreeBSD subversion port administrator. It's weird because it doesn't happen when I upgrade to subversion 1.7.1, and it happened when there is no configuration change.
See http://svn.haxx.se/users/archive-2011-10/0457.shtml. It is a confirmed bug in Subversion 1.7.0 and 1.7.1. It's fixed in Subversion trunk with r1187695 which is proposed to be included in a following 1.7.x-release (see http://svn.apache.org/repos/asf/subversion/branches/1.7.x/STATUS).