Installation issues

[debadutta prusty]

Hi everyone,

For some reason, Moose is not functioning on my computer. It fails all tests mentioned on the installation page on the original website. Even the troubleshooting steps mentioned there do not do much in my case. The error messages that come up on doing 

"

cd ~/projects/moose/test

make -j 4

./run_tests -j 4

"

are the following:

Final Test Results:

--------------------------------------------------------------------------------------------------------------

relationship_managers/two_rm.evaluable_neighbors_distributed ................... [MESH_MODE!=DISTRIBUTED] SKIP

outputs/png.image_tests/wedge ............................................................ [LIBPNG!=TRUE] SKIP

outputs/png.image_tests/adv_diff_reaction ................................................ [LIBPNG!=TRUE] SKIP

outputs/png.image_tests/square_domain .................................................... [LIBPNG!=TRUE] SKIP

outputs/vtk.solution/diff_parallel_mesh ................................. [#6149, MESH_MODE!=DISTRIBUTED] SKIP

outputs/nemesis.nemesis_elemental_distributed .................................. [MESH_MODE!=DISTRIBUTED] SKIP

outputs/nemesis.nemesis_scalar_distributed ..................................... [MESH_MODE!=DISTRIBUTED] SKIP

outputs/format.tecplot_bin_test_override ............................................... [TECPLOT!=FALSE] SKIP

problems/eigen_problem/eigensolvers.no_slepc ............................................. [SLEPC!=FALSE] SKIP

vectorpostprocessors/work_balance.work_balance/distributed ..................... [MESH_MODE!=DISTRIBUTED] SKIP

nodalkernels/constant_rate.group/threaded .......................................... [skipped dependency] SKIP

constraints/equal_value_embedded_constraint.1D_3D_penalty .......................... [skipped dependency] SKIP

constraints/equal_value_embedded_constraint.2D_3D_kinematic ........................ [skipped dependency] SKIP

constraints/equal_value_embedded_constraint.2D_2D_kinematic ........................ [skipped dependency] SKIP

constraints/equal_value_embedded_constraint.2D_3D_penalty .......................... [skipped dependency] SKIP

constraints/equal_value_embedded_constraint.3D_3D_kinematic ........................ [skipped dependency] SKIP

constraints/equal_value_embedded_constraint.1D_2D_penalty .......................... [skipped dependency] SKIP

constraints/equal_value_embedded_constraint.1D_3D_kinematic ........................ [skipped dependency] SKIP

constraints/equal_value_embedded_constraint.2D_2D_penalty .......................... [skipped dependency] SKIP

constraints/equal_value_embedded_constraint.3D_3D_penalty .......................... [skipped dependency] SKIP

outputs/recover.part1_latest ....................................................... [skipped dependency] SKIP

outputs/recover.part2_latest ....................................................... [skipped dependency] SKIP

outputs/recover.part2 .............................................................. [skipped dependency] SKIP

outputs/intervals.common_time_step ................................................. [skipped dependency] SKIP

outputs/csv_final_and_latest.final_only ............................................ [skipped dependency] SKIP

outputs/csv_final_and_latest.no_link ............................................... [skipped dependency] SKIP

dirackernels/nonlinear_source.nonlinear_source ................................................ FAILED (CRASH)

dirackernels/function_dirac_source.function_dirac_source ...................................... FAILED (CRASH)

dirackernels/material_point_source.material_point_source_test ................................. FAILED (CRASH)

dirackernels/constant_point_source.dim/1D ..................................................... FAILED (CRASH)

dirackernels/aux_scalar_variable.test ......................................................... FAILED (CRASH)

dirackernels/front_tracking.test .............................................................. FAILED (CRASH)

dirackernels/point_caching.point_caching/basic ................................................ FAILED (CRASH)

dirackernels/multiplicity.multiplicity ........................................................ FAILED (CRASH)

nodalkernels/penalty_dirichlet.test ........................................................... FAILED (CRASH)

nodalkernels/high_order_time_integration.test ................................................. FAILED (CRASH)

nodalkernels/scaling.scaling ................................................ FAILED (EXPECTED OUTPUT MISSING)

nodalkernels/jac_test.test .................................................................... FAILED (CRASH)

minimal_app.minimal ......................................................... FAILED (EXPECTED OUTPUT MISSING)

nodalkernels/constraint_enforcement.lower_bound/exo ........................................... FAILED (CRASH)

nodalkernels/constant_rate.group/test ......................................................... FAILED (CRASH)

constraints/tied_value_constraint.test ........................................................ FAILED (CRASH)

constraints/equal_value_embedded_constraint.1D_2D_kinematic ................................... FAILED (CRASH)

constraints/nodal_constraint.test ............................................................. FAILED (CRASH)

constraints/equal_value_boundary_constraint.test .............................................. FAILED (CRASH)

constraints/coupled_tied_value_constraint.test ................................................ FAILED (CRASH)

relationship_managers/default_ghosting.test ................................. FAILED (EXPECTED OUTPUT MISSING)

relationship_managers/check_coupling_functor.run .............................................. FAILED (CRASH)

outputs/output_interface.group/indicators ..................................................... FAILED (CRASH)

outputs/xda_xdr.both_xda_and_xdr .............................................................. FAILED (CRASH)

relationship_managers/two_rm.evaluable_neighbors_replicated ...................... [min_cpus=3] FAILED (CRASH)

outputs/xda.group/xda ......................................................................... FAILED (CRASH)

outputs/tecplot.test .......................................................................... FAILED (CRASH)

outputs/recover.part1 ......................................................................... FAILED (CRASH)

outputs/intervals.time_step ................................................................... FAILED (CRASH)

outputs/perf_graph.test ..................................................... FAILED (EXPECTED OUTPUT MISSING)

outputs/perf_graph/multi_app.perf_with_multi ................................ FAILED (EXPECTED OUTPUT MISSING)

outputs/displacement.test ..................................................................... FAILED (CRASH)

outputs/output_on.postprocessor ............................................. FAILED (EXPECTED OUTPUT MISSING)

outputs/append_date.test ...................................................................... FAILED (CRASH)

outputs/variables.test ........................................................................ FAILED (CRASH)

outputs/displaced.use_displaced ............................................................... FAILED (CRASH)

outputs/csv.steady ............................................................................ FAILED (CRASH)

outputs/hide_vector_pp.test ................................................................... FAILED (CRASH)

outputs/vtk.files/serial ...................................................................... FAILED (CRASH)

outputs/postprocessor.limit ................................................................... FAILED (CRASH)

outputs/common.exodus ......................................................................... FAILED (CRASH)

outputs/subdir_output.test .................................................................... FAILED (CRASH)

outputs/overwrite.test ........................................................................ FAILED (CRASH)

outputs/oversample.group/oversample ........................................................... FAILED (CRASH)

outputs/misc.getOutput ....................................................... FAILED (EXPECTED ERROR MISSING)

outputs/csv_final_and_latest.final ............................................................ FAILED (CRASH)

outputs/gmv.test .............................................................................. FAILED (CRASH)

outputs/position.test ......................................................................... FAILED (CRASH)

outputs/debug.show_var_residual_norms ....................................... FAILED (EXPECTED OUTPUT MISSING)

outputs/output_if_base_contains.dt_from_master ................................................ FAILED (CRASH)

--------------------------------------------------------------------------------------------------------------

Ran 50 tests in 6.6 seconds.

0 passed, 26 skipped, 0 pending, 50 FAILED

MAX FAILURES REACHED

As has been suggested on that page, I looked into all possible causes of errors and their solutions/workarounds, given under the heading "build issues". But, unfortunately, nothing came out of that. I would like to know if anyone here also faced the same issue and how they sorted it out. 

Thanks,

Debadutta Prusty

 projects/moose/test

make -j 4

./run_tests -j 4~/pr

[Jason Miller]

Just below "Build Issues" is "Failing Tests": https://mooseframework.inl.gov/help/troubleshooting.html#failingtests. Were you able to run the 'always_ok' test? Which is simply:

  ./run_tests -i always_ok

Also, the actual errors will be listed before:

Final Test Results:
--------------------------------------------------------------------------------------------------------------

If you scroll up a bit, you will see the actual reason for why tests are failing. If you would copy/paste one of those failures, it would help.

Cheers!

Jason

--
You received this message because you are subscribed to the Google Groups "moose-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to moose-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/1dbfb12b-c7a9-45f1-b15c-7d0652d3771eo%40googlegroups.com.

[debadutta prusty]

Hi Jason,

Unfortunately, it did not pass that test. The errors that showed up are given below:

tests/test_harness.always_ok: Working Directory: /home/debadutta/Desktop/Moose-projects/moose/test/tests/test_harness
tests/test_harness.always_ok: Running command: mpiexec -n 2 /home/debadutta/Desktop/Moose-projects/moose/test/moose_test-opt -i good.i --error --error-unused --error-override --no-gdb-backtrace
tests/test_harness.always_ok: /home/debadutta/Desktop/Moose-projects/moose/test/moose_test-opt: symbol lookup error: /home/debadutta/miniconda2/envs/moose/lib/./libmpifort.so.12: undefined symbol: MPII_F_TRUE
tests/test_harness.always_ok: /home/debadutta/Desktop/Moose-projects/moose/test/moose_test-opt: symbol lookup error: /home/debadutta/miniconda2/envs/moose/lib/./libmpifort.so.12: undefined symbol: MPII_F_TRUE
tests/test_harness.always_ok:
tests/test_harness.always_ok:
tests/test_harness.always_ok: Exit Code: 127
tests/test_harness.always_ok: ################################################################################
tests/test_harness.always_ok: Tester failed, reason: CRASH
tests/test_harness.always_ok:
tests/test_harness.always_ok ...................................................... [OVERSIZED] FAILED (CRASH)


Final Test Results:
--------------------------------------------------------------------------------------------------------------
tests/test_harness.always_ok ...................................................... [OVERSIZED] FAILED (CRASH)
--------------------------------------------------------------------------------------------------------------
Ran 1 tests in 0.3 seconds.
0 passed, 0 skipped, 0 pending, 1 FAILED

As can be clearly seen, the reason is CRASH and it can only be resolved by addressing build issues. I followed that exactly, reinstalling MOOSE among other things. But, it's not working simply.

To unsubscribe from this group and stop receiving emails from it, send an email to moose...@googlegroups.com.

[Jason Miller]

Thanks! Looks like this might be an issue with MPI... What is interesting, is that many tests do not need MPI. Yet all tests are failing (the fifty that ran anyway)...  Can you perform the following?

  mpiexec -n 2 echo hello world

I am also concerned with 'miniconda2'. While I think you are using Python3 (run_tests would utterly fail if you were not), it may be related to an old Conda install. Or a mix and match of Python2 miniconda with Python 3 channels? I've never heard of such a thing, but, there it is. The path says miniconda2 in it. So I have to ask.

Also, can you perform an ldd on moose_test-opt?

  ldd /home/debadutta/Desktop/Moose-projects/moose/test/moose_test-opt

It will tell us what libraries the moose_test-opt binary is linking with. It may be linking to some other MPI library during build which is not available during runtime.

Are all the tests failing in the same exact manner (/home/debadutta/miniconda2/envs/moose/lib/./libmpifort.so.12: undefined symbol: MPII_F_TRUE)?

Cheers!

Jason

To unsubscribe from this group and stop receiving emails from it, send an email to moose-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/ad2e0be6-ca99-4d37-8617-a42cc0a5ce20o%40googlegroups.com.

[debadutta prusty]

The results of "mpiexec -n 2 echo hello world"

hello world
hello world

The results of "ldd /home/debadutta/Desktop/Moose-projects/moose/test/moose_test-opt"

    linux-vdso.so.1 =>  (0x00007ffcdd14f000)
    libmoose_test-opt.so.0 => /home/debadutta/Desktop/Moose-projects/moose/test/lib/libmoose_test-opt.so.0 (0x00007f269e0fd000)
    libmoose-opt.so.0 => /home/debadutta/Desktop/Moose-projects/moose/framework/libmoose-opt.so.0 (0x00007f269ca41000)
    libhit-opt.so.0 => /home/debadutta/Desktop/Moose-projects/moose/framework/contrib/hit/libhit-opt.so.0 (0x00007f269c9e1000)
    libmesh_opt.so.0 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/libmesh_opt.so.0 (0x00007f269b7da000)
    libtimpi_opt.so.2 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/libtimpi_opt.so.2 (0x00007f269b7cd000)
    libgfortran.so.4 => /home/debadutta/miniconda2/envs/moose/lib/libgfortran.so.4 (0x00007f269b69d000)
    libgcc_s.so.1 => /home/debadutta/miniconda2/envs/moose/lib/libgcc_s.so.1 (0x00007f269b689000)
    libstdc++.so.6 => /home/debadutta/miniconda2/envs/moose/lib/libstdc++.so.6 (0x00007f269b515000)
    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f269b1e4000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f269ae1a000)
    libmpi.so.12 => /opt/intel/compilers_and_libraries_2018.0.128/linux/mpi/intel64/lib/libmpi.so.12 (0x00007f269a0e8000)
    libpcre-opt.so.0 => /home/debadutta/Desktop/Moose-projects/moose/framework/contrib/pcre/libpcre-opt.so.0 (0x00007f269a0b8000)
    libvtkCommonCore-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/libvtkCommonCore-6.3.so.1 (0x00007f2699c60000)
    libvtkCommonDataModel-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/libvtkCommonDataModel-6.3.so.1 (0x00007f2699948000)
    libvtkImagingCore-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/libvtkImagingCore-6.3.so.1 (0x00007f26996ec000)
    libvtkIOImage-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/libvtkIOImage-6.3.so.1 (0x00007f2699570000)
    libvtkImagingMath-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/libvtkImagingMath-6.3.so.1 (0x00007f2699526000)
    libpetsc.so.3.13 => /home/debadutta/miniconda2/envs/moose/lib/libpetsc.so.3.13 (0x00007f2697db9000)
    libHYPRE-2.18.2.so => /home/debadutta/miniconda2/envs/moose/lib/libHYPRE-2.18.2.so (0x00007f2697911000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f26976f3000)
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f26974ef000)
    /lib64/ld-linux-x86-64.so.2 (0x000056370e56f000)
    libgomp.so.1 => /home/debadutta/miniconda2/envs/moose/lib/libgomp.so.1 (0x00007f26974c2000)
    libnetcdf.so.13 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/libnetcdf.so.13 (0x00007f2697375000)
    libvtkIOCore-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../libmesh-vtk/lib/libvtkIOCore-6.3.so.1 (0x00007f26972fc000)
    libvtkIOXML-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../libmesh-vtk/lib/libvtkIOXML-6.3.so.1 (0x00007f2697232000)
    libvtkIOParallelXML-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../libmesh-vtk/lib/libvtkIOParallelXML-6.3.so.1 (0x00007f269720a000)
    libvtkParallelMPI-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../libmesh-vtk/lib/libvtkParallelMPI-6.3.so.1 (0x00007f26971f2000)
    libvtkParallelCore-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../libmesh-vtk/lib/libvtkParallelCore-6.3.so.1 (0x00007f2697199000)
    libz.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/libz.so.1 (0x00007f269717e000)
    libslepc.so.3.13 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/libslepc.so.3.13 (0x00007f2696e49000)
    libparmetis.so => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/libparmetis.so (0x00007f2696df8000)
    libmetis.so => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/libmetis.so (0x00007f2696d7c000)
    libquadmath.so.0 => /usr/lib/x86_64-linux-gnu/libquadmath.so.0 (0x00007f2696b3c000)
    librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f2696934000)
    libvtksys-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/./libvtksys-6.3.so.1 (0x00007f26968e3000)
    libvtkCommonMisc-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/./libvtkCommonMisc-6.3.so.1 (0x00007f26968cc000)
    libvtkCommonSystem-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/./libvtkCommonSystem-6.3.so.1 (0x00007f26968b5000)
    libvtkCommonTransforms-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/./libvtkCommonTransforms-6.3.so.1 (0x00007f2696881000)
    libvtkCommonMath-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/./libvtkCommonMath-6.3.so.1 (0x00007f269685e000)
    libvtkCommonExecutionModel-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/./libvtkCommonExecutionModel-6.3.so.1 (0x00007f26967c7000)
    libvtkpng-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/./libvtkpng-6.3.so.1 (0x00007f2696794000)
    libvtktiff-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/./libvtktiff-6.3.so.1 (0x00007f2696724000)
    libvtkmetaio-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/./libvtkmetaio-6.3.so.1 (0x00007f2696681000)
    libvtkDICOMParser-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/./libvtkDICOMParser-6.3.so.1 (0x00007f2696660000)
    libvtkzlib-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/./libvtkzlib-6.3.so.1 (0x00007f2696645000)
    libvtkjpeg-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh-vtk/lib/./libvtkjpeg-6.3.so.1 (0x00007f269660f000)
    libsuperlu_dist.so.6 => /home/debadutta/miniconda2/envs/moose/lib/./libsuperlu_dist.so.6 (0x00007f2696501000)
    libmpifort.so.12 => /home/debadutta/miniconda2/envs/moose/lib/./libmpifort.so.12 (0x00007f26964c2000)
    libmfhdf.so.0 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/./libmfhdf.so.0 (0x00007f2696495000)
    libdf.so.0 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/./libdf.so.0 (0x00007f26963e6000)
    libhdf5_hl.so.100 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/./libhdf5_hl.so.100 (0x00007f26963c0000)
    libhdf5.so.103 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/./libhdf5.so.103 (0x00007f269601e000)
    libcurl.so.4 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/./libcurl.so.4 (0x00007f2695f95000)
    libvtkIOXMLParser-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../libmesh-vtk/lib/./libvtkIOXMLParser-6.3.so.1 (0x00007f2695f7b000)
    libvtkIOLegacy-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../libmesh-vtk/lib/./libvtkIOLegacy-6.3.so.1 (0x00007f2695ed6000)
    libjpeg.so.9 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/././libjpeg.so.9 (0x00007f2695e97000)
    libssh2.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/././libssh2.so.1 (0x00007f2695e52000)
    libssl.so.1.1 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/././libssl.so.1.1 (0x00007f2695dc2000)
    libcrypto.so.1.1 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/././libcrypto.so.1.1 (0x00007f2695af6000)
    libgssapi_krb5.so.2 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/././libgssapi_krb5.so.2 (0x00007f2695aa6000)
    libkrb5.so.3 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/././libkrb5.so.3 (0x00007f26959cd000)
    libk5crypto.so.3 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/././libk5crypto.so.3 (0x00007f26959ae000)
    libcom_err.so.3 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/././libcom_err.so.3 (0x00007f26959a7000)
    libvtkexpat-6.3.so.1 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../libmesh-vtk/lib/././libvtkexpat-6.3.so.1 (0x00007f2695970000)
    libkrb5support.so.0 => /home/debadutta/miniconda2/envs/moose/libmesh/lib/../../lib/./././libkrb5support.so.0 (0x00007f2695960000)
    libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f2695745000)

