[KTG]

Hi everyone,


I recently updated to Fedora 33, and no suddenly I get this error whenever I run snappy or an openFoam solver in parallel:

--> FOAM FATAL IO ERROR:
[4] error in IOstream "IOstream" for operation Foam::Istream& Foam:perator>>(Foam::Istream&, Foam::List<T>&) [with T = Foam::Vector<double>]
[4]
[4] file: IOstream at line 0.
[4]
[4] From bool Foam::IOstream::fatalCheck(const char*) const
[4] in file db/IOstreams/IOstreams/IOstream.C at line 63.

I have no idea what this means, or why it is happening. simpleFoam and snappyHexMesh produce the same error! Things still work in serial for some reason. I have tried updating, restarting, running various tutorial files, and keep getting the same behavior. I am not even 100% sure this is an installation issue. I removed the OF binary with dnf, and reinstalled it. Could this be a bug? If it is, it probably can't be reproduced off my computer.



Any help would be much appreciated.


Thanks

[KTG]

I should clarify what I mean by "suddenly". The programs start ok, and then crash after a short time. For example, snappyHexMesh gets to Feature refinement iteration 2 before it throws the error, which is very strange.

[KTG]

This is so insanely frustrating! I tried on a smaller casefile to see what would happen, and get a slightly different IO error!

[4] --> FOAM FATAL IO ERROR:  
[4] incorrect first token, expected '(', found on line 0: punctuation '[' 
[4]  
[4] file: IOstream at line 0. 
[4]  
[4]     From Foam::Istream& Foam::operator>>(Foam::Istream&, Foam::List<T>&) [with T = Foam::Pair<int>] 
[4]     in file lnInclude/ListIO.C at line 153. 
[4]  
FOAM parallel run exiting

Here, snappy got further along than before, I think because the mesh is smaller. Its as if something is getting overloaded, causing the crash, and then it sends out and unrelated error from whatever part of the code was currently running.


It gives different behavior every time I run it! I just ran it again and snappy made it all the way through, again, and it crashes during castellated, then again and it crashes during the snap! What could possibly cause this?!

[olesen]

Could be mpi-related.

[KTG]

I had that thought, and did the brainless thing of just reinstalling it - no change. I am not an expert on MPI, so if anyone has an ideas of how to diagnose, let me know!



Thanks

[EternalSeekerX]

Originally Posted by KTG

I had that thought, and did the brainless thing of just reinstalling it - no change. I am not an expert on MPI, so if anyone has an ideas of how to diagnose, let me know!
Thanks

It definitely seems like an mpi issue with the mpi version in fedora 33/34. Best bet is to try to purge and reinstall openmpi and then rerun Allwmake to see if it works. Or go into prefs file to tell Allwmake to use the openmpi given with the third party folder.

[KTG]

Thanks for the info. I ended up tearing everything down and switching to CentOS to appease IT. Hopefully it is helpful to other Fedora people out there...

[EternalSeekerX]

Originally Posted by KTG

Thanks for the info. I ended up tearing everything down and switching to CentOS to appease IT. Hopefully it is helpful to other Fedora people out there...

Okay I just build myself the latest OpenMPI (v4.1.0) and it works fine with all openfoam I have (namely 7,8, 1912 and 2012). I think the OpenMPI v 4.04 is bugged

[olesen]

Originally Posted by EternalSeekerX

I think the OpenMPI v 4.04 is bugged

Thanks for the heads up.

[EternalSeekerX]

Originally Posted by olesen

Thanks for the heads up.

It seems the update to OpenMPI v4.0.5 fixed the issue, either that or me compiling OF8 inside a Fedora 32 container and then transferring it to f34 did the trick?

Edit: Seems like a F33 issue, works flawlessly inside F32 docker I created.