If you have installed v1.2/v1.3 and now you directly install v1.5.x, you should very carefully to check the metadata URI to make sure it points to right one (ensure the new instance, say v1.5.x will not use old one).
Thanks. Best Regards! --------------------- Luke Han On Fri, Jun 10, 2016 at 10:31 PM, Jie Tao <jie....@gameforge.com> wrote: > I find another error in localhost.log. This may be related. Is > kylin_metadata in Hbase created during deploying kylin.war? Is this the > real reson that the ip:7070/kylin gets stuck? > > > > Jun 10, 2016 4:17:11 PM org.apache.catalina.core.StandardContext > listenerStart > fatal: Exception sending context initialized event to listener instance of > class org.springframework.web.context.ContextLoaderListener > org.springframework.beans.factory.BeanCreationException: Error creating > bean with name 'cacheService': Invocation of init method failed; nested > exception is java.lang.IllegalArgumentException: Failed to find metadata > store by url: kylin_metadata@hbase > > Cheers, > > Jie > > > Am 10.06.2016 um 15:46 schrieb Jie Tao: > >> sorry! There do have problems in catalina.log: >> >> INFORMATION: Starting service Catalina >> ......... >> INFORMATION: Deploying web application archive >> /home/bi-operator/apache-kylin-1.5.2.1-bin/tomcat/webapps/kylin.war >> >> ......... >> Jun 10, 2016 2:46:30 PM org.apache.catalina.core.StandardContext >> startInternal >> >> fatal: Error listenerStart >> >> fatal: Context [/kylin] startup failed due to previous errors >> >> fatal: The web application [/kylin] appears to have started a thread >> named [localhost-startStop-1-SendThread(our-zookeeper:2181)] but has failed >> to stop it. This is very likely to create a memory leak. >> >> So: kylin is not correctly deployed. How to solve this problem? >> >> >> Cheers, >> >> Jie >> >> Am 10.06.2016 um 15:11 schrieb Jie Tao: >> >>> I tried on a cluster of apache BIGTOP installation with Hadoop 2.4.1, >>> hive 0.13.1 and HBase 0.98.5-hadoop2. Kylin is started and there is no >>> exception in either catalina.log or kylin.log. But: the URL >>> http://10.106.4.10:7070/kylin/ keeps connecting and after some time (I >>> guess it is timeout) it shows: >>> >>> Firefox can't establish a connection to the server at >>> my-kylin-server-ip:8080 >>> >>> As 8080 is the TOMCAT port number, so I guess that TOMCAT does not work >>> correctly. How can I further debug this issue? In catalina.log I only see >>> infos like: >>> >>> INFORMATION: Starting service Catalina >>> Jun 10, 2016 2:50:36 PM org.apache.catalina.core.StandardEngine >>> startInternal >>> INFORMATION: Starting Servlet Engine: Apache Tomcat/7.0.59 >>> Jun 10, 2016 2:50:36 PM org.apache.catalina.startup.HostConfig deployWAR >>> INFORMATION: Deploying web application archive >>> /home/bi-operator/apache-kylin-1.5.2.1-bin/tomcat/webapps/kylin.war >>> >>> By the way, Kylin 1.3 runs well with my environment. Maybe something >>> others with kylin 1.5 related to TOMCAT? >>> >>> Cheers, >>> >>> Jie >>> >>> Am 07.06.2016 um 08:40 schrieb Jie Tao: >>> >>>> Thanks for the reply. The same error is in kylin.log. I think it is >>>> version conflict. I will try on another Hadoop version and see if the same >>>> happens. >>>> >>>> Cheers, >>>> >>>> Jie >>>> >>>> Am 07.06.2016 um 02:39 schrieb Li Yang: >>>> >>>>> The log is not related. What's in the kylin.out? >>>>> >>>>> On Mon, May 30, 2016 at 10:09 PM, Jie Tao <jie....@gameforge.com> >>>>> wrote: >>>>> >>>>> after starting Kylin this URL (http://localhost:7070/kylin/) keeps >>>>>> connecting to local host but shows nothing. This happened with 1.5.0, >>>>>> 1.5.1 >>>>>> and 1.5.2. In catalina.log there is a warning: >>>>>> java.io.FileNotFoundException: >>>>>> /home/tao/hadoop-2.7.1/contrib/capacity-scheduler/*.jar not found. >>>>>> After >>>>>> the warning there is no further log information. >>>>>> >>>>>> But the same warning can be seen with version 1.2, where after the >>>>>> warning >>>>>> I see: >>>>>> INFORMATION: Deployment of web application archive >>>>>> /home/tao/apache-kylin-1.2-bin/tomcat/webapps/kylin.war has finished >>>>>> in >>>>>> 12,411 ms >>>>>> >>>>>> I earlier tested version 1.2 using the sample cube. Then I installed >>>>>> version 1.5 on the same hadoop. Hbase and Hive environment. This >>>>>> means that >>>>>> Hive and Hbase already contain data from testing v1.2. Can this be a >>>>>> problem? I have: hbase-0.98.17-hadoop2 and Hive 0.13.0, hadoop 2.7.1. >>>>>> >>>>>> The following is the detail in catalina.log: >>>>>> >>>>>> INFORMATION: Deploying web application archive >>>>>> /home/tao/Downloads/apache-kylin-1.5.2-bin/tomcat/webapps/kylin.war >>>>>> Mai 30, 2016 3:48:59 PM >>>>>> org.apache.tomcat.util.scan.StandardJarScanner scan >>>>>> WARNING: Failed to scan >>>>>> [file:/home/tao/hadoop-2.7.1/contrib/capacity-scheduler/*.jar] from >>>>>> classloader hierarchy >>>>>> java.io.FileNotFoundException: >>>>>> /home/tao/hadoop-2.7.1/contrib/capacity-scheduler/*.jar (file not >>>>>> found) >>>>>> at java.util.zip.ZipFile.open(Native Method) >>>>>> at java.util.zip.ZipFile.<init>(ZipFile.java:219) >>>>>> at java.util.zip.ZipFile.<init>(ZipFile.java:149) >>>>>> at java.util.jar.JarFile.<init>(JarFile.java:166) >>>>>> at java.util.jar.JarFile.<init>(JarFile.java:103) >>>>>> at sun.net.www.protocol.jar.URLJarFile.<init>(URLJarFile.java:93) >>>>>> at >>>>>> sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:69) >>>>>> at >>>>>> sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:99) >>>>>> at >>>>>> sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:122) >>>>>> >>>>>> at >>>>>> sun.net.www.protocol.jar.JarURLConnection.getJarFile(JarURLConnection.java:89) >>>>>> >>>>>> at >>>>>> org.apache.tomcat.util.scan.FileUrlJar.<init>(FileUrlJar.java:41) >>>>>> at >>>>>> org.apache.tomcat.util.scan.JarFactory.newInstance(JarFactory.java:34) >>>>>> >>>>>> at >>>>>> org.apache.catalina.startup.ContextConfig$FragmentJarScannerCallback.scan(ContextConfig.java:2647) >>>>>> >>>>>> at >>>>>> org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:258) >>>>>> >>>>>> at >>>>>> org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:220) >>>>>> >>>>>> at >>>>>> org.apache.catalina.startup.ContextConfig.processJarsForWebFragments(ContextConfig.java:1902) >>>>>> >>>>>> at >>>>>> org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1272) >>>>>> >>>>>> at >>>>>> org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:889) >>>>>> >>>>>> at >>>>>> org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:386) >>>>>> >>>>>> at >>>>>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) >>>>>> >>>>>> at >>>>>> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) >>>>>> >>>>>> at >>>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5412) >>>>>> >>>>>> at >>>>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) >>>>>> at >>>>>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) >>>>>> >>>>>> at >>>>>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) >>>>>> >>>>>> at >>>>>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649) >>>>>> at >>>>>> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1081) >>>>>> >>>>>> at >>>>>> org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1877) >>>>>> >>>>>> at >>>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) >>>>>> >>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >>>>>> at >>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>>>> >>>>>> at >>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>>>> >>>>>> at java.lang.Thread.run(Thread.java:745) >>>>>> >>>>>> >>>>>> >>>> >>> >> >
