[
https://issues.apache.org/jira/browse/SOLR-6851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275643#comment-14275643
]
ASF subversion and git services commented on SOLR-6851:
-------------------------------------------------------
Commit 1651436 from [~thelabdude] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1651436 ]
SOLR-6851: Set the SOLR_VAR_DIR using the SOLR_SERVICE variable, thus
alleviating the need to specify the -d option when overrding the service name
with -s
> Scripts to help install and run Solr as a service on Linux
> ----------------------------------------------------------
>
> Key: SOLR-6851
> URL: https://issues.apache.org/jira/browse/SOLR-6851
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Assignee: Timothy Potter
> Fix For: 5.0, Trunk
>
> Attachments: SOLR-6851.patch, SOLR-6851.patch, SOLR-6851.patch
>
>
> noticed 2 problems with the oom_solr.sh script...
> 1) the script is only being run with the port of hte solr instance to
> terminate, so the log messages aren't getting writen to the correct directory
> -- if we change hte script to take a log dir/file as an argument, we can
> ensure the logs are written to the correct place
> 2) on my ubuntu linux machine (where /bin/sh is a symlink to "/bin/dash"),
> the console log is recording a script error when java runs oom_solr.sh...
> {noformat}
> #
> # java.lang.OutOfMemoryError: Java heap space
> # -XX:OnOutOfMemoryError="/home/hossman/lucene/5x_dev/solr/bin/oom_solr.sh
> 8983"
> # Executing /bin/sh -c "/home/hossman/lucene/5x_dev/solr/bin/oom_solr.sh
> 8983"...
> /home/hossman/lucene/5x_dev/solr/bin/oom_solr.sh: 20: [: 14305: unexpected
> operator
> Running OOM killer script for process 14305 for Solr on port 8983
> Killed process 14305
> {noformat}
> steps to reproduce: {{bin/solr -e techproducts -m 10m}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
