You are here

Error message: ArchiveManager spinning down

2 posts / 0 new
Last post
Error message: ArchiveManager spinning down

Hi Rosetta community! 

The first run I created worked perfectly, but for some reason creating another run for the trimed sequence is not working! I got this error message after about 1min of starting the run: 

ERROR: error detected in ArchiveManager -- spinning down

ERROR:: Exit from: src/protocols/jd2/archive/ line: 426


MPI_ABORT was invoked on rank 2 in communicator MPI_COMM_WORLD 

with errorcode 911.


NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.

You may or may not see output from other processes, depending on

exactly when Open MPI kills them.


mpiexec has exited due to process rank 2 with PID 4849 on

node Sequekal exiting improperly. There are two reasons this could occur:


1. this process did not call "init" before exiting, but others in

the job did. This can cause a job to hang indefinitely while it waits

for all processes to call "init". By rule, if one process calls "init",

then ALL processes must call "init" prior to termination.


2. this process called "init", but exited without calling "finalize".

By rule, all processes that call "init" MUST call "finalize" prior to

exiting or it will be considered an "abnormal termination"


This may have caused other processes in the application to be

terminated by signals sent by mpiexec (as reported here).


I don't know what to adjust! Please help me to solve this issue. 


Post Situation: 
Sun, 2016-01-24 02:42

These are MPI error messages, not Rosetta error messages.  MPI is the wrapper layer that lets you use Rosetta on multiple processors at once.

The Rosetta part of the message signals "ERROR:: Exit from: src/protocols/jd2/archive/ line: 426".  Glancing at this code, it suggests your input command line options didn't lead to any actual jobs to perform.  My most likely guess is that you are running run B in the same directory that you ran run A, so that it senses the output is already present and doesn't want to overwrite it.  Otherwise it may be something like a file path being wrong, or nstruct being zero.

Sun, 2016-01-24 03:24