The OPAL Discussion Forum

["Adelmann Andreas (PSI)" <andreas.adelmann AT psi.ch>]

Hi Philippe what you see is the MPI initialisation. If nothing else 

appears then I suspect anything from: cluster failure, disk error etc,

slurm script error. So this is a suspicion maybe if you can send me full

logfile we can work this out.

Cheers A 

On 27 May 2021, at 13:52, Philippe Piot <philippe.piot AT gmail.com> wrote:

Dear All,

   When running optimization in OPAL it sometimes happens that the optimizer gets stuck: the job is still active (shows as running) in the cluster queue, but none of the files (opt/pilot.trace.0) are updated anymore. It also usually happens before any of the .json outputs are written. Doing a cat of the stdout (which is not more updated) gives the info below. Could somebody points to other diagnostics I could use to troubleshoot this issue? My problem is quite simple (I have two objective emit_x and emit_y and one "derived" objective sqrt(emit_x*emit_y) and four constraints. Thank you for any suggestions. All the best,  -- Philippe. 

--- tail of stdout

Ippl> CommMPI: Initialization complete.
Ippl> CommMPI: Parent process waiting for children ...
Ippl> CommMPI: Initialization complete.
Ippl> CommMPI: Parent process waiting for children ...
Ippl> CommMPI: Initialization complete.
Ippl> CommMPI: Parent process waiting for children ...
Ippl> CommMPI: Initialization complete.
Ippl> CommMPI: Parent process waiting for children ...
Ippl> CommMPI: Initialization complete.