search

hltfbk / Excitement-Open-Platform

Excitement Open Platform for Recognizing Textual Entailments
http://hltfbk.github.io/Excitement-Open-Platform/
86 stars 74 forks source link

TreeTagger fails on specific hardwares #41

Closed gilnoh closed 11 years ago

gilnoh commented 11 years ago

DKPro TreeTagger fails on specific hardwares (Xeon CPUs, on linux). I am suspecting that DKPro fails to map correct binary (32bit) in specific hardwares.

I am still collecting more data (I am testing only on various linux 32/64 bits). If you have other data (say, Windows), please let me know.

This bug is located within DKPro, so it might take some time to be fixed, but I will try to 1) locate the cause 2) report the issue 3) design a possible by-pass (if possible) 4) (finally, when fixed) update the TreeTagger DKPro Jar.

Again, this really may take some time. So for now, I would recommend that everyone uses 64bit OS. (OSX 64bit and Linux X86_64 seems to be unaffected by this).

gilnoh commented 11 years ago

Okay. I think I find one probable reason of this. It has nothing to do with HW, but to a system configuration.

DKPro needs to run an executable file in /tmp (or in the assigned system TMP directory). It copies the needed TreeTagger binary in tmp, and runs it there.

Some servers/unix computers prohibit this, for example, one of our institute server loads /tmp with "noexec". (The following is > mount report on such a server). /dev/sdc1 on /tmp type ext3 (rw,noexec)

So, in such a computer, no executable can be run from /tmp. Thus, DKPro copies the binary there, and tries to run it, but it can't run that… and simply fails.

I will iterate this problem to DKPro community, and try to find a possible work-around.

gilnoh commented 11 years ago

I reported this issue in DKPro issue tracker. They will (maybe) provide a fall back code.

Meanwhile, we have a work-around solution. If your maven fails on testing TreeTagger, do it like the followings.

java -Djava.io.tmpdir=. [the rest], or in maven mvn -Djava.io.tmpdir=. [build command]

This makes java to use "." (current directory) as temp directory.

So if you want to build, the command would be:
mvn -Djava.io.tmpdir=. package

This will pass all failed test, that is caused by "noexec" /tmp.

I will keep this issue opened for a while, to make sure this was indeed the cause of Roberto's problem.

gilnoh commented 11 years ago

On Roberto's case, the problem was caused by a different reason. It was caused by an older version of Linux Kernel, which is classified as 64bit, but can't support 64bit properly (?). Roberto expressed that this problem can be avoided on his side, by updating his system. So let's remind that TreeTagger can have a problem on 64bit systems with older Kernel...

Since we have two issues and two "word-arounds". I am closing this issue.