Jan Høydahl commented on SOLR-7826:

Thanks for the discussion and the contributions. Binoy/Shawn, I hope you don't 
feel bad that I did not use your approach/patch. I thought it was a bit 
overkill. Since the installer script by default creates a "solr" user for 
starting solr, it would be very uncommon for Solr to be run as root, and 
absolutely not something we would recommend. So now we always warn.

The question is if we should discourage and warn about *starting* solr as root 
as well, since this is not recommended?

> Permission issues when creating cores with bin/solr
> ---------------------------------------------------
>                 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
> 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

To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to