[
https://issues.apache.org/jira/browse/SOLR-7826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15546431#comment-15546431
]
Jan Høydahl commented on SOLR-7826:
-----------------------------------
I think I'll leave things as they are for now. Same-user policy for 7.0 sounds
ok. Perhaps see where the breadcrumbs effort in SOLR-9590 leads us, but that
will anyway not help for manual installs.
One idea could be to determine whether Solr has been started before or not,
i.e. by looking for a file that is always created by the Solr process, such as
$SOLR_LOGS_DIR/solr.log or $SOLR_HOME/<directory>/data/index, and require
*that* user. If Solr has not been started before, let the start command succeed
as any user, but test first that the user has write access to both SOLR_HOME
and SOLR_LOGS_DIR?
> Permission issues when creating cores with bin/solr as root user
> ----------------------------------------------------------------
>
> Key: SOLR-7826
> URL: https://issues.apache.org/jira/browse/SOLR-7826
> Project: Solr
> Issue Type: Improvement
> Reporter: Shawn Heisey
> Assignee: Jan Høydahl
> Priority: Minor
> Labels: newdev
> Fix For: 6.3, master (7.0)
>
> Attachments: SOLR-7826.patch, SOLR-7826.patch,
> SOLR-7826_sameuser.patch
>
>
> Ran into an interesting situation on IRC today.
> Solr has been installed as a service using the shell script
> install_solr_service.sh ... so it is running as an unprivileged user.
> User is running "bin/solr create" as root. This causes permission problems,
> because the script creates the core's instanceDir with root ownership, then
> when Solr is instructed to actually create the core, it cannot create the
> dataDir.
> Enhancement idea: When the install script is used, leave breadcrumbs
> somewhere so that the "create core" section of the main script can find it
> and su to the user specified during install.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
