I'm running Solr 4.2 and would like to try out LucidWorks Banana product. However, when I navigate to the banana directory on my Solr server, I receive a 404 error.
I'm following the instructions from their github site here, basically dropping the banana src directory into the my SOLR_HOME\solr-webapp\webapp directory.
I've tried modifying the src\config.js and src\app\dashboards\default.json files as suggested by the readme file to change the localhost URL to the actual server name or the IP address. Both attempts still resulted in the 404 error.
Has anyone had luck in getting banana working with Solr 4.2? Is it not supported on this version of Solr? Hopefully I'm missing something really simple.
Thanks!
At LucidWorks, we have only tested Banana on Solr 4.4 and above. So, I am not sure whether all the functionality will work with Solr 4.2. However, I do know a couple of users on Solr 4.3 (who might have made some small code changes).
That said, the webapp is just javascript/html and should at least come up (maybe with errors on the dashboard, but not a 404), even without modifying config.js/default.json.
Just to confirm your process (from https://github.com/LucidWorks/banana/blob/release/QUICKSTART):
Copy Banana folder to $SOLR_HOME/example/solr-webapp/webapp/
Browse to http://localhost:8983/solr/banana/src/index.html#/dashboard
If you dropped the src folder (and not the banana folder), then you will need to
browse to http://solrserver.yourdomain.com:8983/solr/src/index.html#/dashboard
I figured this out thanks to Ravi's suggestion that made me re-examine my configuration.
Turns out my web app was actually running from C:\Windows\solr-webapp, and not $SOLR_HOME\solr-webapp\webapp. I missed that my CWD was set to C:\Windows even though everything else was pointing to $SOLR_HOME directories.
Once I dropped the Banana folder into C:\Windows\solr-webapp\webapp, I was able to bring up the dashboard. Now I have other errors, but that's a different set of issues.
Hope this helps someone. TL;DR - make sure your CWD is consistent with the destination of banana.
Related
I am trying to install piwik on my machine using XAMPP as it requires PHP, apache and mysql. When i installed XAMPP and launched apache, it worked fine but when i am trying to access MySql admin through XAMPP or access sample php page (copied on xampp/htdocs folder), apache is getting redirected to IIS which is then not able to view page, showing 404.3 error (its looking for file in wwwroot, which is also not working after pasting in wwwroot).
My objective is to make piwik up and running on my machine. Another option is Unix server which is very new to me (i have been working in Windows ). I know one should have a web server loaded with MySql and PHP to run piwik (which is hardly half an hour job once we have all these) but coz different resource available, i am struggling to get this thing done.
Any help is highly appreciated.
After two days of R&D, i figured it out (well, sort of). So for anybody who is new in piwik and in linux/apache/php/mysql, here is what i did to achieve the objective. For those of you who are familiar with all these or few of these, you might have a better way or answer and i would really request you to improve this answer but this is to help someone who is new and does not know all things at once.
Here is what i did
--get apache
--get php (one of the requirement for piwik)
--get sql (again requirement)
--all should be running (get wamp (its carrying all three of the above)), make sure apache is running on port 80.
--install mysql but make sure only wamp's sql is running
--set passowrd for root in wamp->mysql-->mysqlConsole-->set password for 'root'#'localhost'=password('yourPasswordHere');
--Paste piwik folder in www directory
--open localhost through wamp,login in adminer and phpmyadmin (bottom right)
--run http://localhost:8080/piwik-->u will see directory listing, click on folder piwik. You should be able to see welcome screen for piwik installation
--make sure we have php 7 as selected version in wamp( for php, wamp was carrying two version so we can choose) to avoid error in system check step of installation
--Follow the steps which are very straight forward.
This is something which worked out for me. Actual answer might be simpler or better. Hope it will help someone who is probably banging his/her head around and hitting some walls without getting something concrete.
Happy to help!!!
I have an existing Solr instance (4.9) up and running with several cores. I've been trying to set up Kibana for the majority of the day and I can't figure out how to incorporate it with my instance of Solr. I'm running locally on Windows 7 for dev purposes but the production is Linux. I've read through here and here a few times and I'm not picking up on how to get this done. The banana project seemed like the easiest choice but adding it to the banana/ directory did nothing. I started up LucidWorks but wasn't able to figure out how to get my existing cores in here. I have about 1.5TB of data in all of my cores (9 of them) so re-indexing is not an option.
Can someone provide me with resources or tutorials on how to incorporate Kibana with an existing Solr instance or a tutorial on how this is done?
If banana can fulfill your requirements, it is still the easiest choice. I recently set up banana for one of my Solr 5 cores (even though it was released for a 4.x series as far as I can tell), and also had the initial problem that "nothing happened".
Get it from https://github.com/LucidWorks/banana/ and then follow the instructions in the QUICKSTART file:
Copy Banana folder to $SOLR_HOME/example/solr-webapp/webapp/
Browse to http://localhost:8983/solr/banana/src/index.html#/dashboard
Perform the copy so that you will have a banana folder in webapp/, do not copy the contents of the banana folder directly in webapp/
Further information on the banana dashboard configuration and its options that I found useful are here: https://docs.lucidworks.com/display/SiLK/Dashboard+Configuration
I had a Drupal website in drupal 6.x When i wanted to upgrade it to 7.x, the custom theme i was using was absolutely outdated, so i imported my Zen subtheme from another website. For doing that, i just copied the folders "zen" and "mytheme" from the other installation to this one. Then i selected "mytheme" as the current theme and changed some little things to adapt it.
The fact is now i'm experiencing the following problems:
I can't auto-update nothing. It downloads the files but then it stacks (and leaves the site in Maintenance Mode).
I can't run update.php. I can go on until i reach the "Run updates" step, which shows a blank screen. This is the main issue, i think, as it evidences -in my oppinion- a problem of communication between the site and the database.
In the Webform module i can't select "File" as a Field Type. This one is not that important, but it may be relevant for someone who knows more than me.
Edit:
Recently i migrated from a Shared to a VPS server. When i migrated, the subdomain in which i was experiencing the issue threw an incompatibility related to the lenght of the password of the database. I changed the password and it started to work again. This may help somebody for helping me. Thanks!
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">
I'm trying to port a CakePHP application from WAMP (development machine) to LAMP (production server). In the WAMP instance submitting a search works. In the LAMP environment, search returns HTTP 500 error. Tomcat6 works and so does the :8080/solr/admin page. The CakePHP webapp works other than search.
Production Environment:
- Ubuntu 10.04
- Apache 2.2.14
- Tomcat6
- Solr 3.4.0
- CakePHP 1.3 (with solr-php-client)
- MySql 5.1.41
Observation: for the same search, the query strings are slightly different between the two environments. The LAMP version seems to be truncated, but I don't know how the value is derived so I can't be sure if the difference is significant.
LAMP (500 error): fields=9546e7be6d1d17fbd2e82f0d49a296b91853ddf0%253A
WAMP (results) : fields=9546e7be6d1d17fbd2e82f0d49a296b91853ddf0%253An%253A0%253A%257B%257D
Are there logs that might help troubleshoot the 500 error? Are there tests I can run directly through solr/admin that might shed light on the issue?
Problem solved. #aitchnyu: Thank you for your time and suggestions.
This turned out to be a CakePHP issue. The code to reference the php-solr-client classes works differently in WAMP and LAMP. In WAMP, code works when capitalizing file/folders properly. In LAMP, the reference must use all lower case with an added parameter containing properly capitalized file/folder names.
Here's where I found the answer:
http://cakebaker.42dh.com/2008/03/26/loading-vendor-files/
The different URLs in LAMP/WAMP appear to be insignificant.