Skip to main content
Question

Make it easier not to mix different python versions (2.7 - 3.6) on FME Server

  • March 21, 2018
  • 3 replies
  • 23 views
sigtill
Supporter
Forum|alt.badge.img+25

Simplified story: One engine can only use one specific python version. So if you have 2 workspaces running - with different versions of python, they will fail giving this error:

The Workspace requires Python version 3.6, but Python version 2.7 is already loaded Workspace requiring Python 3.6 is requested to run on an FME Engine configured to use a Python 2.7 interpreter. FME cannot continue given the Python version mismatch
A fatal error has occurred. Check the logfile above for details

GUI-suggestion on FME Server:

0684Q00000ArCLbQAN.png

Which will result in a warning when publishing workspaces to that server:

0684Q00000ArC57QAF.png

 

The real SigTill
    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.

    3 replies

    david_r
    Celebrity
    • david_rCelebrity
    • 8394 replies
    • March 21, 2018

    That's a great improvement.

    Alternatively, I would prefer the Engine to just automatically restart and get on with it when encountering a different Python version, rather than raising a fatal error.

    J
    Forum|alt.badge.img+2

    That's a great improvement.

    Alternatively, I would prefer the Engine to just automatically restart and get on with it when encountering a different Python version, rather than raising a fatal error.

    You can set this in the config files as a workaround to restart after every one, but it'd be great if it detected this and then restarted itself.

     

     

    sigtill
    Supporter
    Forum|alt.badge.img+25
    • sigtillSupporter
    • Author
    • Supporter
    • 956 replies
    • April 30, 2018
    You can set this in the config files as a workaround to restart after every one, but it'd be great if it detected this and then restarted itself.

     

     

    This workaround does not work when a workspace failes within a Custom Transformer in Parallell mode (as it is the fmeworker.exe failing - not fme.exe) - so it will not restart these processes.

     

    The real SigTill

    Community Stats

    32,087
    Posts
    121,850
    Replies
    39,729
    Members

    Latest FME

    Terms & ConditionsCookie settingsAccessibility 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.