eBay / griffin

Model driven data quality service
https://ebay.github.io/griffin/
Other
240 stars 165 forks source link

Issue, unable to connect to the web UI #49

Open jmlero opened 6 years ago

jmlero commented 6 years ago

Hi,

I followed the guide to deploy the docker images. I have both (griffin and es running). Then I enter the griffin container in interactive mode and I execute

java -jar service/service.jar

But I obtain the follow:

*


APPLICATION FAILED TO START


Description:

The Tomcat connector configured to listen on port 8080 failed to start. The port may already be in use or the connector may be misconfigured.

So, I change the port as follow:

java -jar service/service.jar --server.port=8181

Then I obtain the follow:

2017-11-10 16:12:18.535  INFO 4845 --- [           main] oConfiguration$WelcomePageHandlerMapping : Adding welcome page: class path resource [public/index.html]
2017-11-10 16:12:19.013  INFO 4845 --- [           main] o.s.j.e.a.AnnotationMBeanExporter        : Registering beans for JMX exposure on startup
2017-11-10 16:12:19.026  INFO 4845 --- [           main] o.s.c.support.DefaultLifecycleProcessor  : Starting beans in phase 2147483647
2017-11-10 16:12:19.026  INFO 4845 --- [           main] o.s.s.quartz.SchedulerFactoryBean        : Starting Quartz Scheduler now
2017-11-10 16:12:19.076  INFO 4845 --- [           main] org.quartz.core.QuartzScheduler          : Scheduler schedulerFactoryBean_$_griffin1510330337340 started.
2017-11-10 16:12:19.087  INFO 4845 --- [           main] s.a.ScheduledAnnotationBeanPostProcessor : No TaskScheduler/ScheduledExecutorService bean found for scheduled processing
2017-11-10 16:12:19.147  INFO 4845 --- [pool-3-thread-1] o.a.griffin.core.common.CacheEvictor     : Evict hive cache
2017-11-10 16:12:19.165  INFO 4845 --- [           main] s.b.c.e.t.TomcatEmbeddedServletContainer : Tomcat started on port(s): 8181 (http)
2017-11-10 16:12:19.171  INFO 4845 --- [           main] o.a.griffin.core.GriffinWebApplication   : Started GriffinWebApplication in 8.062 seconds (JVM running for 8.683)
2017-11-10 16:12:19.261  INFO 4845 --- [pool-3-thread-1] o.a.griffin.core.common.CacheEvictor     : After evict hive cache,automatically refresh hive tables cache.
Hibernate: select distinct jobinstanc0_.group_name as col_0_0_, jobinstanc0_.job_name as col_1_0_ from job_instance jobinstanc0_
Hibernate: select distinct jobinstanc0_.group_name as col_0_0_, jobinstanc0_.job_name as col_1_0_ from job_instance jobinstanc0_

and I cannot access to the :8181 address.

bhlx3lyx7 commented 6 years ago

Hi @jmlero , I guess you're using the docker image following this doc, if not, we suggest you try this one, it's the latest version. Actually you don’t need to execute service.jar manually, our griffin docker image will execute it when start up, and that’s why port 8080 already used. The docker-compose.yml configured the port mapping 38080:8080, which means you can access :38080 as :8080. We didn’t export the container’s port 8181, that’s why you can not access it outside of the container. Btw, the docker images (griffin and es) needs plenty of system resources, we recommend more than 16GB memory environment. And it needs about two minutes to start the service.jar, so you can only connect to the web UI after about two minutes. This may help you about it. We've transferred this repo to incubator-griffin, you can comment there if any issues, thanks.

jmlero commented 6 years ago

Thanks.

I followed that doc. I have the images running (after docker-compose -f docker-compose-batch.yml up -d).

What I want is to try the web interface, if the docker images are running, I should be able to open the web interface with:

Ip_address:8080 , is that right?

The machines have enough resources (more than 32 GB) and I tried 2 different machines (with Ubuntu and with centos).

Checking the service.log, I see the following:

Hibernate: select distinct jobinstanc0_.group_name as col_00, jobinstanc0_.job_name as col_10 from jobinstance jobinstanc0 Hibernate: select distinct jobinstanc0_.group_name as col_00, jobinstanc0_.job_name as col_10 from jobinstance jobinstanc0

Any other idea?

PS: At the https://github.com/apache/incubator-griffin repository, there is not an option for issues. Should I comment there as a pull request? Thanks

bhlx3lyx7 commented 6 years ago

When the docker container starts up, the griffin service starts up, you can also visit the UI page. But the service runs in docker container, you can not access it remotely, that's why we set a mapping port 38080:8080 to let you can visit :38080 to access the UI page. For example, your docker host ip address is 123.123.123.123, then you can visit 123.123.123.123:38080 from any remote machine for griffin UI page. The first time you visit UI, you can login by user name "user" and password "test". Btw, the docker container starts up not so fast, after about 2 minutes, you can access the UI page. About the issue comments, I've found that repo doesn't have an option for issues, we'll check about it. Before that, you can also comment here, or create a ticket in griffin jira, or send email to griffin dev list, we recommend the latter options, thanks.

WangYongNingDA commented 6 years ago

if the port 8080 is used by other service,how to change to other port?

bhlx3lyx7 commented 6 years ago

You can change another port like normal spring boot application.