Tim Parker commented on SOLR-9325:

further testing shows that the logs all appear to be going to the right places 
- I haven't tried this on Windows 7 yet, but I have seen several other 
(apparently unrelated) problems with 6.3 including '...possible analysis 
error...' when indexing PDF (as parsed by Tika), and some 
AlreadyClosedException entries - should I write these up separately? or are 
these just fallout from this being an interim build?

> solr.log written to {solrRoot}/server/logs instead of location specified by 
> -----------------------------------------------------------------------------------------
>                 Key: SOLR-9325
>                 URL: https://issues.apache.org/jira/browse/SOLR-9325
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: logging
>    Affects Versions: 5.5.2, 6.0.1
>         Environment: 64-bit CentOS 7 with latest patches, JVM
>            Reporter: Tim Parker
>            Assignee: Jan H√łydahl
>             Fix For: 6.3, master (7.0)
>         Attachments: SOLR-9325.patch, SOLR-9325.patch, SOLR-9325.patch
> (6.1 is probably also affected, but we've been blocked by SOLR-9231)
> solr.log should be written to the directory specified by the SOLR_LOGS_DIR 
> environment variable, but instead it's written to {solrRoot}/server/logs.
> This results in requiring that solr is installed on a writable device, which 
> leads to two problems:
> 1) solr installation can't live on a shared device (single copy shared by two 
> or more VMs)
> 2) solr installation is more difficult to lock down
> Solr should be able to run without error in this test scenario:
> burn the Solr directory tree onto a CD-ROM
> Mount this CD as /solr
> run Solr from there (with appropriate environment variables set, of course)

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