jit compiler fails for assemble in EC2 ubuntu instance

Question

Hello, I'm trying to run my code on an Amazon EC2 instance using a docker image. I am running the same version of ubuntu and same docker image on my laptop where it runs fine, but on the EC2 instance, I get the following error in assemble.

Traceback (most recent call last):
  File "EM3DORASPtiming.py", line 108, in <module>
    A, b = assemble_system(a, L, bc)
  File "/usr/local/lib/python2.7/dist-packages/dolfin/fem/assembling.py", line 351, in assemble_system
    b_dolfin_form = _create_dolfin_form(b_form, form_compiler_parameters)
  File "/usr/local/lib/python2.7/dist-packages/dolfin/fem/assembling.py", line 67, in _create_dolfin_form
    function_spaces=function_spaces)
  File "/usr/local/lib/python2.7/dist-packages/dolfin/fem/form.py", line 89, in __init__
    mpi_comm=mesh.mpi_comm())
  File "/usr/local/lib/python2.7/dist-packages/dolfin/compilemodules/jit.py", line 68, in mpi_jit
    return local_jit(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/dolfin/compilemodules/jit.py", line 133, in jit
    "ffc.jit failed with message:\n%s" % (tb_text,))
  File "/usr/local/lib/python2.7/dist-packages/dolfin/cpp/common.py", line 2915, in dolfin_error
    return _common.dolfin_error(location, task, reason)
RuntimeError: 

*** -------------------------------------------------------------------------
*** DOLFIN encountered an error. If you are not able to resolve this issue
*** using the information listed below, you can ask for help at
***
***     fenics-support@googlegroups.com
***
*** Remember to include the error message listed below and, if possible,
*** include a *minimal* running example to reproduce the error.
***
*** -------------------------------------------------------------------------
*** Error:   Unable to perform just-in-time compilation of form.
*** Reason:  ffc.jit failed with message:
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/dolfin/compilemodules/jit.py", line 128, in jit
    result = ffc.jit(ufl_object, parameters=p)
  File "/usr/local/lib/python2.7/dist-packages/ffc/jitcompiler.py", line 198, in jit
    module = jit_build(ufl_object, module_name, parameters)
  File "/usr/local/lib/python2.7/dist-packages/ffc/jitcompiler.py", line 120, in jit_build
    generate=jit_generate)
  File "/usr/local/lib/python2.7/dist-packages/dijitso/jit.py", line 160, in jit
    header, source, dependencies = generate(jitable, name, signature, params["generator"])
  File "/usr/local/lib/python2.7/dist-packages/ffc/jitcompiler.py", line 76, in jit_generate
    dep_module_name = jit(dep, parameters, indirect=True)
  File "/usr/local/lib/python2.7/dist-packages/ffc/jitcompiler.py", line 204, in jit
    raise FFCJitError("A directory with files to reproduce the jit build failure has been created.")
FFCJitError: A directory with files to reproduce the jit build failure has been created.
.
*** Where:   This error was encountered inside jit.py.
*** Process: 0
*** 
*** DOLFIN version: 2016.2.0
*** Git changeset:  0f003bc07ee5fd583fb956245016d5972b80fea1
*** -------------------------------------------------------------------------

Aborted (core dumped)

Also, I can run demo_poisson.py just fine in the EC2 instance. Any help would be greatly appreciated.

Comments

Which docker image do you use? Are you running the exact same commands for starting the docker container on your computer and on the EC2 instance?

---

I am using the same docker image for both by calling

docker run -ti -v $(pwd):/home/fenics/shared quay.io/fenicsproject/stable

I have verified that the python version and gcc version are the same by opening a python session in each terminal

---

Make sure you have the same image on both by running

docker pull quay.io/fenicsproject/stable

Then run this inside the containers on both of them:

dijitso clean
instant-clean

Then run your script again. Is it still difference between your laptop and the EC2 instance? If one or both fails, then look in the folder that is created in the directory you ran the script in. There you will find log files that should give you a clue about what the problem is.