May Zhou created KYLIN-3697: ------------------------------- Summary: check port availability when starts kylin instance Key: KYLIN-3697 URL: https://issues.apache.org/jira/browse/KYLIN-3697 Project: Kylin Issue Type: Bug Affects Versions: v2.5.1 Reporter: May Zhou
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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)