Yes, all tests have "MPII_F_TRUE" suffixed to their error messages.

To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/ad2e0be6-ca99-4d37-8617-a42cc0a5ce20o%40googlegroups.com.

[Jason Miller]

I believe this is your issue:

    libmpi.so.12 => /opt/intel/compilers_and_libraries_2018.0.128/linux/mpi/intel64/lib/libmpi.so.12 (0x00007f269a0e8000)

Somehow during the build step, this Intel MPI library is being made available before Conda's. I'd like to figure out how to coexist with Intel before asking you to remove your shell's ability to source the Intel activation profile.

Guessing only:

Can you move your activation scripts of Conda to the end of your shell profile (or Intel before Conda)? Assuming Bash, this will be in your: ~/.bashrc, or ~/.bash_profile files. Afterwards, it will be necessary to re-build MOOSE.

To unsubscribe from this group and stop receiving emails from it, send an email to moose-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/6988c129-9751-443f-a696-14696cea642do%40googlegroups.com.

[debadutta prusty]

Unfortunately, the error remains even after putting intel activation lines above Conda in the .bashrc file.

To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/CALK7ujyp01P8xyQ7VibgyWkYg-t%2BwiKt4F9wMys3Hu0iCYb6qg%40mail.gmail.com.

--

Debadutta Prusty

