Thread constructor fails

[Liserion]

Check these boxes if you have followed the posting rules.

• Q&A General is the most appropriate section for my question
• I have consulted the posting Guidelines on the Discussions front page
• I have searched the Discussions forum and my question has not been asked before
• I have searched the MOOSE website and the documentation does not answer my question
• I have formatted my post following the posting guidelines (screenshots as a last resort, triple back quotes around pasted text)

Question

Hi!
I somehow have a new problem. I thought at first my computer just wasn't having enough power, but there must be a bug somewhere, since it also does not work on the hpc. I tried running debuggers but with no success. Are there any other debuggers I could try to see where the mistake is?
https://github.com/Liserion/babbler is my code with various custom kernels.

Job ID: 46340935
Cluster: lcluster
User/Group: jk98dago/jk98dago
State: FAILED (exit code 137)
Nodes: 1
Cores per node: 48
CPU Utilized: 00:05:19
CPU Efficiency: 36.92% of 00:14:24 core-walltime
Job Wall-clock time: 00:00:18
Memory Utilized: 366.75 MB (estimated maximum)
Memory Efficiency: 0.37% of 96.00 GB (2.00 GB/core
This is what the HPC gave back to me (I tried changing kernels etc.)

On my debugger i go the following error:

*** ERROR ***
thread constructor failed: Resource temporarily unavailable

Stack frames: 6
0: 0   libmesh_opt.0.dylib                 0x0000000106c6eddf libMesh::print_trace(std::__1::basic_ostream<char, std::__1::char_traits<char>>&) + 1151
1: 1   libmoose-opt.0.dylib                0x0000000105b33f40 moose::internal::mooseErrorRaw(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>>, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>>) + 784
2: 2   libmoose-opt.0.dylib                0x000000010535ac87 void mooseError<char const*>(char const*&&) + 247
3: 3   libmoose-opt.0.dylib                0x0000000105b4309a MooseApp::run() + 2138
4: 4   babbler-opt                         0x0000000100010bcb main + 139
5: 5   dyld                                0x00007ff80e57441f start + 1903
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
[unset]: write_line error; fd=-1 buf=:cmd=abort exitcode=1
:
system msg for write_line failure : Bad file descriptor
Process 10423 exited with status = 1 (0x00000001) 
(lldb) 

I hope this is the right place to post, thank you so much for your help!

[GiudGiud]

Hello

I have not seen this one before. How many cores do you have available when you schedule a job? There are 48 cores per nodes, but are you using a full node?

[Liserion]

https://github.com/Liserion/babbler/tree/Liserion-patch-1

[GiudGiud]

this is a pretty dodgy link. how about a public github repo

[Liserion]

updated it, sorry about it

[GiudGiud]

thanks. The fix should be this
Liserion/babbler#1

[Liserion]

thank you very much! When I updated the code I still got an error. It was in the ParticleBVPostBCKernel.h:

#include "IntegratedBC.h"

class ParticleBVPostBCKernel;

//InputParameters
//ParticleBVPostBCKernel::validParams()

class ParticleBVPostBCKernel:public IntegratedBC
{
public:
  ParticleBVPostBCKernel(const InputParameters & parameters);
  static InputParameters validParams();

so I just indented this parted: //InputParameters
//ParticleBVPostBCKernel::validParams() since I got an error for this. Then I tried running the simulation and it worked, for the first time! Thank you so much. However, I am not sure if I ran it correctly since my computer was able to finish it in 20 minutes or so. My friends said I need to use a HPC, even for a smallish simulation like this. I'll look at the output this week.