[
https://issues.apache.org/jira/browse/SOLR-7635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14572738#comment-14572738
]
Shawn Heisey commented on SOLR-7635:
------------------------------------
This is not exactly related to this specific issue, but I'm wondering ... what
do we want to do in the Solr script if lsof is not installed on the machine?
> bin/solr -e cloud can fail on MacOS
> -----------------------------------
>
> Key: SOLR-7635
> URL: https://issues.apache.org/jira/browse/SOLR-7635
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
> Affects Versions: 5.2
> Environment: Unix
> Reporter: Upayavira
> Priority: Minor
> Attachments: SOLR-7635.patch, SOLR-7635.patch
>
>
> On MacOS:
> bin/solr -e cloud
> said:
> Please enter the port for node1 [8983]
> Oops! Looks like port 8983 is already being used by another process. Please
> choose a different port.
> Looking at the script, it uses:
> PORT_IN_USE=`lsof -Pni:$CLOUD_PORT`
> which gave the output:
> {{
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> Google 365 upayavira 130u IPv6 0xab1d227df2e5a7db 0t0 TCP
> [::1]:49889->[::1]:8983 (ESTABLISHED)
> java 10889 upayavira 118u IPv6 0xab1d227df2e73ddb 0t0 TCP *:8983
> (LISTEN)
> java 10889 upayavira 134u IPv6 0xab1d227df2e756db 0t0 TCP
> [::1]:8983->[::1]:49889 (ESTABLISHED)
> }}
> This was connections Google Chrome was attempting to make to Solr.
> Replacing the above line with this:
> PORT_IN_USE=`lsof -Pni:$CLOUD_PORT | grep LISTEN`
> resolved the issue. Very simple patch attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
