Skip to main content
Solved

Crash when batch deploy display child killed: segmentation violation

  • Jul 19, 2017 4:24 AM UTC
  • 2 replies
  • 79 views

When I use batch deploy translate some files, then just success one file, and display these message on last lines, and fme version 2015.1.1.0?20150715 - Build15515-win32?.

Creating reader for format: CSV (Comma Separated Value)

Trying to find a DYNAMIC plugin for reader named `CSV'

FME API version of module 'CSV' matches current internal version (3.7 20150407)

child killed: segmentation violation

FME encountered an error. Please contact

Best answer by davideagle

Batch deploy can be a bit of a dark art, my suggestion would be to consider batch processing using the WorkspaceRunner and a Master\\Slave workspace approach as it is more configurable with the standard FME Workbench interface. You can also configure 1 log file per process by publishing the log file parameter.

View original
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

davideagle
Contributor
Forum|alt.badge.img+21
  • davideagleContributor
  • Contributor
  • Best Answer
  • Jul 19, 2017 8:38 AM UTC

Batch deploy can be a bit of a dark art, my suggestion would be to consider batch processing using the WorkspaceRunner and a Master\\Slave workspace approach as it is more configurable with the standard FME Workbench interface. You can also configure 1 log file per process by publishing the log file parameter.

  • ningfc
  • Author
  • Jul 19, 2017 10:05 AM UTC

Batch deploy can be a bit of a dark art, my suggestion would be to consider batch processing using the WorkspaceRunner and a Master\\Slave workspace approach as it is more configurable with the standard FME Workbench interface. You can also configure 1 log file per process by publishing the log file parameter.

Thanks for your replay. I just change old version translators to new, and then batch deploy can worked, so I guess maybe that's the reason.

Community Stats

32,990
Posts
125,025
Replies
41,911
Members
Terms & ConditionsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.