lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SOLR-10055) Manual bin/solr start causes crash due to resolving wrong
Date Wed, 22 Feb 2017 22:44:44 GMT


ASF subversion and git services commented on SOLR-10055:

Commit 1e206d820ab0a3c080562e056970c77ef5c99f04 in lucene-solr's branch refs/heads/master
from [~janhoy]
[;h=1e206d8 ]

SOLR-10055: Linux installer now renames existing bin/* as bin/*.orig to avoid
wrong resolving.

> Manual bin/solr start causes crash due to resolving wrong
> --------------------------------------------------------------------
>                 Key: SOLR-10055
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: scripts and tools
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>             Fix For: 6.5, master (7.0)
>         Attachments: SOLR-10055.patch
> The install script installs {{}} in {{/etc/defaults/}}. However, if the user
manually runs {{solr start}}, the script will use the {{}} file from {{bin/}} since
that is first in the search path. And it will fail since {{/opt/solr}} is write protected.
But if user starts with {{service solr start}} then the file from installation is used and
all is fine.
> Since the default {{/opt/solr/server/solr}} is not writable by solr user, this creates
a bad user experience and classifies as a bug.
> My proposal is that the installer renames {{bin/ -> bin/}}
and the same with {{}}, so that the resolution logic will end up finding the one
from the install. User can still override this by creating a {{$HOME/}}.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message