[Jason Miller]

Dang. In this case, it will be necessary to either make only Conda available or Intel. What I do myself in these cases, is I isolate the Intel sourcing routines to a file not a part of my shell's initialization routines. Meaning, I create the following files:

  ~/intel_environment

  ~/conda_environment

And remove both Conda and Intel initialization routines from my bash profiles.

When I want to use either Intel, or Conda, I then source that pertinent file before I start work:

  . ~/intel_environment

  which mpicc (should point towards /opt/intel)

In another terminal:

  . ~/conda_environment

  conda activate moose

  which mpicc (should point towards ~/miniconda2)

I believe the Intel activation is a one-liner (put the following in ~/intel_environment, and remove it from ~/.bashrc and/or ~/.bash_profile):

  . /opt/intel/compilers_and_libraries_2018.0.128/linux/bin/compilervars.sh intel64

This is all under the assumption you are in control of the Intel compiler (the above sourcing line is in your ~/.bashrc or ~/.bash_profile). If, for some reason your system is multi-user, and your admin has made the choice to make Intel available by default all the time... it is going to be a bit trickier without their help. Rather than explaining all that in this email, I'd like to find out if the above is possible first...

There is of course, a very elegant way to do all this: modules (an environment management tool). But that is for another email as well, if  you're willing.

