Re: install_solr_service.sh issues with SUSE SLES 12.1, 12.2
Thanks, sorry I missed the issue in JIRA. I think the second issue still stands and is unrelated - it's only related in the sense that it affects the same file. 2) only on SLES 12.2 (and Leap 42.2) and possibly future versions: related to the following change: https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12-SP2/#fate-320973 On a fresh install, the command "service solr start" will result in the message: solr is neither service nor target!? adding "systemctl daemon-reload" before starting the service fixes this issue, however, I'm not sure if this is the right approach. On 08/30/2017 03:44 PM, Susheel Kumar wrote: I had this opened https://issues.apache.org/jira/browse/SOLR-10932 earlier and discussion link http://lucene.472066.n3.nabble.com/install-solr-service-possible-bug-td4340502.html We shall put a fix for this as Shawn suggested. On Wed, Aug 30, 2017 at 9:02 AM, Adrian H <adib...@gmail.com> wrote:
install_solr_service.sh issues with SUSE SLES 12.1, 12.2
hi all I've installed Solr 6.6.0 (and older versions) on a couple of SUSE servers and ran into the following issues with the service installer script: 1) on both SLES 12.1 and 12.2: line 196: service --version &>/dev/null || print_error "Script requires the 'service' command" service --version exits with an exit code of 1 so the script stops there. There is no --version option in the SUSE packaged service command, so it's an error. changing this to: service --help resolves the issue as it exits with a 0. I can confirm that --help also exits with a 0 on my debian 9 system, but I don't know about the others. 2) only on SLES 12.2 (and Leap 42.2) and possibly future versions: related to the following change: https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12-SP2/#fate-320973 On a fresh install, the command "service solr start" will result in the message: solr is neither service nor target!? adding "systemctl daemon-reload" before starting the service fixes this issue, however, I'm not sure if this is the right approach. I'm new to this mailing list and project, so I don't know if these are issues which should be created in JIRA or first discussed here. cheers Adrian
