kylin-issues mailing list archives

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

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

ASF GitHub Bot commented on KYLIN-3697:
---------------------------------------

asfgit commented on issue #353: KYLIN-3697 Check port availability when starts kylin instance
URL: https://github.com/apache/kylin/pull/353#issuecomment-440273296
 
 
   Can one of the admins verify this patch?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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