Error in peacock whicle loading excutable

309 views
Skip to first unread message

iisc....@gmail.com

unread,
Sep 21, 2020, 5:55:11 AM9/21/20
to moose-users
Dear All,

why I am getting sudden error in peacock while loading excutables?? It was working fine i have close peacock and rerun again and suddenly this happen. 

can some one help me please? or I have to build moose again?

WARNING
 '/home/naveen/projects/moose/modules/combined/combined-opt -options_left 0 --json --allow-test-objects' exited with non zero status 127.

Please make sure your application is built and able to execute the given arguments.
Working dir: /home/naveen/projects/moose/python/peacock
Output: /home/naveen/projects/moose/modules/combined/combined-opt: symbol lookup error: /home/naveen/anaconda3/envs/moose/lib/./libmpifort.so.12: undefined symbol: MPII_F_TRUE

WARNING
 Failed to load json from '/home/naveen/projects/moose/modules/combined/combined-opt': '/home/naveen/projects/moose/modules/combined/combined-opt -options_left 0 --json --allow-test-objects' exited with non zero status 127.

Please make sure your application is built and able to execute the given arguments.
Working dir: /home/naveen/projects/moose/python/peacock
Output: /home/naveen/projects/moose/modules/combined/combined-opt: symbol lookup error: /home/naveen/anaconda3/envs/moose/lib/./libmpifort.so.12: undefined symbol: MPII_F_TRUE

Thanking you.
Naveen

Jason Miller

unread,
Sep 21, 2020, 10:08:24 AM9/21/20
to moose-users
The last time I saw this error,  was due to an Intel compiler stack being introduced on the system (causing a conflict with Conda):


Would you peruse that thread, and see if anything we did helps you?

Thanks!
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/47f09d97-3269-45ef-b924-932a05dc8d33n%40googlegroups.com.

iisc....@gmail.com

unread,
Sep 21, 2020, 7:30:35 PM9/21/20
to moose-users
Thanks Jason. Let me go through the thread.

iisc....@gmail.com

unread,
Sep 21, 2020, 9:01:00 PM9/21/20
to moose-users
Hi Jason,
Thanks for help. I don't have intel compiler the reason for this error causing by mpich which is install in /usr/lib64/mpich. I had remove (sudo dnf remove mpich) and now everything on  track.
But still wondering how suddenly cause this problem on run time??
...
mesh/checkpoint.test_4 ....................................................................... [min_cpus=4] OK
mesh/checkpoint.test_4a ...................................................................... [min_cpus=4] OK
mesh/checkpoint.test_8 .................................................. [min_cpus=8,insufficient slots] SKIP
mesh/checkpoint.test_8a ................................................. [min_cpus=8,insufficient slots] SKIP
dampers/min_damping.min_elem_damping ........................................... [min_cpus=2,min_threads=2] OK
dampers/min_damping.min_general_damping ................................................................... OK
--------------------------------------------------------------------------------------------------------------
Ran 2394 tests in 224.9 seconds.
2394 passed, 34 skipped, 0 pending, 0 failed


Naveen

Andrew Slaughter

unread,
Sep 21, 2020, 11:08:43 PM9/21/20
to moose...@googlegroups.com
The skips you are showing here indicated that you don't have enough processors to run those tests. Also, depending on the system you are running I would expect tests that timeout simply because your hardware isn't as quick as our testing machines.

Naveen Kumar

unread,
Sep 22, 2020, 6:51:08 PM9/22/20
to moose...@googlegroups.com
Thank you for your response Andrew.

Reply all
Reply to author
Forward
0 new messages