Hi Chris, According to my attempt, your situation is not reproducible. Could you check the binary again? You can download and extract the tarball file again.
Best regards, Hyunsik On Fri, Oct 24, 2014 at 7:39 AM, Christian Schwabe <[email protected]> wrote: > > Hello guys > > I was very happy about it when I got the message that was Tajo 0.9.0 > released. > For that reason I hopefully try to test it on Ubuntu 14.04.1 LTS > But of course, how could it be otherwise, I get an ZipException while > starting a single worker on the "slave" machine. > I've attached the log and I hope you have another tip that I have not > already tried. > > So what have I done so far: > -Pulled the latest github repository recompiled with >>> $ mvn clean install -DskipTests -Pdist -Dtar -Dhadoop.version=2.5.1 > > These binaries run successfully on my Macbook Pro > > Now I copied the same folder by customizing the ./conf/tajo-site.xml and > ./conf/tajo-site.xml to the second "slave" machine. But in this case I get a > ZipException. You can see this in the attached log. > > Because I had the presumption of the load dependencies for the Macbooks at > compile time and could cause problems, I have also re-cloned the > gitrepository on the Ubuntu system and recompiled it again. Unfortunately, > with the same result. The tajo-core-0.9.0.jar could not be opened. In the > next step, I have now downloaded the Binaries from tajo.apache.org, again > with the same error. > > I've tested it with the following Java-Versions on Ubuntu: > > java version "1.7.0_65" > OpenJDK Runtime Environment (IcedTea 2.5.2) (7u65-2.5.2-3~14.04) > OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) > > AND > > java version "1.7.0_72" > Java(TM) SE Runtime Environment (build 1.7.0_72-b14) > Java HotSpot(TM) 64-Bit Server VM (build 24.72-b04, mixed mode) > > > Do you have any ideas what could cause the error here or can reproduce this > even? > > > P.S.: I know that the TajoMaster not running at the time of start of the > TajoWorker on the "slave" machine. This error is to be ignored, because I > just wanted to test whether the worker starts. > > Best regards, > Chris >
