I've tried this on a dev server and the installation of Solr 3 has been running for approximately 40 minutes now, is this not possible?

Comments

omega8cc’s picture

omega8cc commented
Status: Active » Postponed (maintainer needs more info)

Please follow guidelines and provide enough details.

realityloop’s picture

realityloop commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

removed tomcat manually and re-ran upgrade

omega8cc’s picture

omega8cc commented
Status: Closed (fixed) » Postponed (maintainer needs more info)

This is not really helpful answer. Barracuda should do this for you, automatically, and if you are experiencing problems, please share some details to help in debugging and not just close the issue without sharing anything.

Anonymous’s picture

Anonymous (not verified) commented

I also noticed that - although jetty - both 8 and 9 seemed to install fine during the upgrade to 2.0.7 stable, tomcat was still on the server and still running. My question is: is tomcat being used for anything other than solr on boa now? And if not, do you advise us to remove it completely, or just edit out its autostart in some config file somewhere?

omega8cc’s picture

omega8cc commented

BOA doesn't uninstall/remove Tomcat. It just moves existing Solr cores to Jetty 7 and stops/disables Tomcat, because otherwise Jetty couldn't start (it is expected to run on the same port 8080). And this happens automatically in all our tests and all servers we manage and has been upgraded so far, so I'm really curious to see some details/errors if displayed/logged etc, as we can't reproduce the problem.

omega8cc’s picture

omega8cc commented

Of course this happens only when you add the non-default option.

Anonymous’s picture

Anonymous (not verified) commented

Tomcat is only still running on the boa 2.0.7 server with percona on it, and I did add SR3 and SR4 . Furthermore, I never used solr or tomcat on that server because I was waiting for solr 3 or 4 before setting it up. SO on that server I had listed SLR as an extra since BOA 2.0.4, but never enabled any apache_solr modules or set up the solr server. Perhaps that is why tomcat is still running - there was no migration, and tomcat was previously installed with SLR in an upgrade. - This should explain the problem - but if you really want to see errors or logs, tell me which ones and I'll upload them.

I would still like to know if we should uninstall tomcat - or if BOA uses it for something else, or perhaps if BOA is not using it for anything else, just disabling it, and modifying some rc files (?) to keep it from restarting each time it is stopped manually?

I can confirm that there is no tomcat running on a fresh install of 2.0.7 using mariaDB which includes SR3 and SR4 - almost certainly because I never had added SLR to it in the first place.

omega8cc’s picture

omega8cc commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Tomcat will still run as-is if you just added new options using Jetty and didn't add the _TOMCAT_TO_JETTY=YES option on upgrade. This is by design, so you can still use Tomcat. Some people may use it for some reasons, so we don't force uninstall, unless specified. BOA doesn't use Tomcat for anything and it is safe to disable and remove it, if you prefer. Please read the docs for more information.