[
https://issues.apache.org/jira/browse/SOLR-8296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006958#comment-15006958
]
Shawn Heisey commented on SOLR-8296:
------------------------------------
When I asked about this on the IRC channel, Hoss recommended that I open this
issue and tag [~thelabdude].
I tried renaming the init script mentioned in the error message, and then it
complained that the symlink in /opt already exists.
{code}
ERROR: /opt/solr5 already exists! Please move this directory / link or choose a
different service name using the -s option.
{code}
I renamed that symlink and then it installed. This means I have a workaround,
but novice users may not find their way through the problems.
My solr.in.sh was replaced, so I've got problems I need to correct, like the
heap size.
> Cannot find instructions for upgrading from one 5.x release to another
> ----------------------------------------------------------------------
>
> Key: SOLR-8296
> URL: https://issues.apache.org/jira/browse/SOLR-8296
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
> Affects Versions: 5.3.1
> Reporter: Shawn Heisey
>
> I'm trying to upgrade a Solr install on Linux from 5.2.1. The current
> install was installed with the install_solr_service shell script.
> This command doesn't work:
> {code}
> ./install_solr_service.sh
> /index/src/lucene_solr_5_3/solr/package/solr-5.3.2-SNAPSHOT.tgz -d
> /index/solr5 -s solr5 -p 8982
> {code}
> I get this message:
> {code}
> ERROR: /etc/init.d/solr5 already exists! Perhaps Solr is already setup as a
> service on this host?
> {code}
> What I was hoping for was another directory in /opt, the symlink /opt/solr5
> changing to point at the new directory, and a new init script, with the
> installer noticing an existing solr.in.sh and other files in /index/solr5,
> and not touching them.
> When I installed 5.2.1, I used the same command, with the older install
> script and the 5.2.1 tarball.
> There is an "Upgrading Solr" section in the reference guide, but it just
> talks about differences that might require config changes, not an actual
> procedure.
> I do not know whether we need a separate upgrade script or an upgrade option
> for the current script.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
