kylin-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (KYLIN-3697) check port availability when starts kylin instance
Date Wed, 21 Nov 2018 00:21:00 GMT


ASF GitHub Bot commented on KYLIN-3697:

shaofengshi closed pull request #354: KYLIN-3697 minor, only start check-env

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/build/bin/ b/build/bin/
index b65cb958a5..b04707815c 100755
--- a/build/bin/
+++ b/build/bin/
@@ -27,7 +27,6 @@ if [ "$verbose" = true ]; then
-source ${dir}/
 mkdir -p ${KYLIN_HOME}/logs
 mkdir -p ${KYLIN_HOME}/ext
@@ -66,7 +65,9 @@ then
           quit "Kylin is running, stop it first"
+    source ${dir}/
     export tomcat_root


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:

> check port availability when starts kylin instance
> --------------------------------------------------
>                 Key: KYLIN-3697
>                 URL:
>             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 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
>   I can only find the error message in the kylin.out, which is not so user-friendly.
> > Caused by: Address already in use (Bind failed)
> 	at Method)
> 	at
> 	at
> 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

View raw message