Having issues lately (segmentation fault?)

[uplanddog]

Below is the end of the log file. datasets that used to process with no issues now for some reason having issues.

my setup is webodm on a small machine with nodeodm on a more robust machine 128gb ram 128gb swap. odm version is 3.0.2. Thanks for help or suggestions.

/code/SuperBuild/install/bin/opensfm/bin/opensfm: line 12: 45156 Segmentation fault (core dumped) “$PYTHON” “$DIR”/opensfm_main.py “[email protected]”

===== Dumping Info for Geeks (developers need this to fix bugs) =====
Child returned 139
Traceback (most recent call last):
File “/code/stages/odm_app.py”, line 81, in execute
self.first_stage.run()
File “/code/opendm/types.py”, line 386, in run
self.next_stage.run(outputs)
File “/code/opendm/types.py”, line 386, in run
self.next_stage.run(outputs)
File “/code/opendm/types.py”, line 386, in run
self.next_stage.run(outputs)
File “/code/opendm/types.py”, line 365, in run
self.process(self.args, outputs)
File “/code/stages/run_opensfm.py”, line 35, in process
octx.feature_matching(self.rerun())
File “/code/opendm/osfm.py”, line 411, in feature_matching
self.match_features(rerun)
File “/code/opendm/osfm.py”, line 416, in match_features
self.run(‘match_features’)
File “/code/opendm/osfm.py”, line 34, in run
system.run(‘“%s” %s “%s”’ %
File “/code/opendm/system.py”, line 109, in run
raise SubprocessException(“Child returned {}”.format(retcode), retcode)
opendm.system.SubprocessException: Child returned 139

===== Done, human-readable information to follow… =====

[ERROR] Uh oh! Processing stopped because of strange values in the reconstruction. This is often a sign that the input data has some issues or the software cannot deal with it. Have you followed best practices for data acquisition? See Flying Tips — OpenDroneMap 3.0.2 documentation

[smathermather]

Interesting. An update to OpenSfM hit last week. When was your latest update?

[uplanddog]

Bit of a long story, but it appears after some troubleshooting the problem is related to this machine and not odm. Last week I installed a new mobo and more memory , changed to nodeodm from webodm and installed webodm on a box that runs 24/7. it is funny that last week I tested this set up with a 800 or so image dataset and it did just fine, but now having issues. Today it has failed in different stages on very small datasets, but those small datasets processed ok on the 24/7 webodm machine. ill continue to work on it. thanks for the reply.