Cheers!

Jason

To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/CAMpZyO35HNBG6V8Abb9_5SZaZ2gGNuYJVqkP%2BUmGVk-SjB%3DQ1A%40mail.gmail.com.

[debadutta prusty]

The intel part has two lines, which are given below:

. /opt/intel/bin/compilervars.sh intel64
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/intel/compilers_and_libraries_2018.0.128/linux/mpi/intel64/lib/libmpicxx.so

Shall I move both of them over into the intel environment file that you are suggesting that I create?

To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/CALK7ujw_hd3dJkJrqboJ5CbTEgOQ0n-AYun%2B-k1ojz5sv1jNbw%40mail.gmail.com.

--

Debadutta Prusty

[Jason Miller]

I would do both yes... But it is interesting that the second line exists at all. I've never seen an LD_LIBRARY_PATH set to point directly at a file.

To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/CAMpZyO2pr-ijhbRh3GrT1%3DYQQe8s%3D1dY0t%3Don58si2p-n3uMCg%40mail.gmail.com.

[debadutta prusty]

I did that and then tried to reinstall moose. But the following new error comes up when I type in "conda create --name moose moose-libmesh moose-tools".

Collecting package metadata (current_repodata.json): failed

UnavailableInvalidChannel: The channel is not accessible or is invalid.
  channel name: moose
  channel url: https://mooseframework.org/conda/moose
  error code: 404

You will need to adjust your conda configuration to proceed.
Use `conda config --show channels` to view your configuration's current state,
and use `conda config --show-sources` to view config file locations.

To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/CALK7ujyEzcDnQL_hTLUpmq4SscimWB3GYQW7AXvaRJ-H7qevkw%40mail.gmail.com.

--

Debadutta Prusty

[Alexander Lindsay]

You need to make sure you do:

$ conda config --remove channels https://mooseframework.org/conda/moose
$ conda config --add channels idaholab

To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/CAMpZyO1MJOZZ30o-34bZHPYcKE0%3D6ERPk_X4_QE4XD9k-%2BR2Lg%40mail.gmail.com.

[debadutta prusty]

That did the trick. Thanks a lot, Alexander for your help.

To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/CANFcJrH2bU%2BmcaUt6qvEW0Y8CnX4b2VN4cpFQjqM67Z5H8SBBg%40mail.gmail.com.

--

Debadutta Prusty