kylin-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "May Zhou (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KYLIN-3697) check port availability when starts kylin instance
Date Tue, 20 Nov 2018 08:58:00 GMT

    [ https://issues.apache.org/jira/browse/KYLIN-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16692872#comment-16692872
] 

May Zhou commented on KYLIN-3697:
---------------------------------

As this issue is not that urgent, I would like to contribute a patch myself :)

> 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
>            Priority: Minor
>
> 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)

Mime
View raw message