lammps getting stuck

What are some of the common reasons that lammps might get stuck when running? There’s no error report and the shell is still executing but none of the output is printing after the number of atoms is printed.

What are some of the common reasons that lammps might get stuck when
running? There's no error report and the shell is still executing but none
of the output is printing after the number of atoms is printed.

there are lots of possible reasons. hard to say which are most
frequent. typically that depends on the details of the simulation,
too.
you may want to attach a debugger to the running process(es) and
obtain stack traces to determine where the code gets stuck.

axel.

Yea, I’m trying that now although I’m not used to debugging mpi jobs. For now though it seems to run on 1 core and I noticed when it was running before 1 process of the job wasn’t drawing any system resources.

Yea, I'm trying that now although I'm not used to debugging mpi jobs. For
now though it seems to run on 1 core and I noticed when it was running
before 1 process of the job wasn't drawing any system resources.

you don't really need to do "parallel debugging" here. just log into
the compute node(s), where the parallel process is running, determine
the process ids, and then use "gdb -p <pid>" to attach the debugger.
hit CTRL-C, type "where" to get the stack trace and then quit to
detach. this is the same process for parallel and for serial programs.
i bet, if you just google "gdb attach to running process", you'll find
plenty of tutorials and documentation.

axel.