[jira] [Commented] (HAWQ-1561) build faild on centos 6.8 bzip2
[
https://issues.apache.org/jira/browse/HAWQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292202#comment-16292202
]
xinzhang commented on HAWQ-1561:
I still could not build HAWQ. Here is my env.
I install boost /usr
Could u give me any suggests more? [~rlei]
---
{code:java}
[root@dw-dev205 boost_1_65_1]# find / -name "*bzip2*"
/opt/incubator-hawq/licenses/LICENSE-bzip2.txt
/opt/dependences/boost/boost_1_65_1/tools/build/src/tools/bzip2.jam
/opt/dependences/boost/boost_1_65_1/tools/build/test/bzip2.py
/opt/dependences/boost/boost_1_65_1/bin.v2/libs/iostreams/build/gcc-4.8.2/release/threading-multi/bzip2.o
/opt/dependences/boost/boost_1_65_1/bin.v2/libs/iostreams/build/gcc-4.8.2/release/link-static/threading-multi/bzip2.o
/opt/dependences/boost/boost_1_65_1/libs/iostreams/doc/classes/bzip2.html
/opt/dependences/boost/boost_1_65_1/libs/iostreams/src/bzip2.cpp
/opt/dependences/boost/boost_1_65_1/libs/iostreams/test/bzip2_test.cpp
/opt/dependences/boost/boost_1_65_1/boost/iostreams/filter/bzip2.hpp
/opt/dependences/boost/boost_1_65_1/boost/iostreams/detail/config/bzip2.hpp
/root/anaconda2/pkgs/pytables-3.3.0-np111py27_0/lib/python2.7/site-packages/tables/_comp_bzip2.so
/root/anaconda2/pkgs/freetype-2.5.5-2/include/freetype2/ftbzip2.h
/root/anaconda2/include/freetype2/ftbzip2.h
/root/anaconda2/lib/python2.7/site-packages/tables/_comp_bzip2.so
/usr/share/doc/bzip2-1.0.5
/usr/share/doc/bzip2-devel-1.0.5
/usr/share/man/man1/bzip2recover.1.gz
/usr/share/man/man1/bzip2.1.gz
/usr/local/include/boost/iostreams/filter/bzip2.hpp
/usr/local/include/boost/iostreams/detail/config/bzip2.hpp
/usr/include/boost/iostreams/filter/bzip2.hpp
/usr/include/boost/iostreams/detail/config/bzip2.hpp
/usr/src/kernels/2.6.32-696.16.1.el6.x86_64/include/config/have/kernel/bzip2.h
/usr/src/kernels/2.6.32-696.16.1.el6.x86_64/include/config/decompress/bzip2.h
/usr/src/kernels/2.6.32-696.16.1.el6.x86_64/include/config/rd/bzip2.h
/usr/bin/bzip2
/usr/bin/bzip2recover
/var/lib/yum/yumdb/b/39a5b544870d092858a6eb3fd140ef629e3f6b59-bzip2-libs-1.0.5-7.el6_0-x86_64
/var/lib/yum/yumdb/b/e2ff0b5e4192d403d73e0e26da3e5435797f78e4-bzip2-devel-1.0.5-7.el6_0-x86_64
/var/lib/yum/yumdb/b/c7e02a56f0eec33fa574c6edd460d0576ebe6f9a-bzip2-1.0.5-7.el6_0-x86_64
[root@dw-dev205 boost_1_65_1]# yum list installed |grep bzip2
bzip2.x86_64 1.0.5-7.el6_0
@anaconda-CentOS-201605220104.x86_64/6.8
bzip2-devel.x86_641.0.5-7.el6_0@base
bzip2-libs.x86_64 1.0.5-7.el6_0
@anaconda-CentOS-201605220104.x86_64/6.8
{code}
--
{code:java}
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by HAWQ configure 8.2.15, which was
generated by GNU Autoconf 2.69. Invocation command line was
$ ./configure --prefix=/opt/hawq/ --with-python
## - ##
## Platform. ##
## - ##
hostname = dw-dev205
uname -m = x86_64
uname -r = 2.6.32-642.el6.x86_64
uname -s = Linux
uname -v = #1 SMP Tue May 10 17:27:01 UTC 2016
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = x86_64
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /root/anaconda2/bin
PATH: /opt/rh/devtoolset-2/root/usr//bin
PATH: /opt/maven/maven-bin/bin
PATH: /opt/netdata/netdata-bin/netdata/usr/sbin
PATH: /opt/zookeeper/zookeeper-bin/bin
PATH: /opt/redis/redis-bin/src
PATH: /opt/elasticsearch/elasticsearch-bin/bin
PATH: /usr/java/jdk1.8.0_66/bin
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /sbin
PATH: /bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /root/bin
## --- ##
## Core tests. ##
## --- ##
configure:2934: checking build system type
configure:2948: result: x86_64-unknown-linux-gnu
configure:2968: checking host system type
configure:2981: result: x86_64-unknown-linux-gnu
configure:3003: checking which template to use
configure:3086: result: linux
configure:3214: checking whether to build with 64-bit integer date/time support
configure:3244: result: yes
configure:3251: checking whether NLS is wanted
configure:3284: result: no
configure:3292: checking for default port number
configure:3318: result: 5432
configure:3807: checking for gcc
configure:3823: found /opt/rh/devtoolset-2/root/usr//bin/gcc
configure:3834: result: gcc
configure:3865: checking for C compiler version
configure:3874: gcc --version >&5
gcc (GCC) 4.8.2 20140120 (Red Hat 4.8.2-15)
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
[jira] [Closed] (HAWQ-1569) log4j log can not open level debug
[
https://issues.apache.org/jira/browse/HAWQ-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xinzhang closed HAWQ-1569.
--
Resolution: Won't Fix
Fix Version/s: 2.2.0.0-incubating
Ignore here.
> log4j log can not open level debug
> ---
>
> Key: HAWQ-1569
> URL: https://issues.apache.org/jira/browse/HAWQ-1569
> Project: Apache HAWQ
> Issue Type: Bug
> Components: PXF
>Affects Versions: 2.2.0.0-incubating
>Reporter: xinzhang
>Assignee: Radar Lei
> Fix For: 2.2.0.0-incubating
>
>
> I install with the rpm on Centos7 (rpm -ivh pxf*.rpm).
> I start the pxf service.There is no debug logs. I need the debug logs as help
> me to understand pxf service.
> #vim pxf-log4j.properties
> {code:html}
> # log to a rolling file
> log4j.rootLogger=DEBUG, ROLLINGFILE
> # uncomment to see DEBUG messages from PXF service
> log4j.logger.org.apache.hawq.pxf=DEBUG
> {code}
> #less /var/log/pxf/catalina.out
> {code:java}
> Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol pause
> INFO: Pausing ProtocolHandler ["http-bio-51200"]
> Dec 11, 2017 2:27:14 AM org.apache.catalina.core.StandardService stopInternal
> INFO: Stopping service Catalina
> Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol stop
> INFO: Stopping ProtocolHandler ["http-bio-51200"]
> Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol destroy
> INFO: Destroying ProtocolHandler ["http-bio-51200"]
> Dec 11, 2017 2:27:17 AM org.apache.coyote.AbstractProtocol init
> INFO: Initializing ProtocolHandler ["http-bio-51200"]
> Dec 11, 2017 2:27:17 AM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 830 ms
> Dec 11, 2017 2:27:17 AM org.apache.catalina.core.StandardService startInternal
> INFO: Starting service Catalina
> Dec 11, 2017 2:27:17 AM org.apache.catalina.core.StandardEngine startInternal
> INFO: Starting Servlet Engine: Apache Tomcat/7.0.62
> Dec 11, 2017 2:27:17 AM org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive /var/pxf/pxf-service/webapps/pxf.war
> Dec 11, 2017 2:27:17 AM
> org.apache.hawq.pxf.service.utilities.CustomWebappLoader readClasspathFile
> INFO: Trying to read classpath file /etc/pxf/conf/pxf-private.classpath
> Dec 11, 2017 2:27:17 AM
> org.apache.hawq.pxf.service.utilities.CustomWebappLoader addRepositories
> INFO: Classpath file /etc/pxf/conf/pxf-private.classpath has 7 entries
> Dec 11, 2017 2:27:17 AM
> org.apache.hawq.pxf.service.utilities.CustomWebappLoader readClasspathFile
> INFO: Trying to read classpath file /etc/pxf/conf/pxf-public.classpath
> Dec 11, 2017 2:27:18 AM
> org.apache.hawq.pxf.service.utilities.CustomWebappLoader addRepositories
> INFO: Classpath file /etc/pxf/conf/pxf-public.classpath has 0 entries
> Dec 11, 2017 2:27:20 AM org.apache.catalina.core.ContainerBase
> addChildInternal
> SEVERE: ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException: Failed to start component
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/pxf]]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
> 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:652)
> at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1095)
> at
> org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1930)
> 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)
> Caused by: java.lang.LinkageError: loader constraint violation: loader
> (instance of org/apache/catalina/loader/WebappClassLoader) previously
> initiated loading for a different type with name
> "javax/servlet/ServletContext"
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at
>
[jira] [Updated] (HAWQ-1569) log4j log can not open level debug
[
https://issues.apache.org/jira/browse/HAWQ-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xinzhang updated HAWQ-1569:
---
Description:
I install with the rpm on Centos7 (rpm -ivh pxf*.rpm).
I start the pxf service.There is no debug logs. I need the debug logs as help
me to understand pxf service.
#vim pxf-log4j.properties
{code:html}
# log to a rolling file
log4j.rootLogger=DEBUG, ROLLINGFILE
# uncomment to see DEBUG messages from PXF service
log4j.logger.org.apache.hawq.pxf=DEBUG
{code}
#less /var/log/pxf/catalina.out
{code:java}
Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:14 AM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:17 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:17 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 830 ms
Dec 11, 2017 2:27:17 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Dec 11, 2017 2:27:17 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.62
Dec 11, 2017 2:27:17 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/pxf/pxf-service/webapps/pxf.war
Dec 11, 2017 2:27:17 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader readClasspathFile
INFO: Trying to read classpath file /etc/pxf/conf/pxf-private.classpath
Dec 11, 2017 2:27:17 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader addRepositories
INFO: Classpath file /etc/pxf/conf/pxf-private.classpath has 7 entries
Dec 11, 2017 2:27:17 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader readClasspathFile
INFO: Trying to read classpath file /etc/pxf/conf/pxf-public.classpath
Dec 11, 2017 2:27:18 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader addRepositories
INFO: Classpath file /etc/pxf/conf/pxf-public.classpath has 0 entries
Dec 11, 2017 2:27:20 AM org.apache.catalina.core.ContainerBase addChildInternal
SEVERE: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/pxf]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
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:652)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1095)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1930)
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)
Caused by: java.lang.LinkageError: loader constraint violation: loader
(instance of org/apache/catalina/loader/WebappClassLoader) previously initiated
loading for a different type with name "javax/servlet/ServletContext"
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
at
org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1227)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1690)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at java.lang.Class.getDeclaredMethods(Class.java:1975)
at
org.apache.catalina.util.Introspection.getDeclaredMethods(Introspection.java:127)
at
[jira] [Closed] (HAWQ-1570) Could not start the pxf service .
[
https://issues.apache.org/jira/browse/HAWQ-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xinzhang closed HAWQ-1570.
--
Resolution: Won't Fix
Fix Version/s: 2.2.0.0-incubating
Please ignore it.
> Could not start the pxf service .
> -
>
> Key: HAWQ-1570
> URL: https://issues.apache.org/jira/browse/HAWQ-1570
> Project: Apache HAWQ
> Issue Type: Bug
> Components: PXF
>Reporter: xinzhang
>Assignee: Ed Espino
> Fix For: 2.2.0.0-incubating
>
>
> I install the pxf with the official provided.(2.2.0). The service's status
> is fail.
> # service pxf-service status
> Checking if tomcat is up and running...
> Checking if PXF webapp is up and running...
> ERROR: PXF webapp is inaccessible but tomcat is up. Check logs for more
> information
> #less catalina.out
> {code:java}
> Dec 11, 2017 2:27:17 AM org.apache.coyote.AbstractProtocol init
> INFO: Initializing ProtocolHandler ["http-bio-51200"]
> Dec 11, 2017 2:27:17 AM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 830 ms
> Dec 11, 2017 2:27:17 AM org.apache.catalina.core.StandardService startInternal
> INFO: Starting service Catalina
> Dec 11, 2017 2:27:17 AM org.apache.catalina.core.StandardEngine startInternal
> INFO: Starting Servlet Engine: Apache Tomcat/7.0.62
> Dec 11, 2017 2:27:17 AM org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive /var/pxf/pxf-service/webapps/pxf.war
> Dec 11, 2017 2:27:17 AM
> org.apache.hawq.pxf.service.utilities.CustomWebappLoader readClasspathFile
> INFO: Trying to read classpath file /etc/pxf/conf/pxf-private.classpath
> Dec 11, 2017 2:27:17 AM
> org.apache.hawq.pxf.service.utilities.CustomWebappLoader addRepositories
> INFO: Classpath file /etc/pxf/conf/pxf-private.classpath has 7 entries
> Dec 11, 2017 2:27:17 AM
> org.apache.hawq.pxf.service.utilities.CustomWebappLoader readClasspathFile
> INFO: Trying to read classpath file /etc/pxf/conf/pxf-public.classpath
> Dec 11, 2017 2:27:18 AM
> org.apache.hawq.pxf.service.utilities.CustomWebappLoader addRepositories
> INFO: Classpath file /etc/pxf/conf/pxf-public.classpath has 0 entries
> Dec 11, 2017 2:27:20 AM org.apache.catalina.core.ContainerBase
> addChildInternal
> SEVERE: ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException: Failed to start component
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/pxf]]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
> 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:652)
> at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1095)
> at
> org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1930)
> 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)
> Caused by: java.lang.LinkageError: loader constraint violation: loader
> (instance of org/apache/catalina/loader/WebappClassLoader) previously
> initiated loading for a different type with name
> "javax/servlet/ServletContext"
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at
> org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1227)
> at
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1690)
> at
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
> at java.lang.Class.getDeclaredMethods(Class.java:1975)
> at
> org.apache.catalina.util.Introspection.getDeclaredMethods(Introspection.java:127)
> at
>
[jira] [Created] (HAWQ-1570) Could not start the pxf service .
xinzhang created HAWQ-1570:
--
Summary: Could not start the pxf service .
Key: HAWQ-1570
URL: https://issues.apache.org/jira/browse/HAWQ-1570
Project: Apache HAWQ
Issue Type: Bug
Components: PXF
Reporter: xinzhang
Assignee: Ed Espino
I install the pxf with the official provided.(2.2.0). The service's status is
fail.
# service pxf-service status
Checking if tomcat is up and running...
Checking if PXF webapp is up and running...
ERROR: PXF webapp is inaccessible but tomcat is up. Check logs for more
information
#less catalina.out
{code:java}
Dec 11, 2017 2:27:17 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:17 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 830 ms
Dec 11, 2017 2:27:17 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Dec 11, 2017 2:27:17 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.62
Dec 11, 2017 2:27:17 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/pxf/pxf-service/webapps/pxf.war
Dec 11, 2017 2:27:17 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader readClasspathFile
INFO: Trying to read classpath file /etc/pxf/conf/pxf-private.classpath
Dec 11, 2017 2:27:17 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader addRepositories
INFO: Classpath file /etc/pxf/conf/pxf-private.classpath has 7 entries
Dec 11, 2017 2:27:17 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader readClasspathFile
INFO: Trying to read classpath file /etc/pxf/conf/pxf-public.classpath
Dec 11, 2017 2:27:18 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader addRepositories
INFO: Classpath file /etc/pxf/conf/pxf-public.classpath has 0 entries
Dec 11, 2017 2:27:20 AM org.apache.catalina.core.ContainerBase addChildInternal
SEVERE: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/pxf]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
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:652)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1095)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1930)
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)
Caused by: java.lang.LinkageError: loader constraint violation: loader
(instance of org/apache/catalina/loader/WebappClassLoader) previously initiated
loading for a different type with name "javax/servlet/ServletContext"
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
at
org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1227)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1690)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at java.lang.Class.getDeclaredMethods(Class.java:1975)
at
org.apache.catalina.util.Introspection.getDeclaredMethods(Introspection.java:127)
at
org.apache.catalina.startup.WebAnnotationSet.loadMethodsAnnotation(WebAnnotationSet.java:287)
at
org.apache.catalina.startup.WebAnnotationSet.loadApplicationServletAnnotations(WebAnnotationSet.java:140)
at
org.apache.catalina.startup.WebAnnotationSet.loadApplicationAnnotations(WebAnnotationSet.java:65)
at
[jira] [Updated] (HAWQ-1569) log4j log can not open level debug
[
https://issues.apache.org/jira/browse/HAWQ-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xinzhang updated HAWQ-1569:
---
Affects Version/s: 2.2.0.0-incubating
Component/s: PXF
> log4j log can not open level debug
> ---
>
> Key: HAWQ-1569
> URL: https://issues.apache.org/jira/browse/HAWQ-1569
> Project: Apache HAWQ
> Issue Type: Bug
> Components: PXF
>Affects Versions: 2.2.0.0-incubating
>Reporter: xinzhang
>Assignee: Radar Lei
>
> I install with the rpm on Centos7 (rpm -ivh pxf*.rpm).
> I start the pxf service.There is no debug logs. I need debug log help me to
> start pxf service.
> #vim pxf-log4j.properties
> {code:html}
> # log to a rolling file
> log4j.rootLogger=DEBUG, ROLLINGFILE
> # uncomment to see DEBUG messages from PXF service
> log4j.logger.org.apache.hawq.pxf=DEBUG
> {code}
> #less /var/log/pxf/catalina.out
> {code:java}
> Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol pause
> INFO: Pausing ProtocolHandler ["http-bio-51200"]
> Dec 11, 2017 2:27:14 AM org.apache.catalina.core.StandardService stopInternal
> INFO: Stopping service Catalina
> Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol stop
> INFO: Stopping ProtocolHandler ["http-bio-51200"]
> Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol destroy
> INFO: Destroying ProtocolHandler ["http-bio-51200"]
> Dec 11, 2017 2:27:17 AM org.apache.coyote.AbstractProtocol init
> INFO: Initializing ProtocolHandler ["http-bio-51200"]
> Dec 11, 2017 2:27:17 AM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 830 ms
> Dec 11, 2017 2:27:17 AM org.apache.catalina.core.StandardService startInternal
> INFO: Starting service Catalina
> Dec 11, 2017 2:27:17 AM org.apache.catalina.core.StandardEngine startInternal
> INFO: Starting Servlet Engine: Apache Tomcat/7.0.62
> Dec 11, 2017 2:27:17 AM org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive /var/pxf/pxf-service/webapps/pxf.war
> Dec 11, 2017 2:27:17 AM
> org.apache.hawq.pxf.service.utilities.CustomWebappLoader readClasspathFile
> INFO: Trying to read classpath file /etc/pxf/conf/pxf-private.classpath
> Dec 11, 2017 2:27:17 AM
> org.apache.hawq.pxf.service.utilities.CustomWebappLoader addRepositories
> INFO: Classpath file /etc/pxf/conf/pxf-private.classpath has 7 entries
> Dec 11, 2017 2:27:17 AM
> org.apache.hawq.pxf.service.utilities.CustomWebappLoader readClasspathFile
> INFO: Trying to read classpath file /etc/pxf/conf/pxf-public.classpath
> Dec 11, 2017 2:27:18 AM
> org.apache.hawq.pxf.service.utilities.CustomWebappLoader addRepositories
> INFO: Classpath file /etc/pxf/conf/pxf-public.classpath has 0 entries
> Dec 11, 2017 2:27:20 AM org.apache.catalina.core.ContainerBase
> addChildInternal
> SEVERE: ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException: Failed to start component
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/pxf]]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
> 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:652)
> at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1095)
> at
> org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1930)
> 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)
> Caused by: java.lang.LinkageError: loader constraint violation: loader
> (instance of org/apache/catalina/loader/WebappClassLoader) previously
> initiated loading for a different type with name
> "javax/servlet/ServletContext"
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at
> org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1227)
>
[jira] [Updated] (HAWQ-1569) log4j log can not open level debug
[
https://issues.apache.org/jira/browse/HAWQ-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xinzhang updated HAWQ-1569:
---
Description:
I install with the rpm on Centos7 (rpm -ivh pxf*.rpm).
I start the pxf service.There is no debug logs. I need debug log help me to
start pxf service.
#vim pxf-log4j.properties
{code:html}
# log to a rolling file
log4j.rootLogger=DEBUG, ROLLINGFILE
# uncomment to see DEBUG messages from PXF service
log4j.logger.org.apache.hawq.pxf=DEBUG
{code}
#less /var/log/pxf/catalina.out
{code:java}
Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:14 AM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:17 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:17 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 830 ms
Dec 11, 2017 2:27:17 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Dec 11, 2017 2:27:17 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.62
Dec 11, 2017 2:27:17 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/pxf/pxf-service/webapps/pxf.war
Dec 11, 2017 2:27:17 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader readClasspathFile
INFO: Trying to read classpath file /etc/pxf/conf/pxf-private.classpath
Dec 11, 2017 2:27:17 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader addRepositories
INFO: Classpath file /etc/pxf/conf/pxf-private.classpath has 7 entries
Dec 11, 2017 2:27:17 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader readClasspathFile
INFO: Trying to read classpath file /etc/pxf/conf/pxf-public.classpath
Dec 11, 2017 2:27:18 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader addRepositories
INFO: Classpath file /etc/pxf/conf/pxf-public.classpath has 0 entries
Dec 11, 2017 2:27:20 AM org.apache.catalina.core.ContainerBase addChildInternal
SEVERE: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/pxf]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
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:652)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1095)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1930)
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)
Caused by: java.lang.LinkageError: loader constraint violation: loader
(instance of org/apache/catalina/loader/WebappClassLoader) previously initiated
loading for a different type with name "javax/servlet/ServletContext"
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
at
org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1227)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1690)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at java.lang.Class.getDeclaredMethods(Class.java:1975)
at
org.apache.catalina.util.Introspection.getDeclaredMethods(Introspection.java:127)
at
[jira] [Updated] (HAWQ-1569) log4j log can not open level debug
[
https://issues.apache.org/jira/browse/HAWQ-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xinzhang updated HAWQ-1569:
---
Description:
#vim pxf-log4j.properties
{code:html}
# log to a rolling file
log4j.rootLogger=DEBUG, ROLLINGFILE
# uncomment to see DEBUG messages from PXF service
log4j.logger.org.apache.hawq.pxf=DEBUG
{code}
#less /var/log/pxf/catalina.out
{code:java}
Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:14 AM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:17 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:17 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 830 ms
Dec 11, 2017 2:27:17 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Dec 11, 2017 2:27:17 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.62
Dec 11, 2017 2:27:17 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/pxf/pxf-service/webapps/pxf.war
Dec 11, 2017 2:27:17 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader readClasspathFile
INFO: Trying to read classpath file /etc/pxf/conf/pxf-private.classpath
Dec 11, 2017 2:27:17 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader addRepositories
INFO: Classpath file /etc/pxf/conf/pxf-private.classpath has 7 entries
Dec 11, 2017 2:27:17 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader readClasspathFile
INFO: Trying to read classpath file /etc/pxf/conf/pxf-public.classpath
Dec 11, 2017 2:27:18 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader addRepositories
INFO: Classpath file /etc/pxf/conf/pxf-public.classpath has 0 entries
Dec 11, 2017 2:27:20 AM org.apache.catalina.core.ContainerBase addChildInternal
SEVERE: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/pxf]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
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:652)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1095)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1930)
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)
Caused by: java.lang.LinkageError: loader constraint violation: loader
(instance of org/apache/catalina/loader/WebappClassLoader) previously initiated
loading for a different type with name "javax/servlet/ServletContext"
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
at
org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1227)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1690)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at java.lang.Class.getDeclaredMethods(Class.java:1975)
at
org.apache.catalina.util.Introspection.getDeclaredMethods(Introspection.java:127)
at
org.apache.catalina.startup.WebAnnotationSet.loadMethodsAnnotation(WebAnnotationSet.java:287)
at
org.apache.catalina.startup.WebAnnotationSet.loadApplicationServletAnnotations(WebAnnotationSet.java:140)
[jira] [Created] (HAWQ-1569) log4j log can not open level debug
xinzhang created HAWQ-1569:
--
Summary: log4j log can not open level debug
Key: HAWQ-1569
URL: https://issues.apache.org/jira/browse/HAWQ-1569
Project: Apache HAWQ
Issue Type: Bug
Reporter: xinzhang
Assignee: Radar Lei
#vim pxf-log4j.properties
{code:html}
# log to a rolling file
log4j.rootLogger=DEBUG, ROLLINGFILE
# uncomment to see DEBUG messages from PXF service
log4j.logger.org.apache.hawq.pxf=DEBUG
{code}
#less /var/log/pxf/catalina.out
{code:java}
Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:14 AM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:14 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:17 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-51200"]
Dec 11, 2017 2:27:17 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 830 ms
Dec 11, 2017 2:27:17 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Dec 11, 2017 2:27:17 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.62
Dec 11, 2017 2:27:17 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/pxf/pxf-service/webapps/pxf.war
Dec 11, 2017 2:27:17 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader readClasspathFile
INFO: Trying to read classpath file /etc/pxf/conf/pxf-private.classpath
Dec 11, 2017 2:27:17 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader addRepositories
INFO: Classpath file /etc/pxf/conf/pxf-private.classpath has 7 entries
Dec 11, 2017 2:27:17 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader readClasspathFile
INFO: Trying to read classpath file /etc/pxf/conf/pxf-public.classpath
Dec 11, 2017 2:27:18 AM
org.apache.hawq.pxf.service.utilities.CustomWebappLoader addRepositories
INFO: Classpath file /etc/pxf/conf/pxf-public.classpath has 0 entries
Dec 11, 2017 2:27:20 AM org.apache.catalina.core.ContainerBase addChildInternal
SEVERE: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/pxf]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
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:652)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1095)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1930)
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)
Caused by: java.lang.LinkageError: loader constraint violation: loader
(instance of org/apache/catalina/loader/WebappClassLoader) previously initiated
loading for a different type with name "javax/servlet/ServletContext"
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
at
org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1227)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1690)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at java.lang.Class.getDeclaredMethods(Class.java:1975)
at
org.apache.catalina.util.Introspection.getDeclaredMethods(Introspection.java:127)
at
[jira] [Resolved] (HAWQ-1568) install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro?
[
https://issues.apache.org/jira/browse/HAWQ-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xinzhang resolved HAWQ-1568.
Resolution: Won't Fix
Fix Version/s: 2.2.0.0-incubating
> install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro?
> --
>
> Key: HAWQ-1568
> URL: https://issues.apache.org/jira/browse/HAWQ-1568
> Project: Apache HAWQ
> Issue Type: Bug
>Reporter: xinzhang
>Assignee: Radar Lei
> Fix For: 2.2.0.0-incubating
>
>
> Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm)
> But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm)
>
> {code:actionscript}
> [gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh
> pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
> error: Failed dependencies:
> pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> {code}
> I install hadoop with .tar
>
> {code:actionscript}
> [gpadmin@gpmaster hawq_rpm_packages]$ which hadoop
> /opt/hadoop/hadoop-2.9.0/bin/hadoop
> [gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME
> /opt/hadoop/hadoop-2.9.0
> {code}
> How to let rpm know my Hadoop had installed.
>
> btw:
> The rpms builded Centos7 and Centos6 ?
> (el7=Centos7 el6=Centos6)
> If so, It is in disorder.
> {code:actionscript}
> [root@gpmaster hawq_rpm_packages]# ll
> total 91304
> -rw-r--r--. 1 root root 84103760 Jun 23 01:54
> apache-hawq-2.2.0.0-el7.x86_64.rpm
> -rw-r--r--. 1 root root 8892454 Jun 23 01:54
> apache-tomcat-7.0.62-el6.noarch.rpm
> -rw-r--r--. 1 root root 5668 Jun 23 01:54 pxf-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root33188 Jun 23 01:54
> pxf-hbase-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root57270 Jun 23 01:54
> pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root74971 Jun 23 01:54
> pxf-hive-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root30847 Jun 23 01:54
> pxf-jdbc-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root24833 Jun 23 01:54
> pxf-json-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root 246454 Jun 23 01:54
> pxf-service-3.2.1.0-1.el6.noarch.rpm
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HAWQ-1568) install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro?
[
https://issues.apache.org/jira/browse/HAWQ-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279892#comment-16279892
]
xinzhang commented on HAWQ-1568:
Thanks for your reply.
> install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro?
> --
>
> Key: HAWQ-1568
> URL: https://issues.apache.org/jira/browse/HAWQ-1568
> Project: Apache HAWQ
> Issue Type: Bug
>Reporter: xinzhang
>Assignee: Radar Lei
>
> Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm)
> But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm)
>
> {code:actionscript}
> [gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh
> pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
> error: Failed dependencies:
> pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> {code}
> I install hadoop with .tar
>
> {code:actionscript}
> [gpadmin@gpmaster hawq_rpm_packages]$ which hadoop
> /opt/hadoop/hadoop-2.9.0/bin/hadoop
> [gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME
> /opt/hadoop/hadoop-2.9.0
> {code}
> How to let rpm know my Hadoop had installed.
>
> btw:
> The rpms builded Centos7 and Centos6 ?
> (el7=Centos7 el6=Centos6)
> If so, It is in disorder.
> {code:actionscript}
> [root@gpmaster hawq_rpm_packages]# ll
> total 91304
> -rw-r--r--. 1 root root 84103760 Jun 23 01:54
> apache-hawq-2.2.0.0-el7.x86_64.rpm
> -rw-r--r--. 1 root root 8892454 Jun 23 01:54
> apache-tomcat-7.0.62-el6.noarch.rpm
> -rw-r--r--. 1 root root 5668 Jun 23 01:54 pxf-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root33188 Jun 23 01:54
> pxf-hbase-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root57270 Jun 23 01:54
> pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root74971 Jun 23 01:54
> pxf-hive-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root30847 Jun 23 01:54
> pxf-jdbc-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root24833 Jun 23 01:54
> pxf-json-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root 246454 Jun 23 01:54
> pxf-service-3.2.1.0-1.el6.noarch.rpm
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HAWQ-1568) install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro?
[
https://issues.apache.org/jira/browse/HAWQ-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279887#comment-16279887
]
xinzhang commented on HAWQ-1568:
ye . I noticed that . The wiki use the bigtop. Does it mean if I install with
rpm , the other ways (using binary hadoop without rpm installs like tar) are
not support?
If I use tar, I must build HAWQ from source code for now .
Am I right?
> install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro?
> --
>
> Key: HAWQ-1568
> URL: https://issues.apache.org/jira/browse/HAWQ-1568
> Project: Apache HAWQ
> Issue Type: Bug
>Reporter: xinzhang
>Assignee: Radar Lei
>
> Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm)
> But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm)
>
> {code:actionscript}
> [gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh
> pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
> error: Failed dependencies:
> pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> {code}
> I install hadoop with .tar
>
> {code:actionscript}
> [gpadmin@gpmaster hawq_rpm_packages]$ which hadoop
> /opt/hadoop/hadoop-2.9.0/bin/hadoop
> [gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME
> /opt/hadoop/hadoop-2.9.0
> {code}
> How to let rpm know my Hadoop had installed.
>
> btw:
> The rpms builded Centos7 and Centos6 ?
> (el7=Centos7 el6=Centos6)
> If so, It is in disorder.
> {code:actionscript}
> [root@gpmaster hawq_rpm_packages]# ll
> total 91304
> -rw-r--r--. 1 root root 84103760 Jun 23 01:54
> apache-hawq-2.2.0.0-el7.x86_64.rpm
> -rw-r--r--. 1 root root 8892454 Jun 23 01:54
> apache-tomcat-7.0.62-el6.noarch.rpm
> -rw-r--r--. 1 root root 5668 Jun 23 01:54 pxf-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root33188 Jun 23 01:54
> pxf-hbase-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root57270 Jun 23 01:54
> pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root74971 Jun 23 01:54
> pxf-hive-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root30847 Jun 23 01:54
> pxf-jdbc-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root24833 Jun 23 01:54
> pxf-json-3.2.1.0-1.el6.noarch.rpm
> -rw-r--r--. 1 root root 246454 Jun 23 01:54
> pxf-service-3.2.1.0-1.el6.noarch.rpm
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HAWQ-1568) install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro?
[
https://issues.apache.org/jira/browse/HAWQ-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xinzhang updated HAWQ-1568:
---
Description:
Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm)
But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm)
{code:actionscript}
[gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
error: Failed dependencies:
pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
{code}
I install hadoop with .tar
{code:actionscript}
[gpadmin@gpmaster hawq_rpm_packages]$ which hadoop
/opt/hadoop/hadoop-2.9.0/bin/hadoop
[gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME
/opt/hadoop/hadoop-2.9.0
{code}
How to let rpm know my Hadoop had installed.
btw:
The rpms builded Centos7 and Centos6 ?
(el7=Centos7 el6=Centos6)
If so, It is in disorder.
{code:actionscript}
[root@gpmaster hawq_rpm_packages]# ll
total 91304
-rw-r--r--. 1 root root 84103760 Jun 23 01:54 apache-hawq-2.2.0.0-el7.x86_64.rpm
-rw-r--r--. 1 root root 8892454 Jun 23 01:54
apache-tomcat-7.0.62-el6.noarch.rpm
-rw-r--r--. 1 root root 5668 Jun 23 01:54 pxf-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root33188 Jun 23 01:54 pxf-hbase-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root57270 Jun 23 01:54 pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root74971 Jun 23 01:54 pxf-hive-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root30847 Jun 23 01:54 pxf-jdbc-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root24833 Jun 23 01:54 pxf-json-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root 246454 Jun 23 01:54
pxf-service-3.2.1.0-1.el6.noarch.rpm
{code}
was:
Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm)
But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm)
[gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
error: Failed dependencies:
pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
I install hadoop with .tar
[gpadmin@gpmaster hawq_rpm_packages]$ which hadoop
/opt/hadoop/hadoop-2.9.0/bin/hadoop
[gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME
/opt/hadoop/hadoop-2.9.0
How to let rpm know my Hadoop had installed.
btw:
The rpms builded Centos7 and Centos6 ?
(el7=Centos7 el6=Centos6)
If so, It is in disorder.
{code:actionscript}
[root@gpmaster hawq_rpm_packages]# ll
total 91304
-rw-r--r--. 1 root root 84103760 Jun 23 01:54 apache-hawq-2.2.0.0-el7.x86_64.rpm
-rw-r--r--. 1 root root 8892454 Jun 23 01:54
apache-tomcat-7.0.62-el6.noarch.rpm
-rw-r--r--. 1 root root 5668 Jun 23 01:54 pxf-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root33188 Jun 23 01:54 pxf-hbase-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root57270 Jun 23 01:54 pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root74971 Jun 23 01:54 pxf-hive-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root30847 Jun 23 01:54 pxf-jdbc-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root24833 Jun 23 01:54 pxf-json-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root 246454 Jun 23 01:54
pxf-service-3.2.1.0-1.el6.noarch.rpm
{code}
> install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro?
> --
>
> Key: HAWQ-1568
> URL: https://issues.apache.org/jira/browse/HAWQ-1568
> Project: Apache HAWQ
> Issue Type: Bug
>Reporter: xinzhang
>Assignee: Radar Lei
>
> Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm)
> But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm)
>
> {code:actionscript}
> [gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh
> pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
> error: Failed dependencies:
> pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> {code}
> I install hadoop with .tar
>
> {code:actionscript}
> [gpadmin@gpmaster hawq_rpm_packages]$ which hadoop
> /opt/hadoop/hadoop-2.9.0/bin/hadoop
> [gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME
> /opt/hadoop/hadoop-2.9.0
> {code}
> How to let rpm know my Hadoop had installed.
>
> btw:
> The rpms builded Centos7 and Centos6 ?
> (el7=Centos7 el6=Centos6)
> If so, It is in disorder.
> {code:actionscript}
> [root@gpmaster hawq_rpm_packages]# ll
>
[jira] [Updated] (HAWQ-1568) install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro?
[
https://issues.apache.org/jira/browse/HAWQ-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xinzhang updated HAWQ-1568:
---
Description:
Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm)
But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm)
[gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
error: Failed dependencies:
pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
I install hadoop with .tar
[gpadmin@gpmaster hawq_rpm_packages]$ which hadoop
/opt/hadoop/hadoop-2.9.0/bin/hadoop
[gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME
/opt/hadoop/hadoop-2.9.0
How to let rpm know my Hadoop had installed.
btw:
The rpms builded Centos7 and Centos6 ?
(el7=Centos7 el6=Centos6)
If so, It is in disorder.
{code:actionscript}
[root@gpmaster hawq_rpm_packages]# ll
total 91304
-rw-r--r--. 1 root root 84103760 Jun 23 01:54 apache-hawq-2.2.0.0-el7.x86_64.rpm
-rw-r--r--. 1 root root 8892454 Jun 23 01:54
apache-tomcat-7.0.62-el6.noarch.rpm
-rw-r--r--. 1 root root 5668 Jun 23 01:54 pxf-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root33188 Jun 23 01:54 pxf-hbase-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root57270 Jun 23 01:54 pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root74971 Jun 23 01:54 pxf-hive-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root30847 Jun 23 01:54 pxf-jdbc-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root24833 Jun 23 01:54 pxf-json-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root 246454 Jun 23 01:54
pxf-service-3.2.1.0-1.el6.noarch.rpm
{code}
was:
Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm)
But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm)
[gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
error: Failed dependencies:
pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
I install hadoop with .tar
[gpadmin@gpmaster hawq_rpm_packages]$ which hadoop
/opt/hadoop/hadoop-2.9.0/bin/hadoop
[gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME
/opt/hadoop/hadoop-2.9.0
How to let rpm know my Hadoop had installed.
btw:
The rpms builded Centos7 and Centos6 ?
(el7=Centos7 el6=Centos6)
If so, It is in disorder.
{code:shell}
[root@gpmaster hawq_rpm_packages]# ll
total 91304
-rw-r--r--. 1 root root 84103760 Jun 23 01:54 apache-hawq-2.2.0.0-el7.x86_64.rpm
-rw-r--r--. 1 root root 8892454 Jun 23 01:54
apache-tomcat-7.0.62-el6.noarch.rpm
-rw-r--r--. 1 root root 5668 Jun 23 01:54 pxf-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root33188 Jun 23 01:54 pxf-hbase-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root57270 Jun 23 01:54 pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root74971 Jun 23 01:54 pxf-hive-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root30847 Jun 23 01:54 pxf-jdbc-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root24833 Jun 23 01:54 pxf-json-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root 246454 Jun 23 01:54
pxf-service-3.2.1.0-1.el6.noarch.rpm
{code}
> install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro?
> --
>
> Key: HAWQ-1568
> URL: https://issues.apache.org/jira/browse/HAWQ-1568
> Project: Apache HAWQ
> Issue Type: Bug
>Reporter: xinzhang
>Assignee: Radar Lei
>
> Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm)
> But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm)
>
> [gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh
> pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
> error: Failed dependencies:
> pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> I install hadoop with .tar
>
> [gpadmin@gpmaster hawq_rpm_packages]$ which hadoop
> /opt/hadoop/hadoop-2.9.0/bin/hadoop
> [gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME
> /opt/hadoop/hadoop-2.9.0
> How to let rpm know my Hadoop had installed.
>
> btw:
> The rpms builded Centos7 and Centos6 ?
> (el7=Centos7 el6=Centos6)
> If so, It is in disorder.
> {code:actionscript}
> [root@gpmaster hawq_rpm_packages]# ll
> total 91304
> -rw-r--r--. 1 root root 84103760 Jun 23 01:54
> apache-hawq-2.2.0.0-el7.x86_64.rpm
> -rw-r--r--. 1 root root
[jira] [Updated] (HAWQ-1568) install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro?
[
https://issues.apache.org/jira/browse/HAWQ-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xinzhang updated HAWQ-1568:
---
Description:
Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm)
But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm)
[gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
error: Failed dependencies:
pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
I install hadoop with .tar
[gpadmin@gpmaster hawq_rpm_packages]$ which hadoop
/opt/hadoop/hadoop-2.9.0/bin/hadoop
[gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME
/opt/hadoop/hadoop-2.9.0
How to let rpm know my Hadoop had installed.
btw:
The rpms builded Centos7 and Centos6 ?
(el7=Centos7 el6=Centos6)
If so, It is in disorder.
{code:shell}
[root@gpmaster hawq_rpm_packages]# ll
total 91304
-rw-r--r--. 1 root root 84103760 Jun 23 01:54 apache-hawq-2.2.0.0-el7.x86_64.rpm
-rw-r--r--. 1 root root 8892454 Jun 23 01:54
apache-tomcat-7.0.62-el6.noarch.rpm
-rw-r--r--. 1 root root 5668 Jun 23 01:54 pxf-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root33188 Jun 23 01:54 pxf-hbase-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root57270 Jun 23 01:54 pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root74971 Jun 23 01:54 pxf-hive-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root30847 Jun 23 01:54 pxf-jdbc-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root24833 Jun 23 01:54 pxf-json-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root 246454 Jun 23 01:54
pxf-service-3.2.1.0-1.el6.noarch.rpm
{code}
was:
Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm)
But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm)
[gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
error: Failed dependencies:
pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
I install hadoop with .tar
[gpadmin@gpmaster hawq_rpm_packages]$ which hadoop
/opt/hadoop/hadoop-2.9.0/bin/hadoop
[gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME
/opt/hadoop/hadoop-2.9.0
How to let rpm know my Hadoop had installed.
btw:
The rpms builded Centos7 and Centos6 ?
(el7=Centos7 el6=Centos6)
If so, It is in disorder.
[root@gpmaster hawq_rpm_packages]# ll
total 91304
-rw-r--r--. 1 root root 84103760 Jun 23 01:54 apache-hawq-2.2.0.0-el7.x86_64.rpm
-rw-r--r--. 1 root root 8892454 Jun 23 01:54
apache-tomcat-7.0.62-el6.noarch.rpm
-rw-r--r--. 1 root root 5668 Jun 23 01:54 pxf-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root33188 Jun 23 01:54 pxf-hbase-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root57270 Jun 23 01:54 pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root74971 Jun 23 01:54 pxf-hive-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root30847 Jun 23 01:54 pxf-jdbc-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root24833 Jun 23 01:54 pxf-json-3.2.1.0-1.el6.noarch.rpm
-rw-r--r--. 1 root root 246454 Jun 23 01:54
pxf-service-3.2.1.0-1.el6.noarch.rpm
> install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro?
> --
>
> Key: HAWQ-1568
> URL: https://issues.apache.org/jira/browse/HAWQ-1568
> Project: Apache HAWQ
> Issue Type: Bug
>Reporter: xinzhang
>Assignee: Radar Lei
>
> Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm)
> But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm)
>
> [gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh
> pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
> error: Failed dependencies:
> pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
> I install hadoop with .tar
>
> [gpadmin@gpmaster hawq_rpm_packages]$ which hadoop
> /opt/hadoop/hadoop-2.9.0/bin/hadoop
> [gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME
> /opt/hadoop/hadoop-2.9.0
> How to let rpm know my Hadoop had installed.
>
> btw:
> The rpms builded Centos7 and Centos6 ?
> (el7=Centos7 el6=Centos6)
> If so, It is in disorder.
> {code:shell}
> [root@gpmaster hawq_rpm_packages]# ll
> total 91304
> -rw-r--r--. 1 root root 84103760 Jun 23 01:54
> apache-hawq-2.2.0.0-el7.x86_64.rpm
> -rw-r--r--. 1 root root 8892454 Jun 23 01:54
>
[jira] [Updated] (HAWQ-1568) install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro?
[ https://issues.apache.org/jira/browse/HAWQ-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xinzhang updated HAWQ-1568: --- Description: Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm) But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm) [gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh pxf-hdfs-3.2.1.0-1.el6.noarch.rpm error: Failed dependencies: pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch I install hadoop with .tar [gpadmin@gpmaster hawq_rpm_packages]$ which hadoop /opt/hadoop/hadoop-2.9.0/bin/hadoop [gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME /opt/hadoop/hadoop-2.9.0 How to let rpm know my Hadoop had installed. btw: The rpms builded Centos7 and Centos6 ? (el7=Centos7 el6=Centos6) If so, It is in disorder. [root@gpmaster hawq_rpm_packages]# ll total 91304 -rw-r--r--. 1 root root 84103760 Jun 23 01:54 apache-hawq-2.2.0.0-el7.x86_64.rpm -rw-r--r--. 1 root root 8892454 Jun 23 01:54 apache-tomcat-7.0.62-el6.noarch.rpm -rw-r--r--. 1 root root 5668 Jun 23 01:54 pxf-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root33188 Jun 23 01:54 pxf-hbase-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root57270 Jun 23 01:54 pxf-hdfs-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root74971 Jun 23 01:54 pxf-hive-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root30847 Jun 23 01:54 pxf-jdbc-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root24833 Jun 23 01:54 pxf-json-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root 246454 Jun 23 01:54 pxf-service-3.2.1.0-1.el6.noarch.rpm was: Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm) But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm) [gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh pxf-hdfs-3.2.1.0-1.el6.noarch.rpm error: Failed dependencies: pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch I install hadoop with .tar [gpadmin@gpmaster hawq_rpm_packages]$ which hadoop /opt/hadoop/hadoop-2.9.0/bin/hadoop [gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME /opt/hadoop/hadoop-2.9.0 How to let rpm know my Hadoop had installed. btw: The rpms builded Centos7 and Centos6 ? (el7=Centos7 el6=Centos6) If so, It is in disorder. [root@gpmaster hawq_rpm_packages]# ll total 91304 -rw-r--r--. 1 root root 84103760 Jun 23 01:54 apache-hawq-2.2.0.0-el7.x86_64.rpm -rw-r--r--. 1 root root 8892454 Jun 23 01:54 apache-tomcat-7.0.62-el6.noarch.rpm -rw-r--r--. 1 root root 5668 Jun 23 01:54 pxf-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root33188 Jun 23 01:54 pxf-hbase-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root57270 Jun 23 01:54 pxf-hdfs-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root74971 Jun 23 01:54 pxf-hive-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root30847 Jun 23 01:54 pxf-jdbc-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root24833 Jun 23 01:54 pxf-json-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root 246454 Jun 23 01:54 pxf-service-3.2.1.0-1.el6.noarch.rpm > install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro? > -- > > Key: HAWQ-1568 > URL: https://issues.apache.org/jira/browse/HAWQ-1568 > Project: Apache HAWQ > Issue Type: Bug >Reporter: xinzhang >Assignee: Radar Lei > > Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm) > But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm) > > [gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh > pxf-hdfs-3.2.1.0-1.el6.noarch.rpm > error: Failed dependencies: > pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch > hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch > hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch > I install hadoop with .tar > > [gpadmin@gpmaster hawq_rpm_packages]$ which hadoop > /opt/hadoop/hadoop-2.9.0/bin/hadoop > [gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME > /opt/hadoop/hadoop-2.9.0 > How to let rpm know my Hadoop had installed. > > btw: > The rpms builded Centos7 and Centos6 ? > (el7=Centos7 el6=Centos6) > If so, It is in disorder. > [root@gpmaster hawq_rpm_packages]# ll > total 91304 > -rw-r--r--. 1 root root 84103760 Jun 23 01:54 > apache-hawq-2.2.0.0-el7.x86_64.rpm > -rw-r--r--. 1 root root 8892454 Jun 23 01:54 > apache-tomcat-7.0.62-el6.noarch.rpm >
[jira] [Updated] (HAWQ-1568) install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro?
[ https://issues.apache.org/jira/browse/HAWQ-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xinzhang updated HAWQ-1568: --- Description: Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm) But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm) [gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh pxf-hdfs-3.2.1.0-1.el6.noarch.rpm error: Failed dependencies: pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch I install hadoop with .tar [gpadmin@gpmaster hawq_rpm_packages]$ which hadoop /opt/hadoop/hadoop-2.9.0/bin/hadoop [gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME /opt/hadoop/hadoop-2.9.0 How to let rpm know my Hadoop had installed. btw: The rpms builded Centos7 and Centos6 ? (el7=Centos7 el6=Centos6) If so, It is in disorder. [root@gpmaster hawq_rpm_packages]# ll total 91304 -rw-r--r--. 1 root root 84103760 Jun 23 01:54 apache-hawq-2.2.0.0-el7.x86_64.rpm -rw-r--r--. 1 root root 8892454 Jun 23 01:54 apache-tomcat-7.0.62-el6.noarch.rpm -rw-r--r--. 1 root root 5668 Jun 23 01:54 pxf-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root33188 Jun 23 01:54 pxf-hbase-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root57270 Jun 23 01:54 pxf-hdfs-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root74971 Jun 23 01:54 pxf-hive-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root30847 Jun 23 01:54 pxf-jdbc-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root24833 Jun 23 01:54 pxf-json-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root 246454 Jun 23 01:54 pxf-service-3.2.1.0-1.el6.noarch.rpm was: Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm) But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm) [gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh pxf-hdfs-3.2.1.0-1.el6.noarch.rpm error: Failed dependencies: pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch I install hadoop with .tar [gpadmin@gpmaster hawq_rpm_packages]$ which hadoop /opt/hadoop/hadoop-2.9.0/bin/hadoop [gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME /opt/hadoop/hadoop-2.9.0 How to let rpm know my Hadoop had installed. btw: The rpms builded Centos7 and Centos6 ? (el7=Centos7 el6=Centos6) If so, It is in disorder. [root@gpmaster hawq_rpm_packages]# ll total 91304 -rw-r--r--. 1 root root 84103760 Jun 23 01:54 apache-hawq-2.2.0.0-el7.x86_64.rpm -rw-r--r--. 1 root root 8892454 Jun 23 01:54 apache-tomcat-7.0.62-el6.noarch.rpm -rw-r--r--. 1 root root 5668 Jun 23 01:54 pxf-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root33188 Jun 23 01:54 pxf-hbase-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root57270 Jun 23 01:54 pxf-hdfs-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root74971 Jun 23 01:54 pxf-hive-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root30847 Jun 23 01:54 pxf-jdbc-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root24833 Jun 23 01:54 pxf-json-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root 246454 Jun 23 01:54 pxf-service-3.2.1.0-1.el6.noarch.rpm > install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro? > -- > > Key: HAWQ-1568 > URL: https://issues.apache.org/jira/browse/HAWQ-1568 > Project: Apache HAWQ > Issue Type: Bug >Reporter: xinzhang >Assignee: Radar Lei > > Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm) > But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm) > > [gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh > pxf-hdfs-3.2.1.0-1.el6.noarch.rpm > error: Failed dependencies: > pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch > hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch > hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch > I install hadoop with .tar > > [gpadmin@gpmaster hawq_rpm_packages]$ which hadoop > /opt/hadoop/hadoop-2.9.0/bin/hadoop > [gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME > /opt/hadoop/hadoop-2.9.0 > How to let rpm know my Hadoop had installed. > > btw: > The rpms builded Centos7 and Centos6 ? > (el7=Centos7 el6=Centos6) > If so, It is in disorder. > [root@gpmaster hawq_rpm_packages]# ll > total 91304 > -rw-r--r--. 1 root root 84103760 Jun 23 01:54 > apache-hawq-2.2.0.0-el7.x86_64.rpm > -rw-r--r--. 1 root root 8892454 Jun 23 01:54 > apache-tomcat-7.0.62-el6.noarch.rpm >
[jira] [Updated] (HAWQ-1568) install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro?
[ https://issues.apache.org/jira/browse/HAWQ-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xinzhang updated HAWQ-1568: --- Description: Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm) But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm) [gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh pxf-hdfs-3.2.1.0-1.el6.noarch.rpm error: Failed dependencies: pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch I install hadoop with .tar [gpadmin@gpmaster hawq_rpm_packages]$ which hadoop /opt/hadoop/hadoop-2.9.0/bin/hadoop [gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME /opt/hadoop/hadoop-2.9.0 How to let rpm know my Hadoop had installed. btw: The rpms builded Centos7 and Centos6 ? (el7=Centos7 el6=Centos6) If so, It is in disorder. [root@gpmaster hawq_rpm_packages]# ll total 91304 -rw-r--r--. 1 root root 84103760 Jun 23 01:54 apache-hawq-2.2.0.0-el7.x86_64.rpm -rw-r--r--. 1 root root 8892454 Jun 23 01:54 apache-tomcat-7.0.62-el6.noarch.rpm -rw-r--r--. 1 root root 5668 Jun 23 01:54 pxf-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root33188 Jun 23 01:54 pxf-hbase-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root57270 Jun 23 01:54 pxf-hdfs-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root74971 Jun 23 01:54 pxf-hive-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root30847 Jun 23 01:54 pxf-jdbc-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root24833 Jun 23 01:54 pxf-json-3.2.1.0-1.el6.noarch.rpm -rw-r--r--. 1 root root 246454 Jun 23 01:54 pxf-service-3.2.1.0-1.el6.noarch.rpm was: Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm) But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm) [gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh pxf-hdfs-3.2.1.0-1.el6.noarch.rpm error: Failed dependencies: pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch I install hadoop with .tar [gpadmin@gpmaster hawq_rpm_packages]$ which hadoop /opt/hadoop/hadoop-2.9.0/bin/hadoop [gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME /opt/hadoop/hadoop-2.9.0 How to let rpm know my Hadoop had installed. > install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro? > -- > > Key: HAWQ-1568 > URL: https://issues.apache.org/jira/browse/HAWQ-1568 > Project: Apache HAWQ > Issue Type: Bug >Reporter: xinzhang >Assignee: Radar Lei > > Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm) > But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm) > > [gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh > pxf-hdfs-3.2.1.0-1.el6.noarch.rpm > error: Failed dependencies: > pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch > hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch > hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch > I install hadoop with .tar > > [gpadmin@gpmaster hawq_rpm_packages]$ which hadoop > /opt/hadoop/hadoop-2.9.0/bin/hadoop > [gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME > /opt/hadoop/hadoop-2.9.0 > How to let rpm know my Hadoop had installed. > > btw: > The rpms builded Centos7 and Centos6 ? > (el7=Centos7 el6=Centos6) > If so, It is in disorder. > [root@gpmaster hawq_rpm_packages]# ll > total 91304 > -rw-r--r--. 1 root root 84103760 Jun 23 01:54 > apache-hawq-2.2.0.0-el7.x86_64.rpm > -rw-r--r--. 1 root root 8892454 Jun 23 01:54 > apache-tomcat-7.0.62-el6.noarch.rpm > -rw-r--r--. 1 root root 5668 Jun 23 01:54 pxf-3.2.1.0-1.el6.noarch.rpm > -rw-r--r--. 1 root root33188 Jun 23 01:54 > pxf-hbase-3.2.1.0-1.el6.noarch.rpm > -rw-r--r--. 1 root root57270 Jun 23 01:54 > pxf-hdfs-3.2.1.0-1.el6.noarch.rpm > -rw-r--r--. 1 root root74971 Jun 23 01:54 > pxf-hive-3.2.1.0-1.el6.noarch.rpm > -rw-r--r--. 1 root root30847 Jun 23 01:54 > pxf-jdbc-3.2.1.0-1.el6.noarch.rpm > -rw-r--r--. 1 root root24833 Jun 23 01:54 > pxf-json-3.2.1.0-1.el6.noarch.rpm > -rw-r--r--. 1 root root 246454 Jun 23 01:54 > pxf-service-3.2.1.0-1.el6.noarch.rpm -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HAWQ-1568) install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro?
xinzhang created HAWQ-1568: -- Summary: install " pxf-hdfs-3.2.1.0-1.el6.noarch.rpm" dependencies pro? Key: HAWQ-1568 URL: https://issues.apache.org/jira/browse/HAWQ-1568 Project: Apache HAWQ Issue Type: Bug Reporter: xinzhang Assignee: Radar Lei Hi . I install hawq with rpm from 2.2.0 (apache-hawq-2.2.0.0-el7.x86_64.rpm) But when I install other rpm (like pxf-hdfs-3.2.1.0-1.el6.noarch.rpm) [gpadmin@gpmaster hawq_rpm_packages]$ rpm -ivh pxf-hdfs-3.2.1.0-1.el6.noarch.rpm error: Failed dependencies: pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch I install hadoop with .tar [gpadmin@gpmaster hawq_rpm_packages]$ which hadoop /opt/hadoop/hadoop-2.9.0/bin/hadoop [gpadmin@gpmaster hawq_rpm_packages]$ echo $HADOOP_HOME /opt/hadoop/hadoop-2.9.0 How to let rpm know my Hadoop had installed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HAWQ-1561) build faild on centos 6.8 bzip2
[ https://issues.apache.org/jira/browse/HAWQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279795#comment-16279795 ] xinzhang commented on HAWQ-1561: Ye .I will try what u suggest. > build faild on centos 6.8 bzip2 > --- > > Key: HAWQ-1561 > URL: https://issues.apache.org/jira/browse/HAWQ-1561 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: xinzhang >Assignee: Radar Lei > > Hi. My env is CentOS release 6.8 . > env: > # bzip2 --version > bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010. > fail log: >... > checking for library containing BZ2_bzDecompress... no > configure: error: library 'bzip2' is required. > 'bzip2' is used for table compression. Check config.log for details. > It is possible the compiler isn't looking in the proper directory. > q: > CENTOS 6.X use bzip1.0.5 as default . The dependence libs are the biggest > pros. >What should I to do ? bzip2 1.0.6 had installed . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HAWQ-1561) build faild on centos 6.8 bzip2
[
https://issues.apache.org/jira/browse/HAWQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276809#comment-16276809
]
xinzhang commented on HAWQ-1561:
{panel:title=My title}
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by HAWQ configure 8.2.15, which was
generated by GNU Autoconf 2.69. Invocation command line was
$ ./configure
## - ##
## Platform. ##
## - ##
hostname = node3
uname -m = x86_64
uname -r = 2.6.32-642.el6.x86_64
uname -s = Linux
uname -v = #1 SMP Tue May 10 17:27:01 UTC 2016
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = x86_64
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /opt/rh/devtoolset-2/root/usr//bin
PATH: /opt/oozie/oozie-4.3.0/bin
PATH: /opt/bazel/bazel-0.6.1/output
PATH: /opt/scala/scala-bin/bin
PATH: /opt/idea/idea-bin/bin
PATH: /opt/netdata/netdata-bin/netdata/usr/sbin
PATH: /opt/streamcql/stream-cql-bin/bin
PATH: /opt/storm/storm-bin/bin
PATH: /opt/gradle/gradle-bin/bin
PATH: /opt/kafka/kafka-bin/bin
PATH: /opt/elasticsearch/elasticsearch-bin/bin
PATH: /opt/maven/maven-bin/bin
PATH: /opt/nodejs/node-bin/bin
PATH: /opt/eagle/eagle-bin/bin
PATH: /opt/hive/hive-falcon-bin/bin
PATH: /opt/zookeeper/zookeeper-bin/bin
PATH: /opt/sbt/sbt/bin
PATH: /opt/neo4j/neo4j-community-3.2.1/bin
PATH: /usr/java/jdk1.8.0_66/bin
PATH: /opt/oozie/oozie-4.3.0
PATH: /root/anaconda2/bin
PATH: /opt/rh/devtoolset-2/root/usr//bin
PATH: /opt/oozie/oozie-4.3.0/bin
PATH: /opt/bazel/bazel-0.6.1/output
PATH: /opt/scala/scala-bin/bin
PATH: /opt/idea/idea-bin/bin
PATH: /opt/netdata/netdata-bin/netdata/usr/sbin
PATH: /opt/streamcql/stream-cql-bin/bin
PATH: /opt/storm/storm-bin/bin
PATH: /opt/gradle/gradle-bin/bin
PATH: /opt/kafka/kafka-bin/bin
PATH: /opt/elasticsearch/elasticsearch-bin/bin
PATH: /opt/maven/maven-bin/bin
PATH: /opt/nodejs/node-bin/bin
PATH: /opt/eagle/eagle-bin/bin
PATH: /opt/hive/hive-falcon-bin/bin
PATH: /opt/zookeeper/zookeeper-bin/bin
PATH: /opt/sbt/sbt/bin
PATH: /opt/neo4j/neo4j-community-3.2.1/bin
PATH: /usr/java/jdk1.8.0_66/bin
PATH: /usr/lib64/qt-3.3/bin
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /sbin
PATH: /bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /opt/kafka/kafka-eagle/bin
PATH: /opt/elasticsearch/logstash-bin/bin
PATH: /opt/angel/angel-bin/bin
PATH: /root/bin
PATH: /opt/kafka/kafka-eagle/bin
PATH: /opt/elasticsearch/logstash-bin/bin
PATH: /opt/angel/angel-bin/bin
## --- ##
## Core tests. ##
## --- ##
configure:2936: checking build system type
configure:2950: result: x86_64-unknown-linux-gnu
configure:2970: checking host system type
configure:2983: result: x86_64-unknown-linux-gnu
configure:3005: checking which template to use
configure:3088: result: linux
configure:3216: checking whether to build with 64-bit integer date/time support
configure:3246: result: yes
configure:3253: checking whether NLS is wanted
configure:3286: result: no
configure:3294: checking for default port number
configure:3320: result: 5432
configure:3809: checking for gcc
configure:3825: found /opt/rh/devtoolset-2/root/usr//bin/gcc
configure:3836: result: gcc
configure:3867: checking for C compiler version
configure:3876: gcc --version >&5
gcc (GCC) 4.8.2 20140120 (Red Hat 4.8.2-15)
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:3887: $? = 0
configure:3876: gcc -v >&5
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/opt/rh/devtoolset-2/root/usr
--mandir=/opt/rh/devtoolset-2/root/usr/share/man
--infodir=/opt/rh/devtoolset-2/root/usr/share/info
--with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap
--enable-shared --enable-threads=posix --enable-checking=release
--with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions
--enable-gnu-unique-object --enable-linker-build-id
--enable-languages=c,c++,fortran,lto --enable-plugin
--with-linker-hash-style=gnu --enable-initfini-array --disable-libgcj
--with-isl=/dev/shm/home/centos/rpm/BUILD/gcc-4.8.2-20140120/obj-x86_64-redhat-linux/isl-install
--with-cloog=/dev/shm/home/centos/rpm/BUILD/gcc-4.8.2-20140120/obj-x86_64-redhat-linux/cloog-install
--with-mpc=/dev/shm/home/centos/rpm/BUILD/gcc-4.8.2-20140120/obj-x86_64-redhat-linux/mpc-install
--with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux
Thread model: posix
gcc version 4.8.2 20140120 (Red Hat 4.8.2-15) (GCC)
configure:3887: $? = 0
configure:3876:
[jira] [Comment Edited] (HAWQ-1561) build faild on centos 6.8 bzip2
[ https://issues.apache.org/jira/browse/HAWQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276598#comment-16276598 ] xinzhang edited comment on HAWQ-1561 at 12/4/17 10:38 AM: -- Does your bzip2's version (1.0.5) ? - [root@node3 incubator-hawq]# bzip2 --version bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010. . [root@node3 incubator-hawq]# rpm -qa |grep bzip2 bzip2-devel-1.0.6-1.bentuos8.0.x86_64 bzip2-libs-1.0.5-7.el6_0.x86_64 bzip2-1.0.5-7.el6_0.x86_64 (I use yum install 1.0.5 with /usr/bin/bzip2 and I install 1.0.6 with source tar in/usr/local/bin/bzip2, I install 1.0.6 to /usr/local) [root@node3 incubator-hawq]# which bzip2 /usr/local/bin/bzip2 [root@node3 incubator-hawq]# whereis bzip2 bzip2: /usr/bin/bzip2 /usr/local/bin/bzip2 /usr/man/man1/bzip2.1 /usr/share/man/man1/bzip2.1.gz - configure log: [root@node3 incubator-hawq]# ./configure checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking which template to use... linux checking whether to build with 64-bit integer date/time support... yes checking whether NLS is wanted... no checking for default port number... 5432 checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for __get_cpuid... yes checking for __cpuid... no checking for _mm_crc32_u8 and _mm_crc32_u32 with CFLAGS=... no checking for _mm_crc32_u8 and _mm_crc32_u32 with CFLAGS=-msse4.2... yes checking which CRC-32C implementation to use... SSE 4.2 with runtime check checking if gcc supports -Wendif-labels... yes checking if gcc supports -Wformat-security... yes checking if gcc supports -fno-strict-aliasing... yes checking if gcc supports -fwrapv... yes checking if gcc supports -fno-aggressive-loop-optimizations... yes checking whether the C compiler still works... yes checking how to run the C preprocessor... gcc -E checking whether to build with snmp... no checking whether to build with gphdfs...no checking whether to build with email...no checking allow thread-safe client libraries... yes checking whether to build with Tcl... no checking whether to build Perl modules... no checking whether to build Python modules... no checking whether to build Java modules... no checking whether to build R modules... no checking whether to build pgcrypto modules... no checking whether to build with GSSAPI support... no checking whether to build with Kerberos 5 support... no checking whether to build with PAM support... no checking whether to build with LDAP support... no checking whether to build with Bonjour support... no checking whether to build with OpenSSL support... no checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E configure: using CPPFLAGS= -D_GNU_SOURCE configure: using LDFLAGS= checking for ld used by GCC... /opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/ld checking if the linker (/opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/ld) is GNU ld... yes checking for ranlib... ranlib checking for strip... strip checking whether it is possible to strip libraries... yes checking for ar... ar checking for tar... /bin/tar checking whether ln -s works... yes checking for gawk... gawk checking for a thread-safe mkdir -p... /bin/mkdir -p checking for bison... /usr/bin/bison configure: using bison (GNU Bison) 3.0.4 checking for flex... /usr/bin/flex configure: using flex 2.5.35 checking for mvn... /opt/maven/maven-bin/bin/mvn configure: using Apache Maven 3.3.9 checking for gperf... /usr/bin/gperf checking for perl... /usr/bin/perl configure: using perl 5.10.1 checking for Perl module JSON... yes checking for python... /root/anaconda2/bin/python checking for main in -lm... yes checking for library containing setproctitle... no checking for library containing dlopen... -ldl checking for library containing socket... none required checking for library containing shl_load... no checking for library containing getopt_long... none required checking for library containing crypt... -lcrypt checking for library containing fdatasync... none required checking for library containing gethostbyname_r... none required checking for library containing shmget... none required checking for library containing readline... -lreadline checking for inflate in -lz... yes checking for clock_gettime in -lrt... yes checking for curl-config... /root/anaconda2/bin/curl-config checking for curl >=
[jira] [Commented] (HAWQ-1561) build faild on centos 6.8 bzip2
[ https://issues.apache.org/jira/browse/HAWQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276598#comment-16276598 ] xinzhang commented on HAWQ-1561: Does your bzip2's version (1.0.5) ? log: [root@node3 incubator-hawq]# ./configure checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking which template to use... linux checking whether to build with 64-bit integer date/time support... yes checking whether NLS is wanted... no checking for default port number... 5432 checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for __get_cpuid... yes checking for __cpuid... no checking for _mm_crc32_u8 and _mm_crc32_u32 with CFLAGS=... no checking for _mm_crc32_u8 and _mm_crc32_u32 with CFLAGS=-msse4.2... yes checking which CRC-32C implementation to use... SSE 4.2 with runtime check checking if gcc supports -Wendif-labels... yes checking if gcc supports -Wformat-security... yes checking if gcc supports -fno-strict-aliasing... yes checking if gcc supports -fwrapv... yes checking if gcc supports -fno-aggressive-loop-optimizations... yes checking whether the C compiler still works... yes checking how to run the C preprocessor... gcc -E checking whether to build with snmp... no checking whether to build with gphdfs...no checking whether to build with email...no checking allow thread-safe client libraries... yes checking whether to build with Tcl... no checking whether to build Perl modules... no checking whether to build Python modules... no checking whether to build Java modules... no checking whether to build R modules... no checking whether to build pgcrypto modules... no checking whether to build with GSSAPI support... no checking whether to build with Kerberos 5 support... no checking whether to build with PAM support... no checking whether to build with LDAP support... no checking whether to build with Bonjour support... no checking whether to build with OpenSSL support... no checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E configure: using CPPFLAGS= -D_GNU_SOURCE configure: using LDFLAGS= checking for ld used by GCC... /opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/ld checking if the linker (/opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/ld) is GNU ld... yes checking for ranlib... ranlib checking for strip... strip checking whether it is possible to strip libraries... yes checking for ar... ar checking for tar... /bin/tar checking whether ln -s works... yes checking for gawk... gawk checking for a thread-safe mkdir -p... /bin/mkdir -p checking for bison... /usr/bin/bison configure: using bison (GNU Bison) 3.0.4 checking for flex... /usr/bin/flex configure: using flex 2.5.35 checking for mvn... /opt/maven/maven-bin/bin/mvn configure: using Apache Maven 3.3.9 checking for gperf... /usr/bin/gperf checking for perl... /usr/bin/perl configure: using perl 5.10.1 checking for Perl module JSON... yes checking for python... /root/anaconda2/bin/python checking for main in -lm... yes checking for library containing setproctitle... no checking for library containing dlopen... -ldl checking for library containing socket... none required checking for library containing shl_load... no checking for library containing getopt_long... none required checking for library containing crypt... -lcrypt checking for library containing fdatasync... none required checking for library containing gethostbyname_r... none required checking for library containing shmget... none required checking for library containing readline... -lreadline checking for inflate in -lz... yes checking for clock_gettime in -lrt... yes checking for curl-config... /root/anaconda2/bin/curl-config checking for curl >= 7.0.0... yes checking CURL_CFLAGS... -I/root/anaconda2/include checking CURL_LIBS... -L/root/anaconda2/lib -lcurl checking for ANSI C header files... no checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking bzlib.h usability... yes checking bzlib.h presence... yes checking for bzlib.h... yes checking for library containing BZ2_bzDecompress... no configure: error: library 'bzip2' is required. 'bzip2' is used for table compression. Check config.log for details. It is possible the compiler isn't looking in the proper directory. [root@node3 incubator-hawq]#
[jira] [Commented] (HAWQ-1561) build faild on centos 6.8 bzip2
[ https://issues.apache.org/jira/browse/HAWQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276546#comment-16276546 ] xinzhang commented on HAWQ-1561: Ye. I noticed it . Centos6.X use bzip2-devel (1.0.5) I could not find any rpm(1.0.6) with google. https://rpmfind.net/linux/rpm2html/search.php?query=bzip2-devel I tried use 1.0.5 , it is incorrect. Could u apply any relate links? > build faild on centos 6.8 bzip2 > --- > > Key: HAWQ-1561 > URL: https://issues.apache.org/jira/browse/HAWQ-1561 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: xinzhang >Assignee: Radar Lei > > Hi. My env is CentOS release 6.8 . > env: > # bzip2 --version > bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010. > fail log: >... > checking for library containing BZ2_bzDecompress... no > configure: error: library 'bzip2' is required. > 'bzip2' is used for table compression. Check config.log for details. > It is possible the compiler isn't looking in the proper directory. > q: > CENTOS 6.X use bzip1.0.5 as default . The dependence libs are the biggest > pros. >What should I to do ? bzip2 1.0.6 had installed . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HAWQ-1561) build faild on centos 6.8 bzip2
xinzhang created HAWQ-1561: -- Summary: build faild on centos 6.8 bzip2 Key: HAWQ-1561 URL: https://issues.apache.org/jira/browse/HAWQ-1561 Project: Apache HAWQ Issue Type: Bug Components: Build Reporter: xinzhang Assignee: Radar Lei Hi. My env is CentOS release 6.8 . env: # bzip2 --version bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010. fail log: ... checking for library containing BZ2_bzDecompress... no configure: error: library 'bzip2' is required. 'bzip2' is used for table compression. Check config.log for details. It is possible the compiler isn't looking in the proper directory. q: CENTOS 6.X use bzip1.0.5 as default . The dependence libs are the biggest pros. What should I to do ? bzip2 1.0.6 had installed . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HAWQ-1561) build faild on centos 6.8 bzip2
[ https://issues.apache.org/jira/browse/HAWQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xinzhang updated HAWQ-1561: --- Description: Hi. My env is CentOS release 6.8 . env: # bzip2 --version bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010. fail log: ... checking for library containing BZ2_bzDecompress... no configure: error: library 'bzip2' is required. 'bzip2' is used for table compression. Check config.log for details. It is possible the compiler isn't looking in the proper directory. q: CENTOS 6.X use bzip1.0.5 as default . The dependence libs are the biggest pros. What should I to do ? bzip2 1.0.6 had installed . was: Hi. My env is CentOS release 6.8 . env: # bzip2 --version bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010. fail log: ... checking for library containing BZ2_bzDecompress... no configure: error: library 'bzip2' is required. 'bzip2' is used for table compression. Check config.log for details. It is possible the compiler isn't looking in the proper directory. q: CENTOS 6.X use bzip1.0.5 as default . The dependence libs are the biggest pros. What should I to do ? bzip2 1.0.6 had installed . > build faild on centos 6.8 bzip2 > --- > > Key: HAWQ-1561 > URL: https://issues.apache.org/jira/browse/HAWQ-1561 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: xinzhang >Assignee: Radar Lei > > Hi. My env is CentOS release 6.8 . > env: > # bzip2 --version > bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010. > fail log: >... > checking for library containing BZ2_bzDecompress... no > configure: error: library 'bzip2' is required. > 'bzip2' is used for table compression. Check config.log for details. > It is possible the compiler isn't looking in the proper directory. > q: > CENTOS 6.X use bzip1.0.5 as default . The dependence libs are the biggest > pros. >What should I to do ? bzip2 1.0.6 had installed . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
