[KYLIN-3697] check port availability when starts kylin instance

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: v2.5.1
• Fix Version/s: v2.6.0
• Assignee: May Zhou
• Reporter: May Zhou
• Created: 20/Nov/18 08:43
• Updated: 12/Jan/19 06:41
• Resolved: 14/Dec/18 09:34

Description

As I ran the script and it turned out with no error message, and I ran the kylin.sh start script, the console output indicated that a kylin instance had successfully started, but when I visit the <host>:<port>/kylin, I found another service was running rather than kylin.

I can only find the error message in the kylin.out, which is not so user-friendly.
> Caused by: java.net.BindException: Address already in use (Bind failed)
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
at java.net.ServerSocket.bind(ServerSocket.java:375)

I am wondering why check-env does not check the availability of port, and the error message could be threw out more user-friendly.

Issue Links

• links to: GitHub Pull Request #353
• links to: GitHub Pull Request #354