Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Process exited with code 132 #330

Closed
mxcoldhit opened this issue Nov 16, 2017 · 10 comments
Closed

Process exited with code 132 #330

mxcoldhit opened this issue Nov 16, 2017 · 10 comments
Labels

Comments

@mxcoldhit
Copy link

mxcoldhit commented Nov 16, 2017

How did you install WebODM? (Docker, natively, ...)?
Docker

What's your browser and operating system? (Copy/paste the output of https://www.whatismybrowser.com/)
Chrome 61 on Windows 10

What is the problem?
I get the following error after starting my first task using the web interface. Using 45 images
/code/run.sh: line 6: 24 Illegal instruction python $RUNPATH/run.py "$@"

What should be the expected behavior?

How can we reproduce this? (What steps did you do to trigger the problem? What parameters are you using for processing? If possible please include a copy of your dataset uploaded on Google Drive or Dropbox. Be detailed)
I am using the default options. Just tried to process my first set if images.

@pierotofy
Copy link
Member

Hi @mxcoldhit,

It looks like there is some information missing from your ticket that will be needed in order to diagnose and fix the problem at hand. Please take a look at the Issue Template, which will tell you exactly what your ticket has to contain in order to be processable.

I'm marking this one now as needing some more information. Please understand that if you do not provide that information within the next week (until 2017-11-23 15:50) I'll close this ticket so it doesn't clutter the bug tracker.

Best regards,
~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being.

@pierotofy
Copy link
Member

Hi @mxcoldhit, you are probably using an older CPU. The docker setup needs CPUs with 64-bit extensions, MMX, SSE, SSE2, SSE3 and SSSE3 instruction set support or higher.

You could rebuild the OpenDroneMap and node-OpenDroneMap docker images from sources and then use that instance of node-OpenDroneMap to process a task.

@julianpalladino
Copy link

Hi @pierotofy, with rebuilding you mean running the following?

bash webodm.sh rebuild

I'm having the same problem but rebuilding is not solving it. Maybe it's necessary for me to manually build the docker images?

Is this because opendronemap uses libraries with SSE4.1 instructions? I have an AMD Phenom(tm) II X6 1075T CPU which has SSE4a but not SSE4.1. Is there a way to make it work?

@pierotofy
Copy link
Member

pierotofy commented Jul 18, 2018

Hey @julianpalladino ✋ , no, that will only rebuild the WebODM containers.

You need to rebuild ODM (https://github.com/OpenDroneMap/OpenDroneMap), then node-ODM (https://github.com/OpenDroneMap/node-OpenDroneMap), then finally you can use the node-ODM image with WebODM (no need to recompile WebODM's containers). Usually a:

docker build -t <appropriate tag name> .

Will do the trick for each repository. Note that the Node-ODM docker build references opendronemap/opendronemap, so you might have to change the Dockerfile slightly.

@julianpalladino
Copy link

Hi again @pierotofy , thank you very much for your help!
I tried building OpenDroneMap and node-OpenDroneMap natively. However I still have the same problem (code 132 / illegal instruction, due to old CPU), exactly as this issue.

Is it a bug? Is there a way to bypass that part of the program? I wouldn't mind to lose some functionality, as long as I can use the rest of the program

@julianpalladino
Copy link

Hi again. We managed to fix this, apparently some libraries used by mvs-texturing were compiling with a flag that specified sse4 to be used. Therefore, the solution that worked for us was: installing ODM, node-ODM and WebODM natively, and recompiling those libraries without the flag.

@pierotofy
Copy link
Member

Hey @julianpalladino this is a great find! Would you mind sharing more about the process you followed to remove the flag? It would be great to document the fix for other users (or even open a PR).

@fragofer
Copy link

fragofer commented Aug 8, 2018

Hi @pierotofy, we're working with @julianpalladino on this issue.
The problem wasn't in ODM, node-ODM nor WebODM so rebuilding these projects led us to the same error. After long hours of debugging we found that the problem was/is in a related project MVE (used by mvs-texturing): https://github.com/nmoehrle/mve

In particular, in the file:
https://github.com/simonfuhrmann/mve/blob/master/Makefile.inc
They added the flag -sse4 which is not supported by old AMD processors (ours is an AMD Phenom II X6 1090T). So, we removed that flag and now everything is working :-)

I think that the best thing to do is to transform MVE in a CMakeList based project, so for now a good fix would be to change:
https://github.com/OpenDroneMap/mvs-texturing/blob/master/elibs/CMakeLists.txt
and point to forked projects that can be controlled by the ODM team, and also try to avoid cloning external libraries from master branches to gain stability in the building process.

Thanks!
Francisco

@franchyze923
Copy link

I'm having a similar issue with AMD Phenom(tm) II X6 1090T CPU. I just started working with ODM. Can this CPU be used? I'm unfamiliar with how to recompile, but will investigate if it is possible to get this CPU working.

@pierotofy
Copy link
Member

Could we move this conversation over to the forum at https://community.opendronemap.org? 🙏 The forum is the right place to ask questions (we try to keep the GitHub issue tracker for feature requests and bugs only). Thank you